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


Comments (108)

  1. Qureshi says:

    Great help…worked smoothly !

    thanks

  2. JO says:

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

    Cheers

  3. SQL Protocols says:

    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

  4. deobrat says:

    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

  5. Julia says:

    Exactly what I was looking for !

    Thanks a lot.

    Regards,

    Julia

  6. Thanks for your help. This work great !!

  7. Matt Neerincx [MSFT] says:

    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.

  8. Paulo Sebastião says:

    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

  9. srini says:

    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.

  10. SQL Protocols says:

    Srini,

     Please post a complete errorlog including 17120, 17182 and 17826….

  11. SQL Protocols says:

    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.

  12. dlorenz says:

    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.  

  13. SQL Protocols says:

    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

  14. "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.

  15. SQL Protocols says:

    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

  16. CatsCradle says:

    Here’s the errors I get. I turned off VIA.. still didn’t work.

    Any Ideas?

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

    2006-04-10 21:50:56.35 Server      TDSSNIClient initialization failed with error 0x7e, status code 0x60.

    2006-04-10 21:50:56.35 Server      Error: 17182, Severity: 16, State: 1.

    2006-04-10 21:50:56.35 Server      TDSSNIClient initialization failed with error 0x7e, status code 0x1.

    2006-04-10 21:50:56.35 Server      Error: 17826, Severity: 18, State: 3.

    2006-04-10 21:50:56.35 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-04-10 21:50:56.35 Server      Error: 17120, Severity: 16, State: 1.

    2006-04-10 21:50:56.35 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.

  17. CatsCradle says:

    Sorry!! False alarm. I thought I had disabled VIA but in fact hadn’t. Once I did the problem was fixed. Thanks a bunch.

  18. Lazar says:

    Did anyone determined the solution to this problem?

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

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

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

    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.

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

    SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

  19. SQL Protocols says:

    Status code 0x4 means that all protocols are disabled, as mentioned by Il-Sung above:

    The simple remedy is to enable at least one of the protocols.  If that does not help, let us know.  

    See also blog at http://blogs.msdn.com/sql_protocols/archive/2006/01/10/511330.aspx, to see a more complete list of error states.

    Peter

    Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights

  20. SQL Server 2005 could fail to bring up due to various causes, there are several great blogs that talk…

  21. Sharon Ball says:

    I have this same error, and I tried disabling / enabling various protocols to no avail. In my case I think it it because we have changed the SQL 2005 server from DHCP to be using a static IP address.

    Does anyone know if there is anything I can do to save it? Or is it a re-install?

    Many Thanks

  22. SQL Protocols says:

    Hi, Sharon

       

       This error code happens when server gets via settings fail. So, to fix your probelm:

    1) Are you using VIA protocol or not? If not, did you enabled VIA? After you disabled it, did you restart the server? If you are using VIA, please check correspondant via ipadress and port configuration in VIA driver utility to see whether they match the info when you open SQL Server 2005 configuration Manager client protocol VIA properties.

    2) Could you check server errorlog to see whether there is more specific info like:

    ("The SQL Server failed to initialize VIA support library [QLVipl.dll]. This normally indicates the VIA support library does not exist or is corrupted. Please repair or disable the VIA network protocol. Error: 0x7e.

    ")

    As for how to see server error log, please check following blog:

    http://blogs.msdn.com/sql_protocols/archive/2006/04/28/585835.aspx

    Thanks!

    Ming.

  23. Prasanna says:

    Thanks for the quick fix .

  24. robossliu says:

    Thanks a lot. The solution worked well.

  25. annoyed ms user says:

    Do you not think it would be a good idea to inform people of the consequences of a windows update to a server applicance BEFORE they apply the update instead of having more wasted time and server downtime while searching for a fix. Thanks ! Well not really –  thanks for wasting time, again.

  26. Rajesh S. Chandan says:

    Hi Vaughn,

    Thanks a lot. Server is working Now.

    (If the VIA protocol is enabled disable it and then try starting the SQL Server service again.)  

    Thanks once again.

  27. Charbel says:

    it worked fine for me

    big thanks

  28. Scott Lock says:

    Excellent!  Worked perfectly…once you get out of the "Client Network Protocols" tree!

  29. Ashok Boddeda says:

    Its Working great!! Cool solution Thanks.

    Ashok

  30. Nathan says:

    That fix worked! I’ve been pulling my hair out over this one. Thanks!

  31. Cosmin Serban says:

    This worked fine for the sql server 2005 service. Thanks!

  32. Kuldeep says:

    Great!! Thanks a lot…worked for me

  33. Hi,

    Its a great help. I disabled VIA protocol and gotrid of the issue. Thanks to share this with us. I am very happy as I failed to find solution on numerous sites.

  34. Donna Palmer says:

    Great,  great  help !!!   Extremely   helpful

  35. Jason says:

    Yes turning off VIA and restarting the service worked for me as well..

    Many thanks, Jason

  36. karay akar says:

    if you run sql 2005 with sqlexpress stop sqlexpress, and turn of VIA then restart service…

  37. Radha Krishna Prasad says:

    I have tried it but still not able to start sql server 2005

  38. Matt Neerincx (MSFT) says:

    Post back with the exact error lines from the errorlog, you may have a different status code.

  39. Mohan says:

    Hi,

    I am getting the same error but when i try to disable the VIA, I still cannot restart the service and it gives the same error again and again.  The SQL was working fine until we enable the VIA protocol and restart the service, but it didnt restart and we tried many times to disable the VIA and restart still cannot.  Is there any issues? Our SQL is in clustered environment.  Any help?

  40. sajil says:

    brilliant advice, just spent 2 hours trying everything else

  41. Jacques says:

    It Worked Very well, Thanks, Something so simple, can actually seem to give so many complication’s.

    Thanks.

  42. Rosario says:

    WOW!

    Thank you so much.

    That fixed my problem!

  43. siyixin says:

    Thank u for your kindness and erudition.

  44. Özgür says:

    thank you very much that i lerned something and solved my problem.

  45. Ettien says:

    I got the above error, I have tried the above solution but it does not work, please help

  46. bismi jomom says:

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

    protocols are ok ,,any idea>??

  47. BK says:

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

  48. Not a SqlGuy says:

    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

  49. srinivas says:

    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

  50. SQL Protocols says:

    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

  51. Kiethb says:

    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

  52. man04 says:

    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.

  53. man04 says:

    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.

  54. Gilmar Rocha says:

    Muito Obrigado!!

    Thanks!!!!

  55. Joe Sequela says:

    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?

  56. MattN says:

    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:

    \.pipesqlquery

    A named instance named pipe is usually named:

    \.pipeMSSQL$<InstanceName>sqlquery

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

  57. Jed says:

    Yeah!!!!

    That’s exactly what I need!!!

    Thank you,Vaughn!

    Thank you!!!

  58. Rodrigo França says:

    Thanks!

    It was the VIA protocol.

    VALEEUU!!

  59. Nadia says:

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

    thanks a zillion

    🙂

  60. Alok Pagariya says:

    It worked for me.

    Thanks A Lot 🙂

  61. charlie says:

    it is coming up with this:

    General protection fault!

    History: Address = 0x10918b0b (filename not found)

    Address: = 0xd     (filename not found)

  62. charlie says:

    sorry

    can you help please

    thank you

  63. Sri says:

    I am getting following error when starting the service with service account. this account is admin on the box.

    If i start the sql server with my domain account, the services starts successfully.

    10/17/2008 07:17:44,Server,Unknown,SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

    10/17/2008 07:17:44,Server,Unknown,Error: 17120 17826 17182 17190<c/> Severity: 16<c/> State: 1.

    10/17/2008 07:17:44,Server,Unknown,Could not start the network library because of an internal error in the network library. To determine the cause<c/> review the errors immediately preceding this one in the error log.

    10/17/2008 07:17:44,Server,Unknown,Error: 17826<c/> Severity: 18<c/> State: 3.

    10/17/2008 07:17:44,Server,Unknown,TDSSNIClient initialization failed with error 0x80092004<c/> status code 0x1.

    10/17/2008 07:17:44,Server,Unknown,Error: 17182<c/> Severity: 16<c/> State: 1.

    10/17/2008 07:17:44,Server,Unknown,TDSSNIClient initialization failed with error 0x80092004<c/> status code 0x80.

    10/17/2008 07:17:44,Server,Unknown,Error: 17182<c/> Severity: 16<c/> State: 1.

    10/17/2008 07:17:44,Server,Unknown,Unable to initialize SSL encryption because a valid certificate could not be found<c/> and it is not possible to create a self-signed certificate.

    10/17/2008 07:17:44,Server,Unknown,FallBack certificate initialization failed with error code: 1.

    10/17/2008 07:17:44,Server,Unknown,Error: 17190<c/> Severity: 16<c/> State: 1.

  64. Kumar Sachin says:

    Hi Thanks For this great Information. I spend my one whole day to search and RnD. but no fruit.

    Finally I disable VIA protocal and Now it worked fine.

    Kumar Sachin

  65. Luis Buendia says:

    Thank you very much!!

    This has been a very effective solution.

    It works very well.

    Thank you again.

  66. harpco says:

    Any help would be greatly appreciated!!

    2009-01-13 23:47:25.68 Server      Error: 17182, Severity: 16, State: 1.

    2009-01-13 23:47:25.68 Server      TDSSNIClient initialization failed with error 0x2, status code 0x80.

    2009-01-13 23:47:25.68 Server      Error: 17182, Severity: 16, State: 1.

    2009-01-13 23:47:25.68 Server      TDSSNIClient initialization failed with error 0x2, status code 0x1.

    2009-01-13 23:47:25.68 Server      Error: 17826, Severity: 18, State: 3.

    2009-01-13 23:47:25.68 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-01-13 23:47:25.68 Server      Error: 17120, Severity: 16, State: 1.

    2009-01-13 23:47:25.68 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.

  67. bb says:

    SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

    TDSSNIClient initialization failed with error 0x7e, status code 0x60.

    TDSSNIClient initialization failed with error 0x7e, status code 0x60.

  68. rev.felix says:

    Any help would be appreciated.

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

    Server      TDSSNIClient initialization failed with error 0x2, status code 0xd.

    spid8s      Starting up database ‘model’.

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

    Server      TDSSNIClient initialization failed with error 0x2, status code 0x1.

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

    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.

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

    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.

  69. Ankit Agarwal says:

    2009-04-05 18:51:36.54 Server      Error: 26023, Severity: 16, State: 1.

    2009-04-05 18:51:36.54 Server      Server TCP provider failed to listen on [ ‘any’ <ipv4> 1443]. Tcp port is already in use.

    2009-04-05 18:51:36.54 Server      Error: 17182, Severity: 16, State: 1.

    2009-04-05 18:51:36.54 Server      TDSSNIClient initialization failed with error 0x2740, status code 0xa.

    2009-04-05 18:51:36.54 Server      Error: 17182, Severity: 16, State: 1.

    2009-04-05 18:51:36.54 Server      TDSSNIClient initialization failed with error 0x2740, status code 0x1.

    2009-04-05 18:51:36.54 Server      Error: 17826, Severity: 18, State: 3.

    2009-04-05 18:51:36.54 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-04-05 18:51:36.54 Server      Error: 17120, Severity: 16, State: 1.

    2009-04-05 18:51:36.54 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.

  70. imran says:

    Thanks buddy it solved the problem

  71. Veera says:

    Thanks a lot .This worked for me.

  72. Taqveem says:

    My Shared Memory protocol was disabled. I enabled it and the server instance started working again.

    Thanks, this post helped me get somewhere near the solutuion.

  73. Nitin says:

    It worked for me.

    Keep continuing the good work!

  74. pixelmeow says:

    Disabled VIA. That did it. Thanks!

  75. deepak says:

    Thank you very much ..that helped

  76. Kaushal says:

    Hey… that solved the issue in a snap!!

  77. don says:

    disabling VIA protocol works…thanks a lot

  78. THANKYOU says:

    i spend one week in this problem…. but now i know the solution… it´ss working… thank you very much!

  79. Bogdan says:

    What started:…..

    The sql server (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………….

    got to this point where VIA should Disabled.

    Great post!

    It solved the problem of starting MSSQLSERVER (sqlservr.exe).

    Luckily, I ran sqlservr from command prompt and it showed me some of the error above.

    Thanks again!

  80. Marlon says:

    I disabled TCP IP instead and it worked.

    The cause of our problem is the administration removed SQL Server cluster resource and then add it again manually.  The registry entries were also removed.

  81. anushka says:

    Hi

    Please clarify how enabling via protocol is the reason of above failure

    thanks

  82. SQL Protocols says:

    Enabling the VIA protocol in SQL Server will usually cause failures for a combination of two reasons:

    1) SQL Server does not allow the server to start up if it fails to listen on a protocol specified by the user.

    2) The VIA protocol is tied to specialized hardware (if you have VIA NICs, you bought them intentionally and know that you have it; it’s not common by any stretch).

    Hence, when you enable VIA for SQL Server, since you probably don’t have the required hardware, SQL Server fails to listen on the VIA nic (since it doesn’t find one), and this causes the startup to fail with the above error.

    Hope this clarifies!

  83. Jitendra Kumar Singh says:

    I Just gone to config. manager and disabled VIA and wao its working

  84. Krzysztof says:

    Thanks a lot! Saved a lot of time!

  85. Karl says:

    I Get the following:

    2009-12-29 13:14:52.56 spid11s     Starting up database ‘model’.

    2009-12-29 13:14:52.57 Server      Error: 17182, Severity: 16, State: 1.

    2009-12-29 13:14:52.57 Server      TDSSNIClient initialization failed with error 0xd, status code 0x38. Reason: An error occurred while obtaining or using the certificate for SSL. Check settings in Configuration Manager. The data is invalid.

    2009-12-29 13:14:52.58 spid7s      Informational: No full-text supported languages found.

    2009-12-29 13:14:52.60 Server      Error: 17182, Severity: 16, State: 1.

    2009-12-29 13:14:52.60 Server      TDSSNIClient initialization failed with error 0xd, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. The data is invalid.

    2009-12-29 13:14:52.62 Server      Error: 17826, Severity: 18, State: 3.

    2009-12-29 13:14:52.62 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-12-29 13:14:52.64 Server      Error: 17120, Severity: 16, State: 1.

    2009-12-29 13:14:52.64 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.

  86. Ram says:

    Thanks a lot. Your solution worked very well.

  87. Ven says:

    Thanks a million. You’re a savior!

  88. Abhay lolekar says:

    Was of great help thanks a lot

  89. sureshvc says:

    I tried disabling VIA, but on restart, it gets enabled and SQL fails to start. I tried to failover with disabled and tried to start, but still it fails and enables VIA back.

    Any reasons why this happens and where to check?

    Thanks,

    Suresh

  90. SQL Protocols says:

    On a Failover Cluster Instance, where registry checkpointing is present, specific steps are required to make a change to these settings. This KB article describes how to make the change and even includes an example of changing the Via setting: http://support.microsoft.com/kb/953504

  91. sureshvc says:

    Thank You!. Method 1.. worked from this article you mentioned above.

    Thank you!

  92. Raul says:

    Do you have SQL 2000 running side-by-side with SQL 2005???!!

    I got the following errors in the Windows Event Log:

    Server TCP provider failed to listen on [ ‘any’ <ipv4> 1433]. Tcp port is already in use.

    TDSSNIClient initialization failed with error 0x2740, status code 0xa.

    TDSSNIClient initialization failed with error 0x2740, 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.

    How I fixed it:

    I read most of the comments in this blog and confirmed it wasn’t an issue with the VIA protocol (it was disabled already).  But in one of the comments somebody said something about a possible collision which got me to thinking that there was a SQL Server 2000 instance running on this box!  So, (since we’re no longer using SQL 2000) I manually stopped the MSSQLSERVER service and retried starting the SQL 2005 service and it worked!  VERY IMPORTANT OR THIS PROBLEM WILL COME BACK – modify the StartupType to be Disabled (just in case this box reboots).

    Hope this helps!

  93. perfect, thanks a lot. don't know why but tcp-ip was disabled.

  94. wilver says:

    nice one guys..it works for..thanks.

  95. TrevorF says:

    Got this error message

    2010-07-28 10:19:43.87 spid5s      Starting up database 'mssqlsystemresource'.

    2010-07-28 10:19:43.90 spid5s      The resource database build version is 9.00.3077. This is an informational message only. No user action is required.

    2010-07-28 10:19:44.02 spid8s      Starting up database 'model'.

    2010-07-28 10:19:44.02 Server      Error: 17182, Severity: 16, State: 1.

    2010-07-28 10:19:44.02 Server      TDSSNIClient initialization failed with error 0x5, status code 0x51.

    2010-07-28 10:19:44.02 Server      Error: 17182, Severity: 16, State: 1.

    2010-07-28 10:19:44.02 Server      TDSSNIClient initialization failed with error 0x5, status code 0x1.

    2010-07-28 10:19:44.02 Server      Error: 17826, Severity: 18, State: 3.

    2010-07-28 10:19:44.02 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-07-28 10:19:44.02 Server      Error: 17120, Severity: 16, State: 1.

    2010-07-28 10:19:44.02 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.

  96. ebead says:

    thanxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

  97. Serge Tche says:

    I had "TDSSNIClient initialization failed with error 0x2, status code 0xd".

    I went to SQL Server Configuration Manager->SQL2005 NetConfig->Protocols->TCP/IP and saw that Status was Disabled. I tried to enable it but got an error message that the protocol would be enabled at the next startup. Another strange thing that I noticed was that TCP/IP Properties->General didn't show me all the parameters.

    Then I went to Regedit and compared the keys with the healthy instance of SQL 2005 on my other server. I don't know why but I had some keys missing. The keys must be:

    [HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL ServerMSSQL.1MSSQLServerSuperSocketNetLibTcp]

    "ListenOnAllIPs"=dword:00000001

    "NoDelay"=dword:00000000

    "KeepAlive"=dword:00007530

    "DisplayName"="TCP/IP"

    "Enabled"=dword:00000001

    After the keys had been added I saw that TCP/IP Status changed to Enabled, and the error become "TDSSNIClient initialization failed with error 0x2, status code 0x10". TCP/IP Properties->IP Addresses showed me IP1 and IP2 parameters, but didn't show IPALL. So another portion of keys was added:

    [HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL ServerMSSQL.1MSSQLServerSuperSocketNetLibTcpIPAll]

    "DisplayName"="Any IP Address"

    "TcpDynamicPorts"=""

    "TcpPort"="1433"

    It was the cure.

    Good luck!

  98. Smalto says:

    Disable TCP/IP, restart your Service and then enable TCP/IP again…

  99. Boon says:

    There is no port number under IP ALL in TCP / Ip Protocol.

    I have added it and SQL Services started successfully

  100. saif says:

    this my error log plz help me i searched alot but not having solve able solution….:-(

    2012-06-04 11:52:35.60 Server      Microsoft SQL Server 2008 R2 (RTM) – 10.50.1600.1 (Intel X86)

    Apr  2 2010 15:53:02

    Copyright (c) Microsoft Corporation

    Developer Edition on Windows NT 5.1 <X86> (Build 2600: Service Pack 3)

    2012-06-04 11:52:35.60 Server      (c) Microsoft Corporation.

    2012-06-04 11:52:35.60 Server      All rights reserved.

    2012-06-04 11:52:35.60 Server      Server process ID is 4076.

    2012-06-04 11:52:35.60 Server      Authentication mode is WINDOWS-ONLY.

    2012-06-04 11:52:35.60 Server      Logging SQL Server messages in file 'C:Program FilesMicrosoft SQL ServerMSSQL10_50.MSSQLSERVERMSSQLLogERRORLOG'.

    2012-06-04 11:52:35.60 Server      This instance of SQL Server last reported using a process ID of 2520 at 6/4/2012 11:37:47 AM (local) 6/4/2012 6:37:47 AM (UTC). This is an informational message only; no user action is required.

    2012-06-04 11:52:35.61 Server      Registry startup parameters:

    -d C:Program FilesMicrosoft SQL ServerMSSQL10_50.MSSQLSERVERMSSQLDATAmaster.mdf

    -e C:Program FilesMicrosoft SQL ServerMSSQL10_50.MSSQLSERVERMSSQLLogERRORLOG

    -l C:Program FilesMicrosoft SQL ServerMSSQL10_50.MSSQLSERVERMSSQLDATAmastlog.ldf

    2012-06-04 11:52:35.62 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.

    2012-06-04 11:52:35.62 Server      Detected 1 CPUs. This is an informational message; no user action is required.

    2012-06-04 11:52:35.82 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.

    2012-06-04 11:52:35.89 Server      Node configuration: node 0: CPU mask: 0x00000001:0 Active CPU mask: 0x00000001:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.

    2012-06-04 11:52:35.97 spid7s      Starting up database 'master'.

    2012-06-04 11:52:36.17 spid7s      Resource governor reconfiguration succeeded.

    2012-06-04 11:52:36.17 spid7s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.

    2012-06-04 11:52:36.17 spid7s      SQL Server Audit has started the audits. This is an informational message. No user action is required.

    2012-06-04 11:52:36.20 spid7s      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.

    2012-06-04 11:52:36.26 spid7s      SQL Trace ID 1 was started by login "sa".

    2012-06-04 11:52:36.26 spid7s      Starting up database 'mssqlsystemresource'.

    2012-06-04 11:52:36.28 spid7s      The resource database build version is 10.50.1600. This is an informational message only. No user action is required.

    2012-06-04 11:52:36.57 spid7s      Server name is 'SAIF-22DAE269EB'. This is an informational message only. No user action is required.

    2012-06-04 11:52:36.59 spid10s     Starting up database 'model'.

    2012-06-04 11:52:37.32 spid10s     Clearing tempdb database.

    2012-06-04 11:52:38.15 Server      The server could not load the certificate it needs to initiate an SSL connection. It returned the following error: 0x80090008. Check certificates to make sure they are valid.

    2012-06-04 11:52:38.16 Server      Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.

    2012-06-04 11:52:38.17 Server      Error: 17182, Severity: 16, State: 1.

    2012-06-04 11:52:38.17 Server      TDSSNIClient initialization failed with error 0x80090008, status code 0x80. Reason: Unable to initialize SSL support. Invalid algorithm specified.

    2012-06-04 11:52:38.18 Server      Error: 17182, Severity: 16, State: 1.

    2012-06-04 11:52:38.18 Server      TDSSNIClient initialization failed with error 0x80090008, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Invalid algorithm specified.

    2012-06-04 11:52:38.20 Server      Error: 17826, Severity: 18, State: 3.

    2012-06-04 11:52:38.20 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.

    2012-06-04 11:52:38.20 Server      Error: 17120, Severity: 16, State: 1.

    2012-06-04 11:52:38.20 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.

  101. Rajendra says:

    Thanks a lot. It resolved my problem.

  102. Irfan says:

    Excellent…

    that fixed the problem.

    Thank you

  103. Saran Kumar says:

    This issue is due to improper load of SSL certificate from the cert store and registry  . To solve this issue and bring up the SQL service ONLINE  , need to remove the cluster CRYPTOGRAPHIC checkpoints alone through Command Prompt ( Incase of windows server 2008R2) or through Powershell ( Incase of windows  2012 ) .  I have pasted the detailed STEPS for windows 2012

    Note : It will ask to remove checkpoints for other cluster features , Pls give NO . This is to remove checkpoints only for CRYPTOGRAPHIC checkpoints . This will definitely bring the service up .

    To import cluster objects to Powershell

    PS C:Windowssystem32> Import-module Failovercluster

    Help Command in Powershell:

    PS C:Windowssystem32> get-help clusterresource

    Name                              Category  Module                    Synopsis

    —-                              ——–  ——                    ——–

    Add-ClusterResource               Cmdlet    FailoverClusters          …

    Add-ClusterResourceDependency     Cmdlet    FailoverClusters          …

    To View the Cluster resources:

    PS C:Windowssystem32> get-clusterresource

    Name                          State                         OwnerGroup                    ResourceType

    —-                          —–                         ———-                    ————

    Analysis Services             Online                        SQL Server (MSSQLSERVER)      Generic Service

    Cluster Disk 1                Online                        SQL Server (MSSQLSERVER)      Physical Disk

    Cluster Disk 2                Online                        SQL Server (MSSQLSERVER)      Physical Disk

    PS C:Windowssystem32> get-clusterresource "SQL Network Name (“SQL SERVER NAME”)"

    Name                          State                         OwnerGroup                    ResourceType

    —-                          —–                         ———-                    ————

    SQL Network Name (USCULRMI… Online                        SQL Server (MSSQLSERVER)      Network Name

    To remove Cryptographic  details from Registry:

    Execute the below query,

    PS C:Windowssystem32> Get-ClusterResource "SQL Network Name (“SQL SERVER NAME”)"|remove-clustercheckpoint -"SoftwareMic

    rosoftMicrosoft SQL ServerMSSQL11.MSSQLSERVERMSSQLSERVER"

  104. Bheemanna.K says:

    Thanks lot all

    Issue solved after Disable the VIA