A transport-level error has occurred when sending the request to the server

A transport-level error has occurred when sending the request to the server

Share on Facebook0Share on Google+0Tweet about this on TwitterShare on LinkedIn0Share on Reddit0
This post’s purpose is to explain the above connectivity error and ways of resolving it.

In some cases (upon “wrong” actions or network problems ๐Ÿ™‚ we might get the following error in SQL Server:

A transport-level error has occurred when sending the request to the server. (provider: Shared Memory Provider, error: 0 – No process is on the other end of the pipe.)

As the error message indicates, there is a connectivity problem with a previously opened session in SQL Server.

As an example, consider that you have a query window opened. This query window is connected to a database (the default database is “master”). To this end, there is an established connection to that database, that is a session. At a lower level in SQL Server, there is an spid representing this session.

If this spid is forcibly terminated (i.e. by using the SQL Server KILL function, or after an unexpected network problem) and though you are still trying to use this session (i.e. execute a query) you will most probably get the above connectivity error.

A solution in this case, is to close the query window and open a new one. To this end a new session will be opened and will be assigned a new spid. After that, you will be able to use the database properly.

The above connectivity error might arise not only when using the query window, but other SQL Server services that might access SQL Server objects as well. It is a general connectivity error and the best solution for resolving it is to start a new session in order for the connectivity to the specific SQL Server object(s) to be restored/re-initiated.


My Latest Projects:



Recommended eBooks on SQL Server:

Tuning SQL Server: eBook by SQL Server MVP Artemakis Artemiou
Tuning SQL Server: eBook by SQL Server MVP Artemakis Artemiou
Administering SQL Server: eBook by SQL Server MVP Artemakis Artemiou
Administering SQL Server: eBook by SQL Server MVP Artemakis Artemiou
Artemakis Artemiou
Artemakis Artemiou is a Senior SQL Server Architect, Author, Software Developer and a Microsoft Data Platform MVP. He has over 15 years of experience in the IT industry in various roles. Among other, via his initiative SQLEBooks.com, Artemakis authors and publishes eBooks on different topics on SQL Server. Artemakis currently serves as the President of the Cyprus .NET User Group (CDNUG) and the International .NET Association Country Leader for Cyprus (INETA). Additionally he is the founder of the SQLArtBits initiative that aims to provide the technical community with simple, yet powerful and high-quality SQL Server tools. Currently, the highlights of these tools are DBA Security Advisor and In-Memory OLTP Simulator. Artemakis's official website can be found atย aartemiou.com. Artemakis's blogs can be found at: SQLNetHub.comย and TechHowTos.com.

One thought on “A transport-level error has occurred when sending the request to the server

  1. Thomas Gagne

    Our application has 12 clients posting transactions to the DB. In the middle of an otherwise eventless run, multiple of the clients will begin getting the transport-level error.

    This error suggests a fairly fragile network library for SqlServer.

    Curiously, without closing and opening a new connection the transactions eventually start working again.

    I've been Googling around looking to see if Microsoft is aware of this problem and if there's any official recommendation or patch.

    Of course, other times it works without a hiccup.