After laptop goes into standby, SQLEXPRESS won't start

If my laptop goes into standby with the MSSQL$SQLEXPRESS service running, the service will not start again. I get the following error messages in my log:

2006-03-06 20:49:08.45 Server This instance of SQL Server last reported using a process ID of 1764 at 3/6/2006 1:48:21 PM (local) 3/6/2006 9:48:21 PM (UTC). This is an informational message only; no user action is required.

2006-03-06 20:49:08.45 Server Error: 17053, Severity: 16, State: 1.

2006-03-06 20:49:08.45 Server UpdateUptimeRegKey: Operating system error 5(Access is denied.) encountered.

2006-03-06 20:49:08.45 Server Registry startup parameters:

2006-03-06 20:49:08.45 Server -d c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf

2006-03-06 20:49:08.45 Server -e c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG

2006-03-06 20:49:08.45 Server -l c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf

2006-03-06 20:49:08.56 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.

2006-03-06 20:49:08.56 Server Detected 1 CPUs. This is an informational message; no user action is required.

2006-03-06 20:49:09.32 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.

2006-03-06 20:49:09.35 Server Database Mirroring Transport is disabled in the endpoint configuration.

2006-03-06 20:49:09.35 spid5s Starting up database 'master'.

2006-03-06 20:49:09.68 spid5s SQL Trace ID 1 was started by login "sa".

2006-03-06 20:49:09.76 spid5s Starting up database 'mssqlsystemresource'.

2006-03-06 20:49:10.03 spid5s Failed to check for new installation or a renamed server at startup. The logic for this check has failed unexpectedly. Run setup again, or fix the problematic registry key.

2006-03-06 20:49:10.03 Server Error: 17182, Severity: 16, State: 1.

2006-03-06 20:49:10.03 Server TDSSNIClient initialization failed with error 0x5, status code 0x90.

2006-03-06 20:49:10.03 Server Error: 17182, Severity: 16, State: 1.

2006-03-06 20:49:10.03 Server TDSSNIClient initialization failed with error 0x5, status code 0x1.

2006-03-06 20:49:10.03 Server Error: 17826, Severity: 18, State: 3.

2006-03-06 20:49:10.03 Server Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.

2006-03-06 20:49:10.03 Server Error: 17120, Severity: 16, State: 1.

2006-03-06 20:49:10.03 Server SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

Uninstalling, reinstalling and restoring the databases fixes the problem. Also, is there anyway to gracefully shut down the service on standby? Any help would be greatly appreciated.

Thanks,

David

Essentially this error below means that SQL no longer has access to it's registry keys.

2006-03-06 20:49:10.03 Server Error: 17182, Severity: 16, State: 1.

2006-03-06 20:49:10.03 Server TDSSNIClient initialization failed with error 0x5, status code 0x90.

Error 0x5 means "Access Denied" most likely due to the instance no longer having access to its configuration info stored in the registry. Not sure why going into standby mode would trigger a change in the registry key security.

|||

I don't have this problem on my laptop which goes in and out of standby multiple times a day. This seems like it is probably deeper than just SQL. I'm trying to track down some additional info from the Windows team.

In the mean time, I've occationally seen "weird" behavior associated with a corrupt user profile. You might consider recreating your user profile and see if the problem goes away. Kind of a scatter gun approach, but it's fairly easy to check. Read the following KB articles for more about troubleshooting profiles:

http://support.microsoft.com/kb/305506/en-us

http://support.microsoft.com/kb/811151/en-us

Regards,

Mike Wachal
SQL Express team

|||

Change your SQL Express to logon as the System account, by default it logs on as the Network something or another account which is a total crapshoot as to whether that account can get to the registry.

Gandalf

http://gandalf.hudlow.net

|||gandalf is totally right. I had the same problem on every reboot until I changed the account to LOCAL SYSTEM. Now everything is kosher|||

Every time you install a SQL instance it will automatically grant itself access to the various registry keys that it needs access to. Even if the service is running under network service. So you should not need to run it under local system account to get access to the registry keys. Switching SQL to run under local system will give it carte blanc to read the registry which will solve a problem where setup probably failed to grant itself proper perms on the reg keys.

Perhaps something on your machine is locking down reg key permissions after SQLExpress is installed, this is all I can think of that could cause this issue.

|||Yeah, this is a pretty good demo of why the registry is both the best and worst idea in history :)