Post reply

System.Data.SqlClient.SqlException: The client was unable to establish a connection because of an error during connection initialization process before login

  • May 10, 2011 at 11:03 am

    #235997

    Is there a way to see the memory usage levels at a certain time on a machine? I have a developer with an app that runs every 15 minutes and for the last 2 weeks we've been getting the same error in the same morning 2 hour window. The error states:

    Machine Name = MEDSVC - - - Domain = MED-EDGE.COM - - - User Name = _SVC_PSV - - - - - - MedicalEdge.DAL.Exceptions.DALExceptions: ReturnValue: <br/><br/> The client was unable to establish a connection because of an error during connection initialization process before login. Possible causes include the following: the client tried to connect to an unsupported version of SQL Server; the server was too busy to accept new connections; or there was a resource limitation (insufficient memory or maximum allowed connections) on the server. (provider: Named Pipes Provider, error: 0 - No process is on the other end of the pipe.) ---> System.Data.SqlClient.SqlException: The client was unable to establish a connection because of an error during connection initialization process before login. Possible causes include the following: the client tried to connect to an unsupported version of SQL Server; the server was too busy to accept new connections; or there was a resource limitation (insufficient memory or maximum allowed connections) on the server. (provider: Named Pipes Provider, error: 0 - No process is on the other end of the pipe.) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParserStateObject.WriteSni() at System.Data.SqlClient.TdsParserStateObject.WritePacket(Byte flushMode) at System.Data.SqlClient.TdsParser.SendPreLoginHandshake(Byte[] instanceName, Boolean encrypt) at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject) at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject) at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart) at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup) at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) at System.Data.SqlClient.SqlConnection.Open() at MedicalEdge.DAL.SQL.StoredProcConfig.OpenConnection() at MedicalEdge.DAL.SQL.StoredProcConfig.ExecuteDataSet(DataSet dataset) --- End of inner exception stack trace --- at MedicalEdge.DAL.SQL.StoredProcConfig.ExecuteDataSet(DataSet dataset) at PSV_Global_PrintService.DataAccess.SQLStoredProcedure.GetConfigSettings(String constr, String index) in E:\AppDev\Windows Services\PSV_Global_PrintService\PSV_Global_PrintService\PSV_Global_PrintService\DataAccess\SQLStoredProcedure.cs:line 72 at PSV_Global_PrintService.PSV_Global_PrintService.PopulateSettings() in E:\AppDev\Windows Services\PSV_Global_PrintService\PSV_Global_PrintService\PSV_Global_PrintService\PSV_Global_PrintService.cs:line 291

  • May 10, 2011 at 11:49 am

    #1322566

    A little more info to add. I'm not seeing any errors in the SQL Server Logs nor the event logs. Could this be a network issue?

  • August 5, 2011 at 1:04 am

    #1364109

    I am facing the same issue. Any help is highly appriciable

  • August 21, 2011 at 4:56 pm

    #1371225

    Hi, did anyone ever resolve this problem? I am having the exact same issue but only occasionally not all the time.

    I have connection pooling on, there are no errors in any error logs that I can see.

    The exact same code works fine on a the UAT box below

    MYSERVER\UAT

    Microsoft SQL Server 2005 - 9.00.3050.00 (Intel X86)

    Mar 2 2007 20:01:28

    Copyright (c) 1988-2005 Microsoft Corporation

    Standard Edition on Windows NT 6.0 (Build 6001: Service Pack 1)

    MYSERVER\LIVE

    Microsoft SQL Server 2005 - 9.00.3050.00 (X64)

    Mar 2 2007 22:06:10

    Copyright (c) 1988-2005 Microsoft Corporation

    Standard Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)

    Any ideas appreciated

    Thanks

    Mark

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply