transport-level error

Question

transport-level error

Mike Levan

SSChampion

Points: 14201
More actions
March 5, 2009 at 7:55 pm

#135266

A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)
I get this error very often only for some users not for all. they complain saying that all there work is lost when it gets diconnected and also fwd the issue to network admin but evrything looks good at their side. I still dont understand if this is something i can fix from sql server or its pure network issue.
thanks

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

Mohit K. Gupta SSChampion Points: 12130 More actions · Answer 1

Hi Mike,

Something/someone is killing their SQL Server connections, eg "kill spid" or right clicking in activity monitor going kill connection. Are they connecting to a cluster environment? If the cluster had a failover while they are working it will kill their connection from the node they were connected to and give a similar message.

Mohit.

[font="Arial"]---

Mohit K. Gupta, MCITP: Database Administrator (2005), My Blog, Twitter: @SQLCAN[/url].
Microsoft FTE - SQL Server PFE

* Some time its the search that counts, not the finding...
* I didn't think so, but if I was wrong, I was wrong. I'd rather do something, and make a mistake than be frightened and be doing nothing. :smooooth:[/font]

How to ask for help .. Read Best Practices here[/url].

MANU-J. SSC-Dedicated Points: 31126 More actions · Answer 2

Please do check sql server error logs and event viewer logs for any errors. As another poster has posted "check for any service restart".

MJ

Mike Levan SSChampion Points: 14201 More actions · Answer 3

I think only sysadmin kill any connection (spid) am i right? how can i track who killed the conenction at that time. Actually the user conencted to a remote server and accessing the database from there.

Also i dont see any lof at that time under sql server > Mgmt > SqlSErver Logs. I s there anywhere else i can find that information.

thanks

TRACEY-320982 SSChampion Points: 13653 More actions · Answer 4

If the application uses IIS WEB Server could have IIS timeout that has been meet that can produce this error .

If using ODBC then could have time out on that application server.

In our applications if uses don't use for 30 minutes it logs them out or disconnects them...

Mike Levan SSChampion Points: 14201 More actions · Answer 5

I dont have any applications running and this happens when the user directly connects to sql server and exec query from query window from the remote host. All my sql servers are set for timeout=0.

MANU-J. SSC-Dedicated Points: 31126 More actions · Answer 6

From-->http://blogs.msdn.com/sql_protocols/archive/2005/12/22/506607.aspx

Error Message 2:

A connection was successfully established with the server, but then an error occurred during the pre-login handshake. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 0 - No process is on the other end of the pipe.)

1) You might explicitly use "np:"prefix which ask for connect through named pipe and specify FQDN/LoopbackIP/IPAddress as server name in the connection string.

2) You might use FQDN/IPAddress/LoopbackIP to connect to the server.

To resolve 1) and 2), you can specify instead of FQDN/IPADress/LoopbackIP.

MJ