Connection issue after update SQL 2008 R2 to SP2

• dkondrashov

  Newbie

  Points: 5

  More actions

  November 14, 2012 at 2:09 am

  #284938

  Hallo,

  Some days ago we succesfully update Our SQL 2008 R2 failover cluster(2 nodes) to SQL 2008 R2 SP2.

  Now for 70% users we have connection issues.

  First Scenario

  For example we use software that connects from user computer to SQL with standart connection string like this:

  SqlConnection conn = new SqlConnection(Properties.Settings.Default.ConnectionString);

  On users computers where we see connection issue we got message:

  Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

  after I run command:

  ipconfig /flushdns

  , the problem disappears and connection is established, but after some period of time problem resumes. Firewalls disabled for user and failover cluster.

  Second scenario

  I install on one user computer SQL server management studio, then I try to connect with this user credentials to database I got:

  ===================================

  Cannot connect to MSCLUSTER-SQL.

  ===================================

  Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. (.Net SqlClient Data Provider)

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

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

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

  Server Name: MSCLUSTER-SQL

  Error Number: -2

  Severity: 11

  State: 0

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

  Program Location:

  at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)

  at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)

  at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error)

  at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj)

  at System.Data.SqlClient.TdsParserStateObject.ReadNetworkPacket()

  at System.Data.SqlClient.TdsParser.ConsumePreLoginHandshake(Boolean encrypt, Boolean trustServerCert, Boolean& marsCapable)

  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 Microsoft.SqlServer.Management.SqlStudio.Explorer.ObjectExplorerService.ValidateConnection(UIConnectionInfo ci, IServerType server)

  at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()

  after I run command:

  ipconfig /flushdns

  , the problem disappears and connection is established, but after some period of time problem resumes.

  Then I use first node IP to connect with SQL studio management it is connecting without issues.

  I have all request DNS entries for SQL failover cluster. I don't know maybe it is not SQL problem.

  In SQL log I can't find any bad connections. Any suggestions for this? How can I resolve this problem?

  thank you all for your help in advance