Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.

Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.

• Jerome Le Bateau

  yaah!!!! i have done same and it worked.. but after opening 5 or 6 connection, m getting the same error message again.....

  Cheers!!

  
  

• CamDen

  After a while like 5 hours that I tried to solve this problem Thanks Lane I found your post... & Now it works
  

• PlasticLizard

  Not sure if you have resolved this or not.  I had the same error trying to connect to a new SQL Server 2005 installation with the management studio from a remote machine and discovered that the named pipes protocol was diasabled in the SQL Server network configuration protocols.  I enabled it and restarted SQL Server and the problem was resolved.

  Good Luck

  Lane

  
  

• skier17

  Try and connecting to the SQL Server box using the DAC (Dedicated Admin Connection) e.g if your server name is "SERVER" enter "ADMIN:Server" in Server name and click connect.
  

• arndawg

  I spent a couple hourse working on this issue until i realised my SQL Server Agent Was stopped. It wasn't set to auto start to reboots didn't help. Oddly all my win32 apps would work fine and asp.net apps running from other machines could get the SQL data but a asp.net 2.0 app running off localhost would throw this error.

  Ben

  
  

• lasher999

  I received this error after dropping connections while detaching a database. I restarted the SQL server service as well as agent and IIS. nothing seemed to fix it. I then logged into SQL Server under another admin login. I looked at the properties under my usual login and found that the default database was not set, which seemed strange. I reset the default database and logged back in under my account. Not quite sure what SQL Server did, but now it's fixed.
  

• Tim T

  reboot your db server...
  
  

• jettman

  execute sp_configure and increment the conexion

  
  
  

• Todd Wilder

  This error usually indicates that the server closed the connection, e.g. during login verification. 

  The best is to check for any messages from SQL Server correlated to the time of the failure - either in the Application EventLog or in the ERRORLOG file (by default located in the C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG directory).  There is a chance they provide more information to identify the root cause of the failure. 

   

   

  
  
  

• Kaa

  Did not see any weird error message may cause this problem.
  

• Ludy

  Another mistake that can cause this error is incorrect credentials in a connection string.
  

• ZeBobo5

  The reason this message appears is because of the web.config connectionString. Rather than using the default authentication details of Integrated Security=True:

  connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;Integrated Security=True"

  Use "User ID=sa Password=test" for example in the connection string:

  connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;User ID=sa Password=test"

  Rod Copeland

  
  

• Scott Francis McGrath

  I enable the Protocols "Named Pipes" and it works.

  Thanks Lane.

  
  

• HIRU

  I checked the SQL Server log (message 2 above) and realised there were too many connections opened. The error description was verbose. Closed them and it worked.

  Cheers

  
  
• Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.