Connection timeout
-
my connection is:
<add name="AdNetConnectionString" connectionString="Data Source=.\SQLEXPRESS;Initial Catalog=AdNet;Integrated Security=True" providerName="System.Data.SqlClient" />
the error is Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding and I try to add the proberty
ConnectionTimeout=200
to my connection but this error occurred The Connection Timeout attribute is not declared. so please guide me to solve this problem.
-
my connection is:
<add name="AdNetConnectionString" connectionString="Data Source=.\SQLEXPRESS;Initial Catalog=AdNet;Integrated Security=True" providerName="System.Data.SqlClient" />
the error is Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding and I try to add the proberty
ConnectionTimeout=200
to my connection but this error occurred The Connection Timeout attribute is not declared. so please guide me to solve this problem.
msomar wrote:
Timeout expired.
Your query is to slow to complete only for 200 seconds.You would better try to optimize it. If your query execution time can't be reduced set
ConnectionTimeoutproperty to 0, which means no limit.It's preferred to be avoided but sometimes it's not possible.Life is a stage and we are all actors!
-
my connection is:
<add name="AdNetConnectionString" connectionString="Data Source=.\SQLEXPRESS;Initial Catalog=AdNet;Integrated Security=True" providerName="System.Data.SqlClient" />
the error is Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding and I try to add the proberty
ConnectionTimeout=200
to my connection but this error occurred The Connection Timeout attribute is not declared. so please guide me to solve this problem.
Can you post a bit more of your code? I suspect that your connection string isn't right, as the server should respond in 200 mS easily. Are you using a local installation of SQL Server Express? If so, it should have a name for the instance, not ".\SQLEXPRESS." It may be that it isn't responding because it's never notified on the request. For instance, on my setup, the SQL Server installation is named "BAAL\SQLEXPRESS" and shortening the name in the connection string never works. The shortcut ".\" may not be valid for this application, so try adding the full name of the computer that hosts the server and see if that helps.
"A Journey of a Thousand Rest Stops Begins with a Single Movement"