Just had something strange happen.

I install some updates (KB973825, 961371, 972260, 972636), reboot the box (Server 2003, SQL Server 2005), and I can't connect to the database anymore. I try manually starting MSSQLSERVER, but I get "The MSSQLSERVER service on Local Computer started and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service."

Here's what the logs say:


2009-08-10 12:39:43.76 Server Error: 17182, Severity: 16, State: 1.
2009-08-10 12:39:43.76 Server TDSSNIClient initialization failed with error 0x7e, status code 0x60.
2009-08-10 12:39:43.76 Server Error: 17182, Severity: 16, State: 1.
2009-08-10 12:39:43.76 Server TDSSNIClient initialization failed with error 0x7e, status code 0x1.
2009-08-10 12:39:43.76 Server Error: 17826, Severity: 18, State: 3.
2009-08-10 12:39:43.76 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.
2009-08-10 12:39:43.76 Server Error: 17120, Severity: 16, State: 1.
2009-08-10 12:39:43.76 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.
I look up that error, and find this - http://blogs.msdn.com/sql_protocols/...31/487090.aspx

Check what network protocols are enabled for SQL Server in the SQL Configuration Manager application. If the VIA protocol is enabled disable it and then try starting the SQL Server service again.
Sure enough, that did the trick...

Anyone have any idea why this would happen? This is our dev server - now I'm paranoid about installing those updates on the live server (although it seems unlikely that the updates would cause this), even though I know how to solve it...