April 13, 2006 at 3:52 am
I had to do a server restart and all of a sudden the SQL2005 service simply refuses to start.
Can anyone suggest a cause and solution.
I'm getting the following errors in the event log
TDSSNIClient initialization failed with error 0xd, status code 0x10.
TDSSNIClient initialization failed with error 0xd, 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.
April 13, 2006 at 8:18 am
These resources may be of assistance (I have not personally encounted but would like to know if eaither of these is helpful):
1. spaces after the tcp port on the server side
http://blogs.msdn.com/sql_protocols/archive/2005/10/14/480848.aspx
2. 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.
http://blogs.msdn.com/sql_protocols/archive/2005/10/31/487090.aspx#comments
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply