"CZERNAI" wrote:

> When running the setup for this the installer stops and says to refer to the
> setup log.
> The log reads as follows
> 2005-01-27 07:06:36.26 server Microsoft SQL Server 2000 - 8.00.760
> (Intel X86)
> Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation
> Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
>
> 2005-01-27 07:06:36.26 server Copyright (C) 1988-2002 Microsoft
> Corporation.
> 2005-01-27 07:06:36.26 server All rights reserved.
> 2005-01-27 07:06:36.26 server Server Process ID is 1968.
> 2005-01-27 07:06:36.26 server Logging SQL Server messages in file
> 'C:\Program Files\Microsoft SQL Server\MSSQL\LOG\ERRORLOG'.
> 2005-01-27 07:06:36.29 server SQL Server is starting at priority class
> 'normal'(1 CPU detected).
> 2005-01-27 07:06:36.51 server SQL Server configured for thread mode
> processing.
> 2005-01-27 07:06:36.54 server Using dynamic lock allocation. [500] Lock
> Blocks, [1000] Lock Owner Blocks.
> 2005-01-27 07:06:36.68 spid3 Warning ******************
> 2005-01-27 07:06:36.68 spid3 SQL Server started in single user mode.
> Updates allowed to system catalogs.
> 2005-01-27 07:06:36.71 spid3 Starting up database 'master'.
> 2005-01-27 07:06:37.10 server Using 'SSNETLIB.DLL' version '8.0.766'.
> 2005-01-27 07:06:37.15 spid5 Starting up database 'model'.
> 2005-01-27 07:06:37.26 server SQL server listening on Shared Memory.
> 2005-01-27 07:06:37.26 server SQL Server is ready for client connections
> 2005-01-27 07:06:37.28 spid3 Server name is 'SERVER'.
> 2005-01-27 07:06:37.28 spid3 Skipping startup of clean database id 5
> 2005-01-27 07:06:37.29 spid3 Skipping startup of clean database id 6
> 2005-01-27 07:06:37.31 spid3 Starting up database 'msdb'.
> 2005-01-27 07:06:37.54 spid5 Clearing tempdb database.
> 2005-01-27 07:06:38.31 spid5 Starting up database 'tempdb'.
> 2005-01-27 07:06:38.45 spid3 Recovery complete.
> 2005-01-27 07:06:38.45 spid3 SQL global counter collection task is
> created.
> 2005-01-27 07:06:38.50 spid3 Warning: override, autoexec procedures
> skipped.
> 2005-01-27 07:06:46.67 spid3 SQL Server is terminating due to 'stop'
> request from Service Control Manager.
>
> What have I done wrong--