Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 

SQL Server Blog Forum

My name is Muthukkumaran Kaliyamoorthy and I am living in India (Chennai). I’m currently working as a SQL server DBA in one of the top MNC. I’m passionate about SQL Server, and I’m specialized in Administration and Performance tuning.

SQL server the timeout period elapsed prior to completion of the operation

SQL server clustering the timeout period elapsed prior to completion of the operation

Recently I faced one of our application could not connect. It throws an error ” Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding. (Microsoft SQL Server, Error: -2) ” I found the problem. It’s because of firewall.

SQL Cluster error:

Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. (Microsoft SQL Server, Error: -2)

 

We are using SQL server failover clustering on our application, after a failover occurred the application could not connect it. It’s used a default instance, default port and the connection string are correct (FQDN) even though it’s not connected because the firewall prevents the SQL server (port). Again I failed over the server it works fine. It’s a simple problem. Therefore the problem is the Installation team created inbound rule on one server not the other passive server.

 

Run –> Administrative tools –> Firewall –> Inbound rule–> Right click –> New rule –> Select port –> Click next –> Enter the SQL server port number –> Select the default –> Next –> Select the profile whatever you want –> Enter the name

 

 

The conclusion is always creating a firewall rule to all the nodes after finish a SQL clustering installation.

Comments

Leave a comment on the original post [www.sqlserverblogforum.com, opens in a new window]

Loading comments...