Please note: If you find any post DOES NOT contain required amount of explanation, please do comment them with a request for more information. I will update as soon as I can attend to it. Also you can contact me with a link to the post.


Wednesday, April 22, 2009

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


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

Resolution:

  1. SqlConnection: If this happen when tries to connecting to SQL Server, then try increasing the timeout of the connection
    Connection String: server=Server;database=Database;uid=Uid;pwd=Pwd;timeout=600 (ConnectionTimeout is read-only)
  2. SqlCommand: More interestingly if you manage to connect successfully and although you set a fat timeout value to your connection command object does not inherit the timeout from its connection. It uses its own timeout value. More logically ConnectionTimeout and CommandTimeout.   
    So increase the timeout of the command, which is not read-only like SQLConnection

    command.CommandTimeot = 600 (set to 10 minutes)  

Reference: ASP.NET Forums

0 comments:

 

Copyrights(C) - Charith Gunasekara 2005-2010