Can't connect to SQL Server 2005 with Pet Shop 4.0 : No process at other end of pipe?!

Last post 06-07-2006 4:02 AM by Iori_Jay. 2 replies.

Sort Posts:

  • Can't connect to SQL Server 2005 with Pet Shop 4.0 : No process at other end of pipe?!

    06-06-2006, 11:54 PM
    • Member
      202 point Member
    • LaTtEX
    • Member since 09-09-2005, 7:39 AM
    • Philippines
    • Posts 47
    I downloaded MS Pet Shop 4.0 recently for best-practice training purposes. The installation went smoothly with a SQL Server 2005 backend. At first I had a problem authenticating the mspetshop4 user in the database, but that was solved by fixing some settings with the password policy. Now the mspetshop4 user is authenticated properly, but I came across this error instead:
    Server Error in '/Web' Application.
    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.)
    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
    
    Exception Details: System.Data.SqlClient.SqlException: 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.)
    
    Source Error:
    
    Line 216:
    Line 217:            if (conn.State != ConnectionState.Open)
    Line 218:                conn.Open();
    Line 219:
    Line 220:            cmd.Connection = conn;
    
    
    Source File: C:\Program Files\Microsoft\.NET Pet Shop 4.0\DBUtility\SQLHelper.cs    Line: 218
    
    Stack Trace:
    
    [SqlException (0x80131904): 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.)]
       System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +117
       System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +346
       System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error) +619
       System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj) +224
       System.Data.SqlClient.TdsParserStateObject.ReadPacket(Int32 bytesExpected) +113
       System.Data.SqlClient.TdsParserStateObject.ReadBuffer() +59
       System.Data.SqlClient.TdsParserStateObject.ReadByte() +36
       System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) +181
       System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK) +56
       System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +1083
       System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +272
       System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +688
       System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) +82
       System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject) +558
       System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject) +126
       System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +651
       System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +160
       System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +122
       System.Data.SqlClient.SqlConnection.Open() +229
       PetShop.DBUtility.SqlHelper.PrepareCommand(SqlCommand cmd, SqlConnection conn, SqlTransaction trans, CommandType cmdType, String cmdText, SqlParameter[] cmdParms) in C:\Program Files\Microsoft\.NET Pet Shop 4.0\DBUtility\SQLHelper.cs:218
       PetShop.DBUtility.SqlHelper.ExecuteReader(String connectionString, CommandType cmdType, String cmdText, SqlParameter[] commandParameters) in C:\Program Files\Microsoft\.NET Pet Shop 4.0\DBUtility\SQLHelper.cs:127
       PetShop.SQLServerDAL.Category.GetCategories() in C:\Program Files\Microsoft\.NET Pet Shop 4.0\SQLServer\Category.cs:27
       PetShop.BLL.Category.GetCategories() in C:\Program Files\Microsoft\.NET Pet Shop 4.0\BLL\Category.cs:20
       PetShop.Web.NavigationControl.BindCategories() in c:\Program Files\Microsoft\.NET Pet Shop 4.0\Web\Controls\NavigationControl.ascx.cs:53
       PetShop.Web.NavigationControl.Page_Load(Object sender, EventArgs e) in c:\Program Files\Microsoft\.NET Pet Shop 4.0\Web\Controls\NavigationControl.ascx.cs:27
       System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) +31
       System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +68
       System.Web.UI.Control.OnLoad(EventArgs e) +88
       System.Web.UI.Control.LoadRecursive() +74
       System.Web.UI.Control.LoadRecursive() +158
       System.Web.UI.BasePartialCachingControl.LoadRecursive() +61
       System.Web.UI.Control.LoadRecursive() +158
       System.Web.UI.Control.LoadRecursive() +158
       System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +3035
    
    
    Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.42
    Now I'm clueless. What does No process at the other end of the pipe mean? 
    http://dotnet.kapenilattex.com
  • Re: Can't connect to SQL Server 2005 with Pet Shop 4.0 : No process at other end of pipe?!

    06-07-2006, 3:54 AM
    • All-Star
      33,913 point All-Star
    • vcsjones
    • Member since 04-18-2006, 8:53 PM
    • Falls Church, VA
    • Posts 4,331
    • Moderator
      TrustedFriends-MVPs
    Check if  SQL Server is configured to accept Local and Remote Connections (using tcp) in Surface Area Configuration Manager. Also, check to see if your SQL Server is configured to accept connections over both TCP/IP and named pipes.
    Cheers,
           Kevin Jones


  • Re: Can't connect to SQL Server 2005 with Pet Shop 4.0 : No process at other end of pipe?!

    06-07-2006, 4:02 AM
    • Star
      12,930 point Star
    • Iori_Jay
    • Member since 04-04-2006, 6:21 AM
    • Posts 2,450

    Hi, quick searched on these forums and I found a post with excatly similar issue as yours, hope this helpsSmile:

    http://forums.asp.net/thread/1072499.aspx

     

    Welcome to my SQL/ASPNET forum for Chinese
    http://51up.org/bbs/forumdisplay.php?fid=38
Page 1 of 1 (3 items)