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

    Question

  • 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

    Wednesday, December 14, 2005 6:06 PM

All replies

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

     

     

    Saturday, December 17, 2005 1:02 AM
  • Did not see any weird error message may cause this problem.
    Sunday, December 25, 2005 4:41 PM
  • 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.
    Wednesday, December 28, 2005 3:54 AM
  • 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

    • Proposed as answer by R_2 Monday, March 16, 2009 12:53 PM
    Thursday, January 05, 2006 4:08 AM
  •  

    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

     

    • Proposed as answer by Ross Warden Tuesday, November 16, 2010 2:02 PM
    Wednesday, March 01, 2006 11:02 AM
  • yaah!!!! i have done same and it worked.. but after opening 5 or 6 connection, m getting the same error message again.....

     

     

    Cheers!!

    Wednesday, May 10, 2006 5:51 AM
  • Another mistake that can cause this error is incorrect credentials in a connection string.
    Tuesday, August 01, 2006 5:45 PM
  • execute sp_configure and increment the conexion

    Monday, August 07, 2006 1:20 PM
  • reboot your db server...
    Friday, August 25, 2006 11:37 PM
  • 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

     

     

    Tuesday, September 12, 2006 4:13 PM
  • 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

    Friday, October 13, 2006 2:33 PM
  • I enable the Protocols "Named Pipes" and it works.

    Thanks Lane.

     

    Thursday, November 09, 2006 8:41 AM
  • After a while like 5 hours that I tried to solve this problem Thanks Lane I found your post... & Now it works
    Sunday, December 31, 2006 1:07 AM
  • 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.
    Monday, February 05, 2007 2:30 PM
  • 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?
    Thursday, February 15, 2007 11:15 AM
  •  

    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

    Thursday, February 22, 2007 10:54 PM
  • thanks it works when enable "namedPipes" protocols

     

    Monday, May 21, 2007 12:02 PM
  • 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

    • Proposed as answer by zingab Monday, May 23, 2011 5:33 PM
    • Unproposed as answer by zingab Monday, May 23, 2011 5:33 PM
    Tuesday, May 29, 2007 8:23 PM
  •  

    i have this same problem

    when the name pipes was enable thwe connection is timeout

     

     

    any one could help???

     

     

    Thursday, August 09, 2007 7:55 AM
  • Disable Shared memory protocol and try !....

     

    Thursday, August 23, 2007 10:24 PM
  • 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!

     

    Wednesday, September 12, 2007 5:03 PM
  •  

    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.
    Thursday, October 11, 2007 6:18 PM
  •  

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

    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

     

    Thursday, November 15, 2007 8:27 PM
  • 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' RECONFIGURE WITH OVERRIDE

    GO

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

    GO

    RECONFIGURE WITH OVERRIDE

    GO

    EXEC sys.sp_configure N'show advanced options', N'0' RECONFIGURE WITH OVERRIDE

    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.

    Tuesday, January 08, 2008 4:03 PM
  • Could you please share the steps you did to enable "named pipes protocol in SQL Server network configuration protocols?"

    Thanks!

    Friday, January 11, 2008 3:19 PM
  • 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)

    Friday, January 11, 2008 3:34 PM
  •  

    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!

     

    Friday, February 22, 2008 7:07 PM
  • 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.

    Wednesday, March 05, 2008 7:33 PM
  • How was the named pipes enabled. Was this through the connect string code or is this a setting in SQLExpress

    Friday, March 21, 2008 4:45 PM
  • goto sql server configuration manager.  it's under SQL server2005 Network configuration- protocols for (your sqlengine)

    Saturday, July 19, 2008 7:54 PM

  • 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.
    Thursday, July 24, 2008 10:44 AM
  • 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.

     

    Thursday, July 31, 2008 1:29 AM
  • After restarting the services, able to connect the SQL server from Client machines. thanks

    Tuesday, October 07, 2008 11:45 AM
  • 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

     

    Friday, November 21, 2008 5:01 PM
  • I have the same errror. I try to change the connectionString: ...Data Source=localhost --> Data Source=MAY01\SQLEXPRESS and it work. Wink
    Tuesday, November 25, 2008 4:46 AM
  • 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.
    Thursday, March 12, 2009 4:22 PM
  • Thank you very much.  Your advice worked well.
    Thursday, April 16, 2009 9:18 AM
  • 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.
    Wednesday, July 22, 2009 5:05 PM
  • 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

    albingorkhali
    Thursday, August 13, 2009 5:14 PM
  • 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.

    Friday, November 06, 2009 9:35 AM
  • 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.
    • Proposed as answer by srikanthmn Sunday, January 17, 2010 3:23 PM
    Friday, January 08, 2010 10:18 PM
  • 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
    • Proposed as answer by SenaM Wednesday, April 04, 2012 3:38 AM
    Sunday, January 17, 2010 3:28 PM
  • 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' RECONFIGURE WITH OVERRIDE

     

    GO

     

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

     

    GO

     

    RECONFIGURE WITH OVERRIDE

     

    GO

     

    EXEC sys.sp_configure N'show advanced options', N'0' RECONFIGURE WITH OVERRIDE

     

    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!


    lp
    Monday, January 18, 2010 4:47 PM
  • 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.






    Monday, January 25, 2010 12:13 PM
  • Land thank you this work for as well.
    Wednesday, January 27, 2010 5:11 PM
  • thank for the advise, works like a charm for me...
    Sunday, February 07, 2010 5:59 AM
  • 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.

    • Proposed as answer by Sayed Toufiq Saturday, May 01, 2010 4:16 AM
    Tuesday, April 06, 2010 10:09 AM
  • have restarted the SQL engine service and which worked for me and able to connect to database. Thanks, Toufiq.
    Saturday, May 01, 2010 4:19 AM
  • You are a life saver!!!!
    Thursday, July 22, 2010 3:41 PM
  • This is a very great way. I use it solving my problem very fast!

     

    thanks

    Sunday, July 25, 2010 12:56 PM
  • Thanks a lot.. !!
    Monday, August 16, 2010 8:03 AM
  • 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


    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.

    Thursday, September 09, 2010 11:02 AM
  • 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 .... EXEC sp_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
    ------------------------------

    Tuesday, September 21, 2010 11:15 PM
  • Thanks Lane! It works!
    Thursday, December 02, 2010 12:33 AM
  • So you changed it from mater... to what???
    Samuel Miller
    Tuesday, February 15, 2011 7:46 PM
  • I had this problem but in my case i was not passing the db pwd .... Eu tive esse mesmo problema mas em meu caso eu não estava passando a senha....
    Marcelo Gomes
    Friday, April 15, 2011 4:29 PM
  • I am getting this error, some of the replies i tried and didnt get the solution, some are i dont know how to do it, but still i am getting the error. When i open the SQL Server Configuration Manager, SQLEXPRESS State is stopped, when i try to start the service, it showing the following error:

    The request failed or the service did not respond in a timely fashion.

    Plz anyone help me to find out the solution.

    Friday, November 11, 2011 9:29 AM
  • 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.

    It worked after both SQL and windows auth were set. Thanks RG-labcorp
    Thursday, March 22, 2012 5:34 PM
  • Setting proposed by Lane did it... 

    LOTS of problems connecting SQL DB to SharePoint. Error 233, No Process on end of Pipe, account login failure.... and on and on.... really..! 

    Created SQL account (not AD/NT Domain account); logged in to reset password (on first use)

    Added setting to web.config file (actually in /14 NOT /60) per this post http://support.microsoft.com/kb/831092

    <system.net> <defaultProxy> <proxy proxyaddress="http://ProxyServer:port" bypassonlocal = "true"/> </defaultProxy> </system.net>

    In SQL Config manager, enabled both TCP and Named Pipes, stopped and re-started the server

    (Lane's suggestion Named Pipes - then it worked)

    Not sure if everything else was overkill or not. But whatever the case, I now have a SPD connection to the DB. 


    Terri Morgan


    • Edited by TerriMorgan Saturday, March 31, 2012 7:13 PM
    Saturday, March 31, 2012 7:13 PM
  • Hi,

    I too had the same issue. Below is the solution. If you are using PowerShell to execute sql scripts then put following code after query.

    [System.Data.SqlClient.SqlConnection]::ClearAllPools()

    or if you sing C# then.

    System.Data.SqlClient.SqlConnection.ClearAllPools();

    Thanks,

    Prakash

    Friday, August 24, 2012 6:05 AM
  • i had the same issue but i ran the following script and then restarted the service

    declare
    @oldvalue int;
    set @oldvalue =  CONVERT(int, (select value from   sys.configurations
    where name = 'show advanced options'));
    EXEC sp_configure 'show advanced options', 1
    RECONFIGURE
    EXEC sp_configure 'user connections',0 ;
    RECONFIGURE;
    EXEC sp_configure 'show advanced options', @oldvalue
    RECONFIGURE
    GO

    • Proposed as answer by perezco Friday, October 12, 2012 9:07 PM
    • Unproposed as answer by perezco Friday, October 12, 2012 9:07 PM
    Thursday, October 04, 2012 8:52 AM
  • I ran into this error today. I was able to resolve it by making sure the database is set to Mixed authentication. 
    Tuesday, October 30, 2012 7:35 PM