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 4 and 7 and type the answer here:
  • Post
Thanks for sharing your comment! If your comment doesn't appear right away, please be patient as it may take a few minutes to publish or may require moderation.
  • I got the above error, I have tried the above solution but it does not work, please help

  • I am getting same error when i try to connect to sql server in a virtual machine...

    protocols are ok ,,any idea>??

  • VIA protocol was it.. thanks for the help !!

  • Hm....we followed this order after someone set all of them to disabled.

    1.) Reboot

    2.) Enable TCP/IP

    3.) Go into the properties of TCP and select "Yes" for Enabled for the actual IP for the SQL Server (when we enabled all it didn't work)

    4.) Go into services and start the SQL Service

    5.) Bring the SQL Cluster Service online

  • When I am trying to start the SQL server-2005 on Vista OS, I am getting

    Error: 17190, Severity: 16, State: 1.

    FallBack certificate initialization failed with error code: 4.

    Error: 26015, Severity: 16, State: 1.

    Unable to load user-specified certificate. Because connection encryption is required, the server will not be able to accept any connections. You should verify that the certificate is correctly installed. See "Configuring Certificate for Use by SSL" in Books Online.

    Error: 17182, Severity: 16, State: 1.

    TDSSNIClient initialization failed with error 0x80092004, status code 0x80.

    Error: 17182, Severity: 16, State: 1.

    TDSSNIClient initialization failed with error 0x80092004, status code 0x1.

    Error: 17826, Severity: 18, State: 3.

    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.

    Error: 17120, Severity: 16, State: 1.

    Please help me

  • Hi Srinivas,

     Since your error happens during fallback SSL certificate initialization, the best place to your question would probably be at the SQL Server Security forum: http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=92&SiteID=1

    Hope this helps,

    Dan

  • Right on!  this at least led me to the protocols which showed all were disabled.  thanks for the help!

    As a side note, its nice to see the community come together when MS fails.  I am sick of trying to get additional help on an error only for it to say no help text exists...  unreal!

    l8r

  • Hey Thanks!

    Initially i had hurriedly disabled the VIA for the SQL Native Client which obviously had not worked. But the moment i disabled it for MSSQLSERVER, the service started.

    Thanks again.

  • Hey Thanks!

    Initially i had hurriedly disabled the VIA for the SQL Native Client which obviously had not worked. But the moment i disabled it for MSSQLSERVER, the service started.

    Thanks again.

  • Muito Obrigado!!

    Thanks!!!!

  • I get different error codes:  

    TDSSNIClient initialization failed with error 0xb7, status code 0x50.

    TDSSNIClient initialization failed with error 0xb7, status code 0x1.

    Any ideas?

  • 0xb7 is decimal 183 which in winerror.h is ERROR_ALREADY_EXISTS.

    Status code 0x50 is attempting to start named pipes.

    Hence I think you have a named pipe collision problem. Perhaps you have another SQL Server instance running with the same named pipe name configured.

    Open "SQL Server Configuration Manager" and examine all the sub-nodes under the

    "SQL Server 2005 Network Configuration" node.  Each sub-node is an instance.  Examine named pipes property for each.  You may have same named pipe name for 2 instances by mistake.

    The default instance named pipe (MSSQLSERVER) is usually named:

    \\.\pipe\sql\query

    A named instance named pipe is usually named:

    \\.\pipe\MSSQL$<InstanceName>\sql\query

    Note replace <InstanceName> above with the name of the instance.

  • Yeah!!!!

    That's exactly what I need!!!

    Thank you,Vaughn!

    Thank you!!!

  • Thanks!

    It was the VIA protocol.

    VALEEUU!!

  • Hey you made my day and prevent my head to be thrown to a wall

    thanks a zillion

    :)

Page 4 of 8 (107 items) «23456»