Today a developer called me telling me she could not start the SQL Server service. After checking the SQL error log I found the errors 17182, 17826 & 17120. I did not see these errors before, so I check them using Google and I found a blog(http://blogs.msdn.com/sql_protocols/archive/2005/10/31/487090.aspx) where the author gives a solution to these errors. The solution did not apply completely to my situation. The author of the blog advises to disable the VIA protocol and then try to restart the SQL Service again. In my case when I was checking if the VIA protocol was enabled, I found out that all the protocols were disabled. After enabling TCP/IP & the Named Pipes protocols I was able to restart the SQL Server service.
You can see a part of the SQL error log here:
2010-02-08 16:25:26.83 Server Error: 17182, Severity: 16, State: 1.
2010-02-08 16:25:26.83 Server TDSSNIClient initialization failed with error 0xd, status code 0x4.
2010-02-08 16:25:26.83 Server Error: 17182, Severity: 16, State: 1.
2010-02-08 16:25:26.83 Server TDSSNIClient initialization failed with error 0xd, status code 0x1.
2010-02-08 16:25:26.83 Server Error: 17826, Severity: 18, State: 3.
2010-02-08 16:25:26.83 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.
2010-02-08 16:25:26.83 Server Error: 17120, Severity: 16, State: 1.
2010-02-08 16:25:26.83 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.
IgnacioSalom.com 