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

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: error: The operation has timed-out (executionTimeout?)
    ... I have tried modifying several settings ... calls an asp.Net web service to retrieve the report. ... I also tried modifying my web site to timeout in 300 seconds using ... System.web settings for My web site web.config ...
    (microsoft.public.dotnet.framework.aspnet)
  • error: The operation has timed-out (executionTimeout?)
    ... calls an asp.Net web service to retrieve the report. ... I have tried modifying the executionTimeout setting in Web.Config for both ... I also tried modifying my web site to timeout in 300 seconds using ... System.web settings for My web site web.config ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: error: The operation has timed-out (executionTimeout?)
    ... undesirable since it would affect every web app on the box. ... I also had to add a line to my code where I call the web service, ... I have tried modifying several settings ... I also tried modifying my web site to timeout in 300 seconds using ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: error: The operation has timed-out (executionTimeout?)
    ... timed out instantly) in the code that calls the web service, ... runnign report (90-120 seconds. ... I also tried modifying my web site to timeout in 300 seconds using ... System.web settings for My web service web.config ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: error: The operation has timed-out (executionTimeout?)
    ... I set the timeout on the machine.config, and the web.config for both the web ... I have tried modifying several settings ... the web service are running locally on my PC. ... System.web settings for My web site web.config ...
    (microsoft.public.dotnet.framework.aspnet)
Loading