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

Artikel
10/30/2005

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: https://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

Anonymous
November 29, 2005
Great help...worked smoothly !

thanks
Anonymous
December 01, 2005
The comment has been removed
Anonymous
December 01, 2005
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
Anonymous
January 06, 2006
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
Anonymous
February 26, 2006
Exactly what I was looking for !
Thanks a lot.

Regards,
Julia
Anonymous
March 01, 2006
Thanks for your help. This work great !!
Anonymous
March 01, 2006
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.
Anonymous
March 12, 2006
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
Anonymous
March 12, 2006
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.
Anonymous
March 13, 2006
Srini,
Please post a complete errorlog including 17120, 17182 and 17826....
Anonymous
March 13, 2006
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.
Anonymous
March 16, 2006
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.
Anonymous
March 16, 2006
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
Anonymous
April 03, 2006
"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.
Anonymous
April 03, 2006
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
Anonymous
April 10, 2006
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.
Anonymous
April 10, 2006
Sorry!! False alarm. I thought I had disabled VIA but in fact hadn't. Once I did the problem was fixed. Thanks a bunch.
Anonymous
April 17, 2006
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.
Anonymous
April 18, 2006
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
Anonymous
April 22, 2006
Thank you.:}
Anonymous
April 27, 2006
SQL Server 2005 could fail to bring up due to various causes, there are several great blogs that talk...
Anonymous
June 06, 2006
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
Anonymous
June 07, 2006
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.
Anonymous
August 23, 2006
Thanks for the quick fix .
Anonymous
November 19, 2006
Thanks a lot. The solution worked well.
Anonymous
November 30, 2006
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.
Anonymous
January 11, 2007
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.
Anonymous
February 02, 2007
it worked fine for me big thanks
Anonymous
February 28, 2007
Excellent! Worked perfectly...once you get out of the "Client Network Protocols" tree!
Anonymous
April 30, 2007
Its Working great!! Cool solution Thanks. Ashok
Anonymous
May 08, 2007
That fix worked! I've been pulling my hair out over this one. Thanks!
Anonymous
May 22, 2007
This worked fine for the sql server 2005 service. Thanks!
Anonymous
May 30, 2007
Great!! Thanks a lot...worked for me
Anonymous
October 08, 2007
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.
Anonymous
October 12, 2007
Great, great help !!! Extremely helpful
Anonymous
October 24, 2007
Yes turning off VIA and restarting the service worked for me as well.. Many thanks, Jason
Anonymous
November 15, 2007
if you run sql 2005 with sqlexpress stop sqlexpress, and turn of VIA then restart service...
Anonymous
January 02, 2008
I have tried it but still not able to start sql server 2005
Anonymous
January 03, 2008
Post back with the exact error lines from the errorlog, you may have a different status code.
Anonymous
January 15, 2008
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?
Anonymous
January 15, 2008
brilliant advice, just spent 2 hours trying everything else
Anonymous
March 18, 2008
It Worked Very well, Thanks, Something so simple, can actually seem to give so many complication's. Thanks.
Anonymous
April 14, 2008
WOW! Thank you so much. That fixed my problem!
Anonymous
April 14, 2008
Thank u for your kindness and erudition.
Anonymous
May 15, 2008
thank you very much that i lerned something and solved my problem.
Anonymous
May 26, 2008
I got the above error, I have tried the above solution but it does not work, please help
Anonymous
May 29, 2008
I am getting same error when i try to connect to sql server in a virtual machine... protocols are ok ,,any idea>??
Anonymous
June 04, 2008
VIA protocol was it.. thanks for the help !!
Anonymous
June 27, 2008
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
Anonymous
June 27, 2008
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
Anonymous
July 01, 2008
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
Anonymous
July 02, 2008
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
Anonymous
August 04, 2008
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.
Anonymous
August 04, 2008
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.
Anonymous
August 14, 2008
Muito Obrigado!! Thanks!!!!
Anonymous
August 27, 2008
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?
Anonymous
August 27, 2008
The comment has been removed
Anonymous
September 08, 2008
Yeah!!!! That's exactly what I need!!! Thank you,Vaughn! Thank you!!!
Anonymous
September 15, 2008
Thanks! It was the VIA protocol. VALEEUU!!
Anonymous
September 16, 2008
The comment has been removed
Anonymous
September 30, 2008
It worked for me. Thanks A Lot :-)
Anonymous
October 07, 2008
it is coming up with this: General protection fault! History: Address = 0x10918b0b (filename not found) Address: = 0xd (filename not found)
Anonymous
October 07, 2008
sorry can you help please thank you
Anonymous
October 19, 2008
The comment has been removed
Anonymous
October 21, 2008
The comment has been removed
Anonymous
November 30, 2008
Thank you very much!! This has been a very effective solution. It works very well. Thank you again.
Anonymous
January 13, 2009
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.
Anonymous
January 21, 2009
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.
Anonymous
March 21, 2009
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.
Anonymous
April 05, 2009
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.
Anonymous
April 08, 2009
Thanks buddy it solved the problem
Anonymous
April 20, 2009
Thanks a lot .This worked for me.
Anonymous
April 27, 2009
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.
Anonymous
May 07, 2009
It worked for me. Keep continuing the good work!
Anonymous
June 08, 2009
PingBack from http://hairgrowthproducts.info/story.php?id=4431
Anonymous
June 09, 2009
PingBack from http://jointpainreliefs.info/story.php?id=305
Anonymous
June 16, 2009
PingBack from http://topalternativedating.info/story.php?id=11829
Anonymous
July 02, 2009
Disabled VIA. That did it. Thanks!
Anonymous
July 22, 2009
Thank you very much ..that helped
Anonymous
August 07, 2009
Hey... that solved the issue in a snap!!
Anonymous
August 12, 2009
disabling VIA protocol works...thanks a lot
Anonymous
September 14, 2009
i spend one week in this problem.... but now i know the solution... it´ss working... thank you very much!
Anonymous
October 22, 2009
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!
Anonymous
October 27, 2009
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.
Anonymous
October 31, 2009
Hi Please clarify how enabling via protocol is the reason of above failure thanks
Anonymous
November 02, 2009
Enabling the VIA protocol in SQL Server will usually cause failures for a combination of two reasons:

