Home » Visual StudioRSS

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

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

 

53 Answers Found

 

Answer 1

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.     
 

Answer 2

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

Answer 3

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.
 

Answer 4

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
 

Answer 5

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

 

Answer 6

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

Cheers!!

 

Answer 7

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

Answer 8

execute sp_configure and increment the conexion

 

Answer 9

reboot your db server...
 

Answer 10

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

 

Answer 11

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

 

Answer 12

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

Thanks Lane.

 

Answer 13

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

Answer 14

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.
 

Answer 15

Hi!

I experience same error  message.
I have an asp application that works with a DB. The database is mirrored. At the beginning the database worked with windows authentication. Also IIS paths requests from the application with specially created user. The user was also added to the DB (in login and users). My connectionStrings element in the application was configured to work  with SSPI.
Now I need to did a next change: I want to work with sql  authentication. Do do it I create new login and user that works with  the DB. I also  change connectionStrings to add user and password and remove  SSPI.
Now I run the application. It works perfect, but if I do a failover between mirrored DBs I've go next error:
"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.)"

Now if I run create of login and user for the DB. And than I run application once again it works well.

Any help?
 

Answer 16

I'm having the same problem.  The Named Pipes support is disabled, but when I enable it, I get a timeout error.  Has anyone any idea about what may be happening?

Thanks in advance,

Monique

 

Answer 17

thanks it works when enable "namedPipes" protocols

 

Answer 18

Open the SQL Server Configuration Manager. Expand the Network configuration and enable the Shared Memory and Named Pipes, see to it the other 2 protocols TCP/IP and VIA are disabled. The same is to be done in Client configuration in client protocol section.

I was getting the same error  and i tried this and the error went off. Hope this helps.

Regards

Jolly bzach

 

Answer 19

i have this same problem

when the name pipes was enable thwe connection  is timeout

any one could help???

 

Answer 20

Disable Shared memory  protocol and try !....

 

Answer 21

One of the most common reasons for this error  is that SQL authentication is not enabled on the instance that you are logging into. Enable Sql Authentication, Restart the Instance and it should go away!

 

Answer 22

Check your SQL Native Client Configuration in Computer Management. Check to see if there are any Aliases under Client Protocols. If there are Aliases with the name of the SQL server  you try to connect, delete them. It works.
 

Answer 23

-------------------------------

ASP.Net 2.0 Application

SQL server  2005

Clients have a mix of IE6 and IE6

-------------------------------

My users reported this error. I checked the Event Log on the server and it gave the following message:

Could not connect because the maximum number of '5' user connections has already been reached. The system administrator can use sp_configure to increase the maximum value. The connection  has been closed. [CLIENT: <local machine>]

The ASP.Net application gave this error  message in IE:

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.)

I had everyone disconnect so I could, then ran this statement in SQL Server Mgmt Studio:

sp_configure 'user connections', 25

reconfigure with override

 

Answer 24

My issue was with the connection  strings was limited.  Try connecting with only one query (be sure to disconnect from all other connections to the SQL server), then run the following script:

EXEC sys.sp_configure N'show advanced options', N'1'RECONFIGUREWITHOVERRIDE

GO

EXEC sys.sp_configure N'user connections', N'0'

GO

RECONFIGUREWITHOVERRIDE

GO

EXEC sys.sp_configure N'show advanced options', N'0'RECONFIGUREWITHOVERRIDE

GO

The problim seems to have multipule causes, but one of the causes is that a limited number of connections to the SQL database has been set.  This script will set it back to 0 which is unlimited.  This setting can be found by right clicking on the server  the click Properties - Connections.  This script will allow you to reset that setting even if you can't get that far through the Object Explorer. 

* Note: Be sure to disconnect from the server in Object Explore so you can run this script.

 

Answer 25

Could you please share the steps you did to enable "named pipes protocol in SQL Server network configuration protocols?"

Thanks!

 

Answer 26

I found how to enable the NP but got the new error  message:

Login failed for user 'sa'. The user is not associated with a trusted SQL Server connection. (Microsoft SQL Server, Error: 18452)

 

Answer 27

Ryan - Thanks for the script and instructions on resetting connections back to "0" - but remember that you need to restart SQL services for it to take efffect. 

It worked for me!  Thanks!

 

Answer 28

