Re: "Timeout expired" in ADO.NET

Tech-Archive recommends: Fix windows errors by optimizing your registry

Hi Gregory,

Thank you for your reply, but perhaps you didn't read the whole post? As I
mentioned, I get the exception instantly, no matter what the timeout values
are. Also, I get the exception before I would otherwise get the "Login
failed" exception.


Regards,
Nils Magnus Englund

"Cowboy (Gregory A. Beamer) - MVP" <NoSpamMgbworld@xxxxxxxxxxxxxxxxxx> wrote
in message news:E135E651-DA94-4EB0-961E-712A69B47E4A@xxxxxxxxxxxxxxxx
> 1. Make sure the connection timeout is large enough - this is not normally
> the problem,however.
>
> 2. Make sure the command timeout is large enough for the work you are
> doing
> - this is a common problem.
>
> NOTE: I find it best to always explicitly set timeout values.
>
> --
> Gregory A. Beamer
> MVP; MCP: +I, SE, SD, DBA
>
> ***************************
> Think Outside the Box!
> ***************************
>
>
> "Nils Magnus Englund" wrote:
>
>> Hi,
>>
>> I've sent a similar post earlier - but after no more luck and a lot more
>> frustration, I am reposting the issue with some additional information.
>>
>> It's regarding several web applications on the same server, connecting to
>> a
>> SQL Server on another server.
>>
>> I keep getting the following exception when accessing the database:
>>
>> -----
>> System.Data.SqlClient.SqlException: Timeout expired. The timeout period
>> elapsed prior to completion of the operation or the server is not
>> responding.
>> ----
>>
>> I am currently using the following code to connect, but I've had the same
>> problem with all the different code snippets I've tried, so I doubt the
>> problem lies herein:
>>
>> -----
>> using (SqlConnection connection = new SqlConnection(connectionString))
>> {
>> connection.Open();
>> .... data code ....
>> connection.Close();
>> }
>> -----
>>
>> The problem happens 1-5 times, after I refresh the page enough times, it
>> usually goes through. I've seen a number of potential solutions to the
>> problem - but none of them fits the problem.
>>
>> I usually get the exception after not using the system for a while, but I
>> haven't experienced when the system is "in use", i.e. when the previous
>> request was no more than a couple of minutes ago, and no recompile of the
>> application has been done.
>>
>> I _don't_ get enough connections to exceed the maximum - far from it
>> (when I
>> don't get the exception, the connection pooling seems to work fine).
>>
>> The exception is thrown instantly, not after the default 30 second
>> timeout.
>>
>> And after I had accidentally misconfigured the authentication in the web
>> application, the user didn't have access - I got "Login failed for user
>> (null)" - what's odd was that I _still_ got the "Timeout expired"
>> exception
>> 4-5 times before I finally got the expected "Login failed" exception. The
>> "Timeout expired" exception gets thrown even before I successfully
>> connect
>> to the database!
>>
>> Suggestions are very welcome, I've been struggling with this problem off
>> and
>> on for several weeks now. It's only a big nuisance during development,
>> but
>> naturally, it's a real showstopper for going into production with the
>> application(s).
>>
>>
>> Regards,
>> Nils Magnus Englund
>>
>>
>>
>>
>>
>>


.

Relevant Pages

  • Re: Query runs slow from web app, but not from management studio
    ... sent to the server, particularly w/ respect to the parameters. ... I've Included the timeout information below. ... exception gets thrown on the ExecuteReader call. ... connection, SqlTransaction transaction, CommandType commandType, String ...
    (microsoft.public.dotnet.framework.adonet)
  • Attempt on SqlConnection.BeginOpen
    ... The "Connection Timeout" ... connection to the SQL Server, not to the actual TCP port. ... will throw a custom Exception. ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Query runs slow from web app, but not from management studio
    ... because of performance hits on the server. ... I've Included the timeout information below. ... the exception gets thrown on the ExecuteReader call. ... connection, SqlTransaction transaction, CommandType commandType, String ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: IIS ASP.net Web Services Disconnected
    ... does show no exception, and it is a perfect run on the server-side. ... the connection idle for more than 1/2 hours, ... the server thinks the file is send without problem. ... At the client-side, it times out after 1.5 hours if nothing happen. ...
    (microsoft.public.dotnet.framework.aspnet.webservices)
  • Re: System.Security.SecurityException {Beginner working with ASP.NET}
    ... seems like the server is runnning with partial trust. ... In the page_load I fill the data adapter, ... grid and close the connection. ... I get this exception when attempting to view my webform in IE6. ...
    (microsoft.public.dotnet.framework.aspnet.security)