SQL Server Forums
Profile | Register | Active Topics | Members | Search | Forum FAQ
 
Register Now and get your question answered!
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 SQL Server 2000 Forums
 MSDE (2000)
 MSDE Install Issue
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

jbender
Starting Member

1 Posts

Posted - 11/12/2004 :  11:42:15  Show Profile  Reply with Quote
We are trying to install MSDE on a new Dell desktop and when we run the setup.exe, it fails and the SQL Error log is...

2004-11-12 11:14:11.76 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)

2004-11-12 11:14:11.76 server Copyright (C) 1988-2002 Microsoft Corporation.
2004-11-12 11:14:11.76 server All rights reserved.
2004-11-12 11:14:11.76 server Server Process ID is 2872.
2004-11-12 11:14:11.76 server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL$CRM\LOG\ERRORLOG'.
2004-11-12 11:14:11.76 server SQL Server is starting at priority class 'normal'(2 CPUs detected).
2004-11-12 11:14:11.85 server SQL Server configured for thread mode processing.
2004-11-12 11:14:11.85 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
2004-11-12 11:14:11.90 spid4 Warning ******************
2004-11-12 11:14:11.90 spid4 SQL Server started in single user mode. Updates allowed to system catalogs.
2004-11-12 11:14:11.90 spid4 Starting up database 'master'.
2004-11-12 11:14:12.07 server Using 'SSNETLIB.DLL' version '8.0.766'.
2004-11-12 11:14:12.07 spid5 Starting up database 'model'.
2004-11-12 11:14:12.09 spid4 Server name is 'IT\CRM'.
2004-11-12 11:14:12.09 spid4 Skipping startup of clean database id 5
2004-11-12 11:14:12.09 spid4 Skipping startup of clean database id 6
2004-11-12 11:14:12.09 spid4 Starting up database 'msdb'.
2004-11-12 11:14:12.24 server SQL server listening on Shared Memory.
2004-11-12 11:14:12.24 server SQL Server is ready for client connections
2004-11-12 11:14:12.26 spid5 Clearing tempdb database.
2004-11-12 11:14:12.43 spid5 Starting up database 'tempdb'.
2004-11-12 11:14:12.51 spid4 Recovery complete.
2004-11-12 11:14:12.51 spid4 SQL global counter collection task is created.
2004-11-12 11:14:12.53 spid4 Warning: override, autoexec procedures skipped.
2004-11-12 11:14:21.95 spid4 SQL Server is terminating due to 'stop' request from Service Control Manager.

We have checked Add/Remove Programs and cleaned out all MSSQL and Microsoft SQL Server directories and Registry settings and we still get the same error message. Has anyone else seen something similar to this? If you fixed it, how?

sbt1
Yak Posting Veteran

89 Posts

Posted - 12/03/2004 :  09:59:00  Show Profile  Reply with Quote
Did you get past this problem? Looks to me like it ran ok, just that the service stopped.

Can you launch the service control manager and simply restart it?
Go to Top of Page

bobalston
Starting Member

USA
3 Posts

Posted - 01/13/2005 :  19:12:00  Show Profile  Reply with Quote
I have the exact same problem, at this same point in the log.

I have been trying to resolve this for weeks without success.
I downloaded the msizap.exe utility from here
http://support.microsoft.com/default.aspx?scid=kb;en-us;290301
it is part of this cleanup utility
and followed the instructions here
http://support.microsoft.com/kb/320873/EN-US/
for manually removing prior installations. I have such leftovers
from prior aborted installs.

Very frustrating.

Bob
Go to Top of Page

sbt1
Yak Posting Veteran

89 Posts

Posted - 02/04/2005 :  07:55:00  Show Profile  Reply with Quote
Are you guys sure the service is running?

This line:
2004-11-12 11:14:21.95 spid4 SQL Server is terminating due to 'stop' request from Service Control Manager

sure tells me that the Service Control Manager requested the service to stop.

I've never had any issues with MSDE.

Check the service, I'm guessing that's all it is.
Go to Top of Page

bobalston
Starting Member

USA
3 Posts

