StephK


Hello,

Please bear with me as I am no Sql Server guru, but am getting this error that is preventing me from continuing with my development work.  I am the only developer on my team running Sql Server 2005 and it has been working just fine for the last week.  I opened the Management Studio this morning, just like every other morning and got this error:

TITLE: Connect to Server
------------------------------

Cannot connect to (local).

------------------------------
ADDITIONAL INFORMATION:

A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) (Microsoft SQL Server, Error: 233)

Of course the help page says no help is available.  I have googled myself sick and still have not found a way so resolve this...has anyone else had this error and/or a fix   I am using XP Pro SP2...any help would be greatly appreciated!

Thanks!
Steph




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

Peter Gvozdjak


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. 

 

 







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

Hardy

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




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

brokenrulz

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.



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

LaneH

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





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

ta2

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





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

king kailas

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

Cheers!!





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

Mike Wentzel

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



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

PabloL

execute sp_configure and increment the conexion






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

JinTao

reboot your db server...




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

fewfewfew

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





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

BSautner

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





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

Alexcl

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

Thanks Lane.





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

OmLeD

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



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

S_Gibson

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.