SQL Server does not allow the server to start up if it fails to listen on a protocol specified by the user.
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!

Anonymous
November 08, 2009
I Just gone to config. manager and disabled VIA and wao its working
Anonymous
November 17, 2009
Thanks a lot! Saved a lot of time!
Anonymous
December 28, 2009
The comment has been removed
Anonymous
January 18, 2010
Thanks a lot. Your solution worked very well.
Anonymous
February 15, 2010
Thanks a million. You're a savior!
Anonymous
March 13, 2010
Was of great help thanks a lot
Anonymous
April 08, 2010
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
Anonymous
April 08, 2010
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
Anonymous
April 08, 2010
Thank You!. Method 1.. worked from this article you mentioned above. Thank you!
Anonymous
April 22, 2010
The comment has been removed
Anonymous
May 24, 2010
perfect, thanks a lot. don't know why but tcp-ip was disabled.
Anonymous
July 20, 2010
nice one guys..it works for..thanks.
Anonymous
July 27, 2010
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.
Anonymous
October 03, 2010
thanxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Anonymous
October 28, 2010
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!
Anonymous
November 22, 2010
Disable TCP/IP, restart your Service and then enable TCP/IP again...
Anonymous
December 01, 2010
There is no port number under IP ALL in TCP / Ip Protocol. I have added it and SQL Services started successfully
Anonymous
June 03, 2012
The comment has been removed
Anonymous
May 04, 2014
Thanks a lot. It resolved my problem.
Anonymous
June 04, 2014
Excellent... that fixed the problem. Thank you
Anonymous
July 13, 2014
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"
Anonymous
December 26, 2014
Thanks lot all Issue solved after Disable the VIA

Freigeben über

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

Comments

Zusätzliche Ressourcen