26

Possible Duplicate:
A transport-level error has occurred when receiving results from the 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.)

We are getting the following error message appearing intermittently on our server. We are running a asp.net 4 web application with SQL Server 2008 database. Has anyone ever come across this error message and a solution to stop this happening.

The strange thing is this issue was not occurring on our dev system and we are finding it very difficult to replicate due to the sporadic nature of this issue.

Still have not found a solution to this issue.

Community
  • 1
  • 1
Matt Seymour
  • 8,880
  • 7
  • 60
  • 101

2 Answers2

24

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

Try:

SqlConnection.ClearAllPools();

SqlConnection.ClearAllPools Method resets (or empties) the connection pool. If there are connections in use at the time of the call, they are marked appropriately and will be discarded (instead of being returned to the pool) when Close is called on them.

Akram Shahda
  • 14,655
  • 4
  • 45
  • 65
  • yeah i've had this before when i delete a dev database while the website is running and recreate it and forget to restart the website and the website is using the old sql session – Daniel Powell Jun 30 '11 at 12:52
4

Yes, I have a few times actually. Very very irratating error. If I'm not mistaken had something to do with Named Pipes instead of Shared Memory being used.

Please take a look at the following links should help you sort out the isse.

Link 1 Link 2

Jethro
  • 5,896
  • 3
  • 23
  • 24
  • Thanks @jethro I looked at the web.config file and we are making use of 'localhost' I think i might give '(local)' a try to see if this makes any difference. – Matt Seymour Jun 30 '11 at 12:04
  • No, you actually have to look at sql server. Go to SQL Server = > Configuration Tools => Sql server configuration Manger and you need to look at what sql is using there. – Jethro Jun 30 '11 at 12:07