Re: error: The operation has timed-out (executionTimeout?)

Um, no connection timeout is for database connections timeout. Command
timeout is for sql command timouts, which is what you are experiencing.

When you run the query in SQL Analyzer, how long does it take? Of course the
the shortest timeout, the Webservice timeout or command timeout, will happen
first. If your command takes longer than the webservice timeout, you'll get
that error. Database connections always happen very fast, it's the queries
(commands) that can take awhile.

First, you need to fix your SQL!

Jeff

"Jim Underwood" <james.underwoodATfallonclinic.com> wrote in message
news:e9gvrnyXGHA.4248@xxxxxxxxxxxxxxxxxxxxxxx
Isn't Command.Timeout for database connections? I am dealing with Crystal
reports DLLs that run reports and return a file to the web service, which
returns them to my web app. The database connections do not appear to be
a
problem, although I am nto ruling anythign at just yet.

I have set my Webservice.Timeout=300000 (milliseconds I think, since 300
timed out instantly) in the code that calls the web service, and now I am
getting an error at 5 minutes instead of 90 seconds. From what can see
it
seems to be working as I want it, but more testing is needed. I am
purposely sending bad criteria to make the report run for a longer period,
so I can see what effect the parameters have.

Once I figure out just what makes the difference I'll post the solution
here. In the mean time, any additional advice is apreciated.


"Jeff Dillon" <jeffdillon@xxxxxxxxxxx> wrote in message
news:OimI40xXGHA.3444@xxxxxxxxxxxxxxxxxxxxxxx
You need Command.TimeOut, not connection or Server.Timeout

Jeff
"bruce barker (sqlwork.com)" <b_r_u_c_e_removeunderscores@xxxxxxxxxxx>
wrote
in message news:%23CTUOixXGHA.3656@xxxxxxxxxxxxxxxxxxxxxxx
the webservice call can also timeout. you need to set its timeout also.

-- bruce (sqlwork.com)



"Jim Underwood" <james.underwoodATfallonclinic.com> wrote in message
news:OtRBdAxXGHA.3496@xxxxxxxxxxxxxxxxxxxxxxx
I am having a problem with my web page timng out while retrieving a
long
runnign report (90-120 seconds. I have tried modifying several
settings
in
various places and cannot get it to run for more than 90 seconds.

I am running VS.Net and the app is ASP.Net, written using VB.Net. The
app
calls an asp.Net web service to retrieve the report. Both the web
site
and
the web service are running locally on my PC.

I have tried modifying the executionTimeout setting in Web.Config for
both
the site and the web service, and I have also modified the
executionTimeout
setting in machine.config. In all cases the value is set to 300
(seconds).

.Net Version is 1.1.4322.2032.

I also tried modifying my web site to timeout in 300 seconds using
Server.ScriptTimeout = 300
with no effect.

Both the web site and the web service have been compiled as "release",
and
not as "debug".

If anyone can provide any suggestions, I would very much apreciate it.

Below are sections of each of my config files.

System.web settings for My web site web.config
<system.web>
<compilation defaultLanguage="vb" debug="false" />
<httpRuntime executionTimeout="300" maxRequestLength="4096"
useFullyQualifiedRedirectUrl="false" minFreeThreads="8"
minLocalRequestFreeThreads="4" appRequestQueueLimit="100"
enableVersionHeader="true"/>
....
</system.web>

System.web settings for My web service web.config
<system.web>
<compilation defaultLanguage="vb" debug="false" />
<httpRuntime executionTimeout="300" maxRequestLength="4096"
useFullyQualifiedRedirectUrl="false" minFreeThreads="8"
minLocalRequestFreeThreads="4" appRequestQueueLimit="100"
enableVersionHeader="true"/>
....
</system.web>

System.web settings from machine.config
<system.web>
<httpRuntime executionTimeout="300" maxRequestLength="4096"
useFullyQualifiedRedirectUrl="false" minFreeThreads="8"
minLocalRequestFreeThreads="4" appRequestQueueLimit="100"
enableVersionHeader="true"/>
<compilation debug="false" explicit="true" defaultLanguage="vb">
...
</system.web>










.

Relevant Pages

  • Re: Really need help on this one
    ... Is there a way to read the output of a particular command into ... Heres a better example using ssh. ... set timeout $timeout ... exec kill -9 $pid ...
    (comp.lang.tcl)
  • Re: writing/publishing/consuming
    ... \par "Whether it will generated cs file or dll" is not important for the two approaches as both of them can generate dll and cs file. ... Is there an advantage to using the command line? ... \par> and after writing a web service to convert temperatures between ... \par> Generating a proxy class of the service. ...
    (microsoft.public.dotnet.framework.webservices)
  • Re: writing/publishing/consuming
    ... "Whether it will generated cs file or dll" is not important for the two approaches as both of them can generate dll and cs file. ... ** In Visual Studio, the visual approach is integrated with IDE and as long as you use VS to generate the webservice proxy, IDE will help you do a lot of things(such as call the command with parameters get from your GUI input). ... Also, when you want to update a proxy, you can simply right click it to update. ... and after writing a web service to convert temperatures between ...
    (microsoft.public.dotnet.framework.webservices)
  • Re: What if Expect buffer overflows
    ... expect_outwhen eof and timeout events happen. ... with your command and see what happens. ... Can anybody please guide what should I do to display the whole info? ...
    (comp.lang.tcl)
  • IIS5.0 Timeout problem
    ... The "sessionState" timeout is set to 60 mins. ... I have the default web site "Connection Timeout" set to 60 ... Under the virtual directory for the web service app, ...
    (microsoft.public.inetserver.iis)