Posted - 02/04/2005 :  10:30:45  Show Profile  Reply with Quote
I found another posting (forget where) which suggested to run the install with a parm to avoid the rollback if an install error. Apparently it did fully install it.

Bob
Go to Top of Page

mhnsql
Starting Member

11 Posts

Posted - 02/08/2005 :  16:35:23  Show Profile  Reply with Quote
Bob, I am encountering the same error, there is no install parameter for an install error. If you can find that post on how to install with a roll back it would be great. I am really under the gun.
thanks
Mike
Go to Top of Page

bobalston
Starting Member

USA
3 Posts

Posted - 02/08/2005 :  17:19:53  Show Profile  Reply with Quote
I am not sure if this was the actual post I used, but it appears to have the same parm for avoiding rollback
. an excerpt:

"If you have SQL Server 7.0 client tools installed on your computer, and the MSDE 2000 Setup returns this error message An installation rolls back. When the MSDE 2000 setup fails, it may rollback the installation. The rollback may cause the deletion of some of the setup logs. For example, the Cnfgsvr.out file in the Install folder is deleted during rollback. For troubleshooting the MSDE 2000 setup, you can disable the rollback feature to collect the setup output files. Here is a sample command for disabling rollback:
D:\MSDE2000\>Setup.exe DISABLEROLLBACK=1 /L*v C:\MSDE_setup.log

http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q317328

Good luck. This one was a bugger.

Bob
Go to Top of Page

SunnyDee
Yak Posting Veteran

76 Posts

Posted - 01/10/2007 :  20:58:19  Show Profile  Reply with Quote
I am having the same error. I tried to follow the instructions to remove the previous installation, but my conditions did not exactly meet the items in the microsoft documents. I then had to manually delete the registry keys as recommended by microsoft.

I tried installing and re-installing multiple times applying the correct sps, etc. The problem occurs when the desktop engine attempts to configure. If I attempt to start the service from Enterprise Manager, I receive the error "1060 The specified service does not exist...."

Below is the entry in the error log file:

2007-01-10 18:17:15.29 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)

2007-01-10 18:17:15.29 server Copyright (C) 1988-2002 Microsoft Corporation.
2007-01-10 18:17:15.29 server All rights reserved.
2007-01-10 18:17:15.29 server Server Process ID is 3736.
2007-01-10 18:17:15.29 server Logging SQL Server messages in file 'C:\Microsoft SQL Server\Mssql\data\MSSQL$HOTMAMA\LOG\ERRORLOG'.
2007-01-10 18:17:15.32 server SQL Server is starting at priority class 'normal'(1 CPU detected).
2007-01-10 18:17:16.10 server SQL Server configured for thread mode processing.
2007-01-10 18:17:16.11 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
2007-01-10 18:17:16.41 spid3 Warning ******************
2007-01-10 18:17:16.41 spid3 SQL Server started in single user mode. Updates allowed to system catalogs.
2007-01-10 18:17:16.50 spid3 Starting up database 'master'.
2007-01-10 18:17:17.33 server Using 'SSNETLIB.DLL' version '8.0.760'.
2007-01-10 18:17:17.33 spid5 Starting up database 'model'.
2007-01-10 18:17:17.47 spid3 Server name is 'VERY\HOTMOMA'.
2007-01-10 18:17:17.47 spid3 Skipping startup of clean database id 5
2007-01-10 18:17:17.47 spid3 Skipping startup of clean database id 6
2007-01-10 18:17:17.47 spid3 Starting up database 'msdb'.
2007-01-10 18:17:18.72 spid5 Clearing tempdb database.
2007-01-10 18:17:18.78 server SQL server listening on 192.168.1.6: 1517.
2007-01-10 18:17:18.78 server SQL server listening on 10.4.8.81: 1517.
2007-01-10 18:17:18.78 server SQL server listening on 127.0.0.1: 1517.
2007-01-10 18:17:19.65 spid5 Starting up database 'tempdb'.
2007-01-10 18:17:19.98 spid3 Recovery complete.
2007-01-10 18:17:19.98 spid3 SQL global counter collection task is created.
2007-01-10 18:17:20.04 spid3 Warning: override, autoexec procedures skipped.
2007-01-10 18:17:20.75 server SQL server listening on TCP, Shared Memory, Named Pipes.
2007-01-10 18:17:20.75 server SQL Server is ready for client connections
2007-01-10 18:17:35.19 spid3 SQL Server is terminating due to 'stop' request from Service Control Manager.

Any help is really appreciated, as I'm totally and completely stuck!
Go to Top of Page

SunnyDee
Yak Posting Veteran

76 Posts

Posted - 01/14/2007 :  17:28:16  Show Profile  Reply with Quote
After searching on this issue for days, it appears that many other people have had the same problem. I finally was able to fix this problem by moving my sqlserver files to a new location and reinstalling. This was after I wiped out some the registry files (which I hate doing) and the other steps described in this article:

http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q317328

While it still didn't work, someone in another forum suggested moving the files to anothe directory, and it finally installed. It appears that not all of the registry files are removed during an uninstall in the control panel.

Go to Top of Page

hugerob
Starting Member

1 Posts

Posted - 02/15/2007 :  10:45:40  Show Profile  Reply with Quote
The above solution seems to work.
But make sure that you also remove all references to the Instance (if you are using one) in the registry (using regedit.exe).
For example if the instance is called "HUGEROB" look for all mentions of it in the registry and remove them. Of course don't bother with MRU (Most recently Used) lists.
Go to Top of Page

jpdb
Starting Member

1 Posts

Posted - 09/24/2007 :  20:57:59  Show Profile  Reply with Quote
It took me a long time to figure this problem out, but I have solved it and applied this solution to multiple computers having the same issue. The problem is that if a sql installation (or MSDE installation) goes awry in any way and aborts midway, or if there was a previous installation and then a removal, the removal process does not get rid of all the appropriate folders and registry keys. this has to be done manually. Here are the steps I took:

1. Delete the folder: C:\Program Files\Microsoft SQL Server
2. go into the regedit application by entering "regedit" into the prompt after selecting "run" from your start menu.
3. Look in HKEY_LOCAL_MACHINE | SOFTWARE | MICROSOFT | and delete the folder "Microsoft SQL Server" as well as the folder MSSQLServer and SQL Redist.
4. run the sql installation exe file. The installation will complete without any notice, but sql will not be running. Restart the machine and you will see the sql service will start.

hope this helps, it sure did for me.

jpdb
Go to Top of Page

jdekid
Starting Member

1 Posts

Posted - 04/02/2008 :  02:40:22  Show Profile  Reply with Quote
You made my day sir. Thank you so much. I followed the exact mentioned steps and I could actually get thru in installeing MSDE. Thank you once again !!!


quote:
Originally posted by jpdb

It took me a long time to figure this problem out, but I have solved it and applied this solution to multiple computers having the same issue. The problem is that if a sql installation (or MSDE installation) goes awry in any way and aborts midway, or if there was a previous installation and then a removal, the removal process does not get rid of all the appropriate folders and registry keys. this has to be done manually. Here are the steps I took:

1. Delete the folder: C:\Program Files\Microsoft SQL Server
2. go into the regedit application by entering "regedit" into the prompt after selecting "run" from your start menu.
3. Look in HKEY_LOCAL_MACHINE | SOFTWARE | MICROSOFT | and delete the folder "Microsoft SQL Server" as well as the folder MSSQLServer and SQL Redist.
4. run the sql installation exe file. The installation will complete without any notice, but sql will not be running. Restart the machine and you will see the sql service will start.

hope this helps, it sure did for me.

jpdb

Go to Top of Page

srazai
Starting Member

1 Posts

Posted - 05/30/2008 :  12:58:32  Show Profile  Reply with Quote
Thank you so very much! I have been trying to resolve this issue for 2 weeks without success. Stumbling onto this site (specifically this forum) has saved my sanity. Thanks again.
Go to Top of Page

johnn
Starting Member

South Africa
1 Posts

Posted - 01/27/2009 :  04:18:49  Show Profile  Reply with Quote
This fix works fine. Thanks
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.12 seconds. Powered By: Snitz Forums 2000