TDSSNIClient initialization failed with error 0xd, status code 0x36.

TDSSNIClient initialization failed with error 0xd, status code 0x36.

I've seen this problem posted a couple times on the MSDN forums so I'm including the problem and the solution here.  The MSDN SQL Server Data Access Forum is available at: http://forums.microsoft.com/msdn/ShowForum.aspx?ForumID=87.

If you see the following error messsages in your SQL Server ERRORLOG:

2005-10-30 15:35:44.79 Server      Error: 17182, Severity: 16, State: 1.
2005-10-30 15:35:44.79 Server      TDSSNIClient initialization failed with error 0xd, status code 0x36.
2005-10-30 15:35:44.79 Server      Error: 17182, Severity: 16, State: 1.
2005-10-30 15:35:44.79 Server      TDSSNIClient initialization failed with error 0xd, status code 0x1.
2005-10-30 15:35:44.79 Server      Error: 17826, Severity: 18, State: 3.
2005-10-30 15:35:44.79 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.
2005-10-30 15:35:44.79 Server      Error: 17120, Severity: 16, State: 1.
2005-10-30 15:35:44.79 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.

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. 

Hope this helps,
Vaughn

Leave a Comment
  • Please add 6 and 5 and type the answer here:
  • Post
  • Great help...worked smoothly !

    thanks
  • Tried this didn't fix it any other hot fixes?? What user security settings are you guys using with the srvice.

    Cheers
  • JO, is the first error message in your ERRORLOG exactly "Error: 17182, Severity: 16, State: 1" with "error 0xd, status code 0x36" or is it slightly different? If it's the exact same I suggest retrying the steps again and maybe rebooting once to be certain the service has stopped and started.

    If the message is different in error code or state code please post the codes from your message and we'll try to provide some suggestions.

    Thanks,
    Vaughn
  • Great help, Thanx

    My Web apps hostyed on web server with SQL server. Today morning suddenly, it stopped working.

    I put the word 'TDSDNIClient' in the google and first link helped me out.

    Now can u help me knowing what VIA protocol does? And how our SQL server is dependent on VIA protocol with port number 1433.

    I guess there is some conflict using same port no. 1433.

    Regards,
    Amit S.
    amit_shah312002@yahoo.co.in

  • Exactly what I was looking for !
    Thanks a lot.

    Regards,
    Julia
  • Thanks for your help. This work great !!
  • Just a follow up on Amit's question about the VIA protocol.  The VIA protocol is a special protocol that requires specialized hardware (a custom network card essentially) and also a VIA driver from a 3rd party vendor.  VIA is used in some specialized applications where massive network bandwidth is needed, for example if you have 2 SQL Servers that replicate huge amounts of data.  

    So do NOT enable VIA unless you have the VIA hardware and drivers installed on your system.
  • Hi,

    I've got a slight different status code. Here it goes:

    2006-03-13 00:33:11.93 Server      Error: 17182, Severity: 16, State: 1.
    2006-03-13 00:33:11.93 Server      TDSSNIClient initialization failed with error 0xd, status code 0x4.
    2006-03-13 00:33:11.93 Server      Error: 17182, Severity: 16, State: 1.
    2006-03-13 00:33:11.93 Server      TDSSNIClient initialization failed with error 0xd, status code 0x1.
    2006-03-13 00:33:11.93 Server      Error: 17826, Severity: 18, State: 3.
    2006-03-13 00:33:11.93 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-13 00:33:11.93 Server      Error: 17120, Severity: 16, State: 1.
    2006-03-13 00:33:11.93 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.

    Any clues?

    Best Regards,
    Paulo
  • Hi,

     I had struck up with the Error 17120, sql service cannot be started,i tried with all the options no use. So if any one can know please mark a mail to srinicms@yahoo.com.
  • Srini,
     Please post a complete errorlog including 17120, 17182 and 17826....
  • Paulo,
     Looks like you disabled all protocols. Without a protocol enabled, sql server won't be able accept requests and process queries. You need to enable at least one protocol.
  • Is there a way to disable the VIA protocol during install.  While attempting to install SQL Server 2005, the installation attempts to start the SQL Server Service midway through install (even if I use the advanced option to not start SQL Server service at end of install).  It fails to start, with event logs showing the errors listed here.  I can only retry or cancel.  If I cancel, it rolls back the installation.  Without the complete install, I cannot seem to configure the protocols.  
  • Are you certain the error code and status code are the same (0xd, and 0x36, resp.).  Generally, Setup does not enable VIA by default, so it is surprising to hit this during installation.  

    Thanks,
    Peter Gvozdjak
  • "2006-03-13 00:33:11.93 Server      Error: 17182, Severity: 16, State: 1.
    2006-03-13 00:33:11.93 Server      TDSSNIClient initialization failed with error 0xd, status code 0x4.
    2006-03-13 00:33:11.93 Server      Error: 17182, Severity: 16, State: 1.
    2006-03-13 00:33:11.93 Server      TDSSNIClient initialization failed with error 0xd, status code 0x1.
    2006-03-13 00:33:11.93 Server      Error: 17826, Severity: 18, State: 3.
    2006-03-13 00:33:11.93 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-13 00:33:11.93 Server      Error: 17120, Severity: 16, State: 1.
    2006-03-13 00:33:11.93 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. "

    We had the same error (the difference is that the first status code is 0x4), and disabling via didn't help. What seems to be the problem, is that sqlserver was installed while no network interface was present.
  • The 0x4 error indicates that no protocol was enabled and SQL Server was unable to start.  The simple remedy is to enable at least one of the protocols.  Take a look at this previous blog, http://blogs.msdn.com/sql_protocols/archive/2006/01/10/511330.aspx, to see a more complete list of error states.

    Il-Sung.

    Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights
Page 1 of 8 (107 items) 12345»