SQL Protocols

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

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.

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.  

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

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.

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

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.

Thank you.:}

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

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

Thanks for the quick fix .

Thanks a lot. The solution worked well.

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.

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.

it worked fine for me

big thanks

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

Its Working great!! Cool solution Thanks.

Ashok

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

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

Great!! Thanks a lot...worked for me

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.

Great,  great  help !!!   Extremely   helpful

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

Many thanks, Jason

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

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

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

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?

brilliant advice, just spent 2 hours trying everything else

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

Thanks.

WOW!

Thank you so much.

That fixed my problem!

Thank u for your kindness and erudition.

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

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

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

:)

It worked for me.

Thanks A Lot :-)

it is coming up with this:

General protection fault!

History: Address = 0x10918b0b (filename not found)

Address: = 0xd     (filename not found)

sorry

can you help please

thank you

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.

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

Thank you very much!!

This has been a very effective solution.

It works very well.

Thank you again.

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.

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.

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.

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.

Thanks buddy it solved the problem

Thanks a lot .This worked for me.

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.

It worked for me.

Keep continuing the good work!

PingBack from http://hairgrowthproducts.info/story.php?id=4431

PingBack from http://jointpainreliefs.info/story.php?id=305

PingBack from http://topalternativedating.info/story.php?id=11829

Disabled VIA. That did it. Thanks!

Thank you very much ..that helped

Hey... that solved the issue in a snap!!

disabling VIA protocol works...thanks a lot

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

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!

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.

Hi

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

thanks

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

Thanks a lot! Saved a lot of time!