Active Server Pages error 'ASP 0113'

"Active Server Pages error 'ASP 0113'
Script timed out"
>
...<% server.ScriptTimeout = 4000 %>...
>
.ConnectionTimeout = 4800
.CommandTimeout = 4800
>
Any idea?

"Active Server Pages error 'ASP 0113'
Script timed out"
>
I am still getting this error, and I am not sure how I could fix this.
>
When I execute the query at SQL 2005, it only takes 8 seconds.
The stored procedure for this report has been already went through
Database Engine Tuning Advisor to put all the necessary indexes on
the associated tables.
>
It happens when I run this report on other new web server.
>
I already put this on the ASP web page for this report.
>
<% server.ScriptTimeout = 4000 %>
>
.ConnectionTimeout = 4800
.CommandTimeout = 4800
>
Any idea?
Thanks.

Before setting ridiculous timeouts, verify that you need them.
1. use SQL Profiler to run a trace to verify that the stored procedure
is the problem
2. identify the bottleneck in your code if the stored procedure is not
the problem
>
<%
Response.Write "Code start: " & now & "<BR>"
....
Response.Write "Opening connection: " & now & "<BR>"
....
Response.Write "Calling procedure: " & now & "<BR>"
>
....
Response.Write "Processing results: " & now & "<BR>"
....

"Bob Barrows [MVP]" wrote:
>>
But if the problem is an infinite loop of some kind, then you might
want to follow up each of the Response.Write calls with
Response.Flush
to be sure the output gets to the browser.

Also, be sure to *NOT*
output your debug into the <TRrows of a <TABLE>. Even with
Response.Flush, the browser will set there forever waiting for the
terminating </TABLEbefore displaying anything.

Script timed out"
>
I am still getting this error, and I am not sure how I could fix this.
>

...Also, be sure to *NOT* output your debug into the <TRrows of a
<TABLE>. Even with Response.Flush, the browser will set there forever
waiting for the terminating </TABLEbefore displaying anything.

>
Try with a very simple query first to verify connectivity, etc.
>
Jeff
>
>
>

My output is:
I have the error message on the top of web page
>
Active Server Pages error 'ASP 0113'
Script timed out
And then, there is output (report with data)..
>
It retrieved the data fine, but why do I have the error message on the top?

>
"Justin Doh" wrote:
>>
Well, this is a pure guess. But one way it *could* happen would be for you
to have an infinite loop AFTER all of the reporting is done but before the
final </TABLEtag was written.
>
And if your reporting is done into a <TABLEthen the error message, since
it wouldn't be output with <TR><TD>...</TD></TRsurrounding it, then indeed
the browser might show the error message *before* the incomplete <TABLE>.
>
As Dave Anderson might comment, this would likely only happen with MSIE (and
possibly only with pre-MSIE 7 versions), but I have seen it happen with MSIE
6, for sure. (Well, not timeout...but other errors.)
>
You can find out the truth of my guess by inspecting the HTML. Do a
VIEW==>>SOURCE in the browser and look at the HTML (in Notepad, if using
MSIE, by default). See if the error message really is at the bottom of the
HTML text and is simply displaying at the top becuz of MSIE peculiarities.
>
>

You know what.
When I looked at the SOURCE of HTML (notepad), I see the error message on
the bottom.
How do I fix this?

If I were trying to find the moment this timeout occurs, I would put a
Response.Flush() after every Response.Write(), ...

>
>
"Dave Anderson" wrote:
>>
But I think that the problem is occurring at a point in time when he isn't
*doing* any Response.Write calls. Possibly even when he is trying to close
the connection. It would be silly, but if he had something like:
While Err.Number 0
DB.Close
Wend
and if "DB" was already closed at that point...well, kablooey!
>
So I really think we have to see some code.
>

I found the reason.
I had the "response.flush" but I did not have "response.buffer = true" before.
>
Thank you!
>
"Old Pedant" wrote:
>

I found the reason.
I had the "response.flush" but I did not have "response.buffer = true" before.

I found the reason.
I had the "response.flush" but I did not have "response.buffer = true" before.

Response.Buffer=True is the *default* for all modern versions (since
2003 at least, maybe before that) of IIS.

"Old Pedant" wrote:>

FALSE No buffering. The server sends output to the client as it is
processed. This is the default value for versions of IIS 4.0
and earlier. For version 5.0 and later, the default value is
TRUE.
http://msdn.microsoft.com/en-us/library/ms526001.aspx

>
[snip]
>
Or were you agreeing with me? Hmmm...I guess you were. Okay.
Great.

Documentation takes no sides.

"Dave Anderson" wrote:>
LMAO!
>
Only tops and bottoms, huh?
>
>