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:
Labels: SQL Server, SQL Server Administration, SQL Server Troubleshooting