I'm new to the forum, but i found a way to actually see the connections.  In SQL Managment Studio under the database server  name expand the management tree and open the Activey Monitor.  It will then display the active connections.  I was having the same problem during development  testing and sure enough i was trying to open more than 10 connections.

 

Answer 29

How was the named pipes enabled. Was this through the connect string code or is this a setting in SQLExpress

 

Answer 30

goto sql  server configuration manager.  it's under SQL server2005 Network configuration- protocols for (your sqlengine)

 

Answer 31


I had the same problem. I try to connect to SQL server  using "Management Studio Express" from another computer.
So i solved the problem. Here are steps:


1) Start->Programs-> Microsoft SQL Server 2005 -> Configuration Tools-> SQL Server Surface Area Configuration
2) Run "Surface Area Configuration for Services and Conections"
3) In the tree Select "Remote Connections" and then select "Using named pipes only".
4) Look at Start->Programs-> Microsoft SQL Server 2005 -> Configuration Tools->SQL Server Configuration Manager
5) In the tree select "SQL Server 2005 Network Configuration->Protocols for SQL..." All protocols must be Disabled, but Named Pipes -- Enabled.

Don't forget to restart server.
 

Answer 32

I found using SQL server  Management Studio Express that my newly installed SQL server was set to Windows Authentication only, so I set it to both Windows Authentication and SQL login.

 

Answer 33

After restarting the services, able to connect the SQL server  from Client machines. thanks

 

Answer 34

This issue was posted long time ago, and many people replied with their own solutions including connection  strings of the apps. This is my case and I think Steph experienced exactly same as mine.

My ASP.Net app can connect and access to the database, but Management Studio gives the error  expained by Steph. My solution was...

Start>SQL server  2005>Configuration Tools>Surface Area Configuration>Add New Administrator

Then add available privileges.

HTH

 

Answer 35

I have the same errror. I try to change the connectionString: ...Data Source=localhost --> Data Source=MAY01\SQLEXPRESS and it work. Wink
 

Answer 36

I had an error  that is related to this thread.

Microsoft sql  Server 2005 -- Error 29515. SQL server  Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client]Shared Memory Provider: No process  is on the other end  of the pipe.

Here is what led to the error: I had installed SQL2005 and SharePoint on a box for testing purposes. Everything went in fine and configured correctly as well as setup initial site.  After this was done I installed visual studio 2008 and called it a day.

Came back on monday and attempted to connect to the Sharepoint central administration site and got a database not found error. No matter what I did I could not connect to it. So I uninstalled SQL and sharepoint, cleaned everything up and reinstalled.  That is when the Error 29515 first appeared.  I found this thread and tried everything listed here but nothing worked.

Fast forward ahead 3 days . . . I was to the point of reloading Server and starting from scratch but decided to try one more install.  This time I created a new user account on the server and installed using this account.

The SOB worked.  Not saying that this will solve all problems but it worked for me and is a quick fix to try.  I still have no idea why the error started but I suspect it had something to do with the initial install of visual studio and the sql express that comes with it.
 

Answer 37

Thank you very much.  Your advice worked well.
 

Answer 38

Yea I got this error...and in the event log it said that my server  was only configured for  Windows authentication.
So I logged in via Windows Auth and set the server properties to allow both sql  and Windows auth and also set the primary database for the sql user in the user properties..changed it from master. restarted sql services and things worked.
 

Answer 39

I have the similiar kinda of issue. but when i look into Log directory..this is what it says


Logon       Could not connect because the maximum number of '1' user connections has already been reached. The system administrator can use sp_configure to increase the maximum value. The connection  has been closed.



whats the procedure of using sp_configure.

thanks
Albin
 

Answer 40

My own issue is not similar to those mentioned in this forum.

I have got some SSIS packages stored in MSDB database. Exporting some of them gives this type of error  message.

Communication link failure Shared Memory Provider: No process  is on the other end  of the pipe. (Microsoft sql  Native Client)

Disabling Shared Memory Protocol and exporting the package again reports error on the other protocols (TCP and Named Pipe) depending on which of them at the top of priority list.

I have had a look at the server  and client protocols configurations. These settings seems to be working fine. I even had to disable and reorder them but the error still persists.
The irony of it is that the error is not coming up on all the packages.
I have restarted the engine and looked at the error log.

The log reports are as follows:

