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

Actually, there was no SQL timeout issue in this case, and when I said
connection, I meant the SQL command whcih runs over the connection. The web
service was calling Crystal Reports behind the scenes, and it is Crystal
that is taking so long. The actual SQL executes in seconds, but it takes
over a minute to send all of the data (400,000 plus rows) across the
network, then crystal has apply formulas and summarize the results. I am
pretty sure I can rewrite this report to return results much faster (under
30 seconds anyway) by doing some of the summarization on the database.
However, since I know we will end up with reports that take over 90 seconds
to run, I needed to insure that we can accomodate them, in addition to
fixing the performance of this particular report. By the way, it is a
report written by a business user, not by me, but it will be made more
efficient before it hits production. After it is rewritten those 400,000
rows should be summarized into 2,000 rows with about the same execution
time. but saving netowrk traffic, memory, and CPU cycles on the crystal end.

Since Crystal manages the SQL connections on its own, I didn't have to worry
abotu that at all, but I did have to worry about the web service which was
quiting the request before crystal completed the report. I could actually
watch the report files get saved to disk seconds after the page timed out.

In the end, I had to set executionTimeout in both my web site and the web
service which it was calling, as well as set the webservice.timeout in my
code before I called it. I had problems with my web site timing out, the
web service timing out, then my web site timing out it's own request to the
web service. Now I am able to run a report that completes in under 5
minutes (yes, still a long time, I know), and I know what I can do in the
future if I run into this problem again.

Anyway, thanks for the suggestions. Although the solution was (in part)
different then you suggested, your advice was right on the money.

"Jeff Dillon" <jeffdillon@xxxxxxxxxxx> wrote in message
news:%230ps76yXGHA.4620@xxxxxxxxxxxxxxxxxxxxxxx
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: How complex is this, really?
    ... I'd just create an asp.net web app with a SQL backend. ... Users can enter orders on a "public" web site up until the event. ... I'd back up the SQL database and restore it to the notebook. ... All the web service would be doing is keeping four ...
    (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: Populating a list -- table structure?
    ... I had made a report already and figured out about adding the ... your responce below, but thanks to your help with SQL, I was able to get the ... It takes a summary from a select query and gives the ... KitID, long integer ...
    (microsoft.public.access.forms)
  • Re: SCAN.EXE - McAfee AntiVirus Software
    ... > | of network computers and have only report summaries sent to be via ... > | Virus Scan Report File ... > | application RemoteProcessLaunch. ...
    (microsoft.public.security.virus)
  • Re: Populating a list -- table structure?
    ... I don't mean to skip your responce below, but thanks to your help with SQL, I was able to get the query to pull the info the way I needed. ... I have one report complete, ... Queries (just shows the QBE grid for convenience -- ...
    (microsoft.public.access.forms)