Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2005 Forums
 SQL Server Administration (2005)
 SQL Server does not start after windows update

Author  Topic 

tanu
Yak Posting Veteran

57 Posts

Posted - 2007-05-25 : 09:45:01
Windows updates are scheduled for the server every 15 days. After windows update the machine reboots on its own but sql server does not start. If I reboot the mchine manually sql server starts without any problem. SQL services set to start automatically.
Can somone tell me what do I need to do to fix this problem.

rmiao
Master Smack Fu Yak Hacker

7266 Posts

Posted - 2007-05-25 : 09:55:14
Any related message in windows event logs?
Go to Top of Page

tanu
Yak Posting Veteran

57 Posts

Posted - 2007-05-25 : 10:34:59
Appication Log
Set AWE Enabled to 1 in the configuration parameters to allow use of more memory.
FallBack certificate initialization failed with error code: 1.
Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.

TDSSNIClient initialization failed with error 0x80092004, status code 0x80.
TDSSNIClient initialization failed with error 0x80092004, status code 0x1.
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.
SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

But when I reboot it manually I got this messages:

Set AWE Enabled to 1 in the configuration parameters to allow use of more memory.

A self-generated certificate was successfully loaded for encryption.
Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].

Go to Top of Page

rmiao
Master Smack Fu Yak Hacker

7266 Posts

Posted - 2007-05-25 : 12:10:36
Looks like service startup sequence issue, os starts sql service before its dependency services.
Go to Top of Page

tanu
Yak Posting Veteran

57 Posts

Posted - 2007-05-25 : 12:27:18
How do I fix it?
Go to Top of Page

Kristen
Test

22859 Posts

Posted - 2007-05-25 : 12:42:27
Batch file to start it after a reasonable delay after a reboot?
Go to Top of Page

tanu
Yak Posting Veteran

57 Posts

Posted - 2007-05-25 : 12:49:50
That means I should not make the sql services automatic. After update in the night I need a job to run that would start all sql services after an hour.
Go to Top of Page

Kristen
Test

22859 Posts

Posted - 2007-05-25 : 12:58:26
Or just schedule the BATCH file to Start SQL Service once an hour (or more often). If they are already started it will have no effect.

If you go this route I suggest you think about a way of preventing this if you manually stop SQL Services for a deliberate reason. Temporarily Renaming the Batch file would do ... for example.

(I have used this method before to ensure that Services are KEPT running, particularly before MS introduced an Agent that watched for services that died unexpectedly)

Kristen
Go to Top of Page

tanu
Yak Posting Veteran

57 Posts

Posted - 2007-05-25 : 13:24:45
I forgot to mention that I tried to start services manually 9 hours after rebooting but it didn't start. I had to reboot the machine to make it work. I got the same error message.

Do you think it is something to do with the self-generated certificate. If it is not there I will get the error.

Go to Top of Page

Kristen
Test

22859 Posts

Posted - 2007-05-25 : 13:32:02
"Do you think it is something to do with the self-generated certificate"

Yes, assuming that you are using the Force Protocol Encryption option

See: http://support.microsoft.com/kb/318605

If you turn off "Force Protocol Encryption" and SQL Services starts normally then t he SSL is your problem, I reckon.

Kristen
Go to Top of Page

tanu
Yak Posting Veteran

57 Posts

Posted - 2007-05-25 : 14:21:08
I have "Force Protocol Encryption" turned off. When I reboot the server the service starts automatically.
Because in the event log I found :
"A self-generated certificate was successfully loaded for encryption."

Why doesn't this certificate generate and load when the machine reboots after windows update?
What is the work around?
Go to Top of Page

Kristen
Test

22859 Posts

Posted - 2007-05-25 : 14:33:50
Sorry, don't know the answer to that one
Go to Top of Page

tanu
Yak Posting Veteran

57 Posts

Posted - 2007-05-25 : 14:42:45
If I have "Force Protocol Encryption" turned off, then it should not need any certificate.
How do I get self-generated certificate?
Go to Top of Page

Kristen
Test

22859 Posts

Posted - 2007-05-25 : 14:44:36
"If I have "Force Protocol Encryption" turned off, then it should not need any certificate."

Yup, I agree with that.

"How do I get self-generated certificate?"

There are tools within Windows Server, but its so long sine I;ve used them I have forgotten.

But I still don't see why you would need one

Kristen
Go to Top of Page
   

- Advertisement -