February 26, 2009 at 5:36 pm
I am getting a "Setup Failed to Configure the Server" message when attempting to install a client application which includes MSDE 2000 w/SP4
The article http://support.microsoft.com/kb/816499 describes this happening when the computer previously had MSDE with the same named instance.
I have deleted all MS SQL folders and registry keys referencing MSSQL but I am still getting the resulot above. Any ideas?
February 27, 2009 at 9:02 am
A little more information:
Here is the error log from the MSSQL folder:
2009-02-25 17:42:46.60 server Copyright (C) 1988-2002 Microsoft Corporation.
2009-02-25 17:42:46.60 server All rights reserved.
2009-02-25 17:42:46.60 server Server Process ID is 2284.
2009-02-25 17:42:46.60 server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL$(instancename)\LOG\ERRORLOG'.
2009-02-25 17:42:46.68 server SQL Server is starting at priority class 'normal'(2 CPUs detected).
2009-02-25 17:42:47.38 server SQL Server configured for thread mode processing.
2009-02-25 17:42:47.38 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
2009-02-25 17:42:47.41 spid4 Warning ******************
2009-02-25 17:42:47.41 spid4 SQL Server started in single user mode. Updates allowed to system catalogs.
2009-02-25 17:42:47.47 spid4 Starting up database 'master'.
2009-02-25 17:42:47.76 spid5 Starting up database 'model'.
2009-02-25 17:42:47.76 server Using 'SSNETLIB.DLL' version '8.0.2039'.
2009-02-25 17:42:47.79 spid4 Server name is '(machine name)\(instancename)'.
2009-02-25 17:42:47.79 spid4 Skipping startup of clean database id 5
2009-02-25 17:42:47.79 spid4 Skipping startup of clean database id 6
2009-02-25 17:42:47.79 spid4 Starting up database 'msdb'.
2009-02-25 17:42:47.80 server SQL server listening on Shared Memory.
2009-02-25 17:42:47.80 server SQL Server is ready for client connections
2009-02-25 17:42:48.19 spid5 Clearing tempdb database.
2009-02-25 17:42:48.33 spid5 Starting up database 'tempdb'.
2009-02-25 17:42:48.37 spid4 Recovery complete.
2009-02-25 17:42:48.37 spid4 SQL global counter collection task is created.
2009-02-25 17:42:48.40 spid4 Warning: override, autoexec procedures skipped.
2009-02-25 17:42:56.80 spid4 SQL Server is terminating due to 'stop' request from Service Control Manager.
So why would the Service Control Manager making a 'stop' request?
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply