Error 1053: The service did not respond to start in timely fashion SQL Server 2003

I can't get SQL to start.  I had a problem with the registry and had to restore from backup.  Now all the SQL services give the Error 1053: when trying to start them.  Any ideas?
schowningAsked:
Who is Participating?
 
QlemoBatchelor, Developer and EE Topic AdvisorCommented:
Jim,
That is not correct. A named instance of MSSQL has an internal name of  MSSQL$instance (probably MSSQL$SQLEXPRESS). MyMachineName\SQLExpress is the name used for the connection string.

I assume you just need ot change and then revert the service account info used for those services. That will correct any misaligned credential info which might have come with the registry repair.

About the MMC thing - I'm clueless at the moment how to repair that (besides by repairing MSSQL itself).
0
 
alisafiaCommented:
0
 
schowningAuthor Commented:
When I went to SQL Server Configuration Manager (Local), I got a message that says MMC could not create the snap-in.  Any idea about how to get around that?
0
Network Scalability - Handle Complex Environments

Monitor your entire network from a single platform. Free 30 Day Trial Now!

 
Jason WatkinsIT Project LeaderCommented:
Hi,

More details about your current setup would be great. It could be that you need to update your version of MMC. What version of SQL Server is in play? SQL 2000 or SQL 2005, there is no product version called "SQL Server 2003". There is a Windows Server 2003.
0
 
schowningAuthor Commented:
I am running Windows Server 2003 and SQL 2005.  It is a small business server.  I tried updating MMC and it says the current version is newer than the 3.1 version I found.  
0
 
gheistCommented:
Check application and system event log around time error pops up...
0
 
schowningAuthor Commented:
In application event viewer I get:
Faulting application sqlservr.exe version 2005.90.4035.0 faulting module kernel32.dll, version 5.2.3790.4480. fault address 0x000bef7.

In system event viewer I get:
The SQL Server (SQLEXPRESS) service failed to start due to the following error:  The service did not respond to the start or control request in a timely fashion.
0
 
Jim P.Commented:
To other experts: That is SQL Server Express 2005 SP3 on a Win2003 SBS server.

In the services panel see what user ID is in the Log On As column. What user id is it? Does the user ID have admin rights to the box?

What happens if you try to fire it up via a command line?

How to: Start an Instance of SQL Server (SQL Server Configuration Manager)
http://msdn.microsoft.com/en-us/library/ms190699.aspx
0
 
schowningAuthor Commented:
When I type "net start MSSQLSERVER" on command line, I get "The service name is invalid".    The login ID in services is Local System.
0
 
Jim P.Commented:
You will need to look at the services name in the Services.msc console. It probably is something like "MyMachineName\SQLExpress".  The other thing to do is create a domain user that has limited domain rights but is a local admin user "MyDomain\SQLMgr".

Go in and change the user id on the services and change the log on as in the security tab.

0
 
Jim P.Commented:
Qlemo,

Thanks for the correction.

As far as the MMC issue, SQL Server 2000 used an "msc" files as snapins to MMC. With 2005+ they went to a standalone exe configuration. Could it it be he is trying to use old tools with 2005?

In that case he would need to download the SSMS Express edition.

Microsoft SQL Server Management Studio Express
http://www.microsoft.com/downloads/details.aspx?FamilyID=c243a5ae-4bd1-4e3d-94b8-5a0f62bf7796&displaylang=en
0
 
schowningAuthor Commented:
I'm sorry but I don't know what I need to do.

"I assume you just need ot change and then revert the service account info used for those services"

What do I need to change and revert?

Thanks
0
 
Jim P.Commented:
He is referring to the LocalSystem account may not be setup correctly. We're trying to suggest that you change all the SQL Services to a "real" account. You may change it back afterward.
0
 
schowningAuthor Commented:
Sorry.  How do I change the SQL services to a real account?  I can't get into the Sql Server Configuration Manager.
0
 
Jim P.Commented:
That can be done by right clicking the service in the Services column. There will be a security tab. Select Log on as this user and then put in the "MyDomain\SQLMgr" userid. Then put in the password.
0
 
schowningAuthor Commented:
I've put in Administrator in this field.  Nothing changed.
0
 
Jim P.Commented:
OK, then there is a deeper issue. At this point, I would find any files with an extension of mdf or ldf and copy them to a separate directory so that you have some sort of backup.

After that  try this from a command line sqlservr.exe -f -m -s <instancename>

How to: Start an Instance of SQL Server (sqlservr.exe)
http://technet.microsoft.com/en-us/library/ms180965%28SQL.90%29.aspx
0
 
QlemoBatchelor, Developer and EE Topic AdvisorCommented:
I agree, I would try the manual start of MSSQL now (as suggested twice). This will show if the service setup is an issue, or the instance - e.g. a defective database or transaction log file (.mdf, .ndf, .ldf).
0
 
QlemoBatchelor, Developer and EE Topic AdvisorCommented:
In addition you could have a look into the sql log file, which should be located at
C:\Program Files\Microsoft SQL Server\MSSQL*\MSSQL\Log
and is called ERRORLOG. You can open it in Notepad, though it has no extension. Important part is at the end, if there are errors, we need to know this part.
0
 
schowningAuthor Commented:
I tried the manual restart and nothing changed.  I tried to re-install SQL express.  When I try to start the SQL Server (SQLEXPRESS) it still give me Error 1053: The service did not respond to the start or control request in a timely fashion.  The SQL Server Browser and VSS Writer did start.

The error log does not have any new entries since February when the registry problem happened.
0
 
QlemoBatchelor, Developer and EE Topic AdvisorCommented:
Looks like a missing / misaligned registry entry. A repair resp. reinstall should have corrected that, but did obviously not. I would try with providing additional parameters on commandline:

sqlservr -c -s SQLEXPRESS ^-d C:\Program Files\Microsoft SQL Server\MSSQL.9\MSSQL\Data\master.mdf ^-e C:\Program Files\Microsoft SQL Server\MSSQL.9\MSSQL\LOG\ERRORLOG ^-l C:\Program Files\Microsoft SQL Server\MSSQL.9\MSSQL\Data\mastlog.ldf
(the carrots are intentional, to allow for continuation on next line). This will show MSSQL where to search for the Master db and the errlog. The latter should then show new entries.
0
 
Jim P.Commented:
Qlemo,

I think there is no space between "-? C:\". I don't have SQL loaded on my machine to check. Please correct me if I'm wrong.
0
 
QlemoBatchelor, Developer and EE Topic AdvisorCommented:
Rechecked. The syntax description shows a blank between the switch and the argument. But the file names need to be enclosed in double quotes if they contain spaces, of course. So the command is more of

sqlservr  -c -s SQLEXPRESS ^
-d  "C:\Program Files\Microsoft SQL Server\MSSQL.9\MSSQL\Data\master.mdf"  ^
-e "C:\Program  Files\Microsoft SQL Server\MSSQL.9\MSSQL\LOG\ERRORLOG" ^
-l "C:\Program Files\Microsoft SQL  Server\MSSQL.9\MSSQL\Data\mastlog.ldf"
0
 
schowningAuthor Commented:
I got "Your SQL Server installation is either corrupt or has been tampered with (error getting instance ID from name.).  Please uninstall then re-run setup to correct this problem.  I've uninstalled and re-run setup 3 times.
0
 
QlemoBatchelor, Developer and EE Topic AdvisorCommented:
The "-s SLQEXPRESS" might not be correct. Maybe the instance name has been different. Do you have any recordings of the original instance name?
0
 
schowningAuthor Commented:
It gave me the same error.  In the services section, I show 2 instances (ATC) and (SQLEXPRESS) but the are not started.  Regardless of which on I put in the "-s SQLEXPRESS" I get the message ""Your SQL Server installation is either corrupt or has been tampered with (error getting instance ID from name.).  Please uninstall then re-run setup to correct this problem. "
0
 
QlemoBatchelor, Developer and EE Topic AdvisorCommented:
The instance name is something you cannot see at the moment, but is  stored somewhere. Frankly said, I don't know where that persistent instance name comes from. The only way to get that straight would be uninstall MSSQL (all instances!), clear the registry for MSSQL entries, and reinstall.


0
 
schowningAuthor Commented:
Thanks for your help!!!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.