SQL Server is now ready for client connections. This is an informational message; no user action is required. Server is listening on [ 127.0.0.1 <ipv4> 1434]. Server named pipe provider  is ready to accept connection  on [ \\.\pipe\sql\query ]. Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ]. Server is listening on [ 'any' <ipv4> 1433].

I'm suspecting these packages but they are running  fine without any errors.
There is no certificate installed on the box.

Does anyone have a clue why this is happening?

One more thing the server configs are:
Win 2003 SP1, SQL 2005 RTM.

I'm not suspecting SQL service pack since the issues are not occurring on production with the same configurations. I'm planning to apply SP3 on the box though.

 

Answer 41

I had the same issue and none of the solutions here worked.

New install and created the first SQL Authentication user in a way that has always worked before.  Got the error  initially.

Restarted SQL Server service and tried the login on the host and still failed.

Clicked Add New Administrator as noted above in this thread.  I was already a sysadmin so I don't think this step made any difference.

I went to a remote computer to try the login and got a prompt that the login was expired.  No idea how it was considered expired.

I put in a new password at that prompt and then the login worked.
 

Answer 42

Login with default admin. Right click on server  name and select property, Select 'security' from left panel. Select option 'SQL Server and Windows Authentication mode' under Server Authentication. After this restart your server... hope this solves the problem
 

Answer 43

I had the same problem but on a remote server. In case anyone else might have the same issue, here’s what solved the issue for me.

 

1)       Go to Sql server  Surface Area Configuration Manager. Set remote connections to local only. Restart Sql Server (services manager)


2)       Go to Sql Server Studio Manager and login as “localhost” (make sure you don’t use a network instance but localhost). Then run this query (which someone on this forum so graciously posted)

 

EXEC sys.sp_configure N'show advanced options', N'1'RECONFIGUREWITHOVERRIDE

 

GO

 

EXEC sys.sp_configure N'user connections', N'0'

 

GO

 

RECONFIGUREWITHOVERRIDE

 

GO

 

EXEC sys.sp_configure N'show advanced options', N'0'RECONFIGUREWITHOVERRIDE

 

GO

 

3)       Go to Sql Server Surface Area Configuration Manager. Set remote connections to local and remote (i used tcp and named pipes). Restart Sql Server (services manager). The issue should now be resolved. Good luck!

 

Answer 44

Hi,

I am very new to sql  server.  I am facing a very strange problem with sql server.

We have installed sql server  2005 on windows server 2003 and authentication mode is mixed.  My problem is that sql server suddenly stop taking login authentication in sql mode however we are able to login from windows mode.

Restart the sql services does not make any difference but when we reboot our server,  problem gets solved but after sometimes we face the same problem again. 

following is error 

"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.) (.Net SqlClient Data Provider)"

There is no message in error log and even Named pipes enabled in my sql server. My all services are running  and there is no too many connections opened.

I don't understand where the problem lies.  any help would be greatly appreciated.

Thanks In Advance.






 

Answer 45

Land thank you this work  for as well.
 

Answer 46

thank for the advise, works like a charm for me...
 

Answer 47

Hi,

I had the same problem but when I tried to check the ERRORLOG, I got the below error

 

 "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL is not accessible."

Access is denied.

Can you please help me out now. Thanks.

 

Answer 48

have restarted the SQL engine service and which worked for me and able to connect to database. Thanks, Toufiq.
 

Answer 49

You are a life saver!!!!
 

Answer 50

This is a very great way. I use it solving my problem very fast!

 

thanks

 

Answer 51

Thanks a lot.. !!
 

Answer 52

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:

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


Hi !   Actually the problem is that urs MS SQL didn't configure correctly .  Use the Surface Area and make sure  remote connection to SQL  is avalable.

 

Answer 53

I faced below mentioned issue today and here's the solution .  This is because sql  server's "user connections' row in sp_configure was set to 2.

1)Open the database in single login mode..

2)  If you dont know how to open in single login mode then

         i)stop sql server  agent service .This will deduct one connection  to the database.

         ii)Now, use your management studio to login . You should be able to login becuase stopping the sql server agent service removes one connection to the database.

3) type sp_configure and see for 'user connections' row..You should see 2 over there .

4) run .... EXECsp_configure'user connections', 10 .

That fixes your problem.....

------------------------------
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)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476

------------------------------
BUTTONS:

OK
------------------------------

 
 
 

<< Previous      Next >>


Microsoft   |   Windows   |   Visual Studio   |   Follow us on Twitter