"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.
Evertjan. - 11 Sep 2008 20:44 GMT
=?Utf-8?B?SnVzdGluIERvaA==?= wrote on 11 sep 2008 in
microsoft.public.inetserver.asp.db:
> "Active Server Pages error 'ASP 0113'
> Script timed out"
[quoted text clipped - 14 lines]
> .ConnectionTimeout = 4800
> .CommandTimeout = 4800
Please do not multipost on usenet

Signature
Evertjan.
The Netherlands.
(Please change the x'es to dots in my emailaddress)
Ted Dawson - 12 Sep 2008 02:35 GMT
> "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.
Obviously IUSR is connecting to the database, but the script times out? IUSR
may not have adequate permission to run the query.
KEN - 03 Oct 2008 21:54 GMT
It's probably not in the connection to SQL or the query but some loop
in the code that is running so long that it's timing out.
Check the loops ie where your moving through the record set.
On Sep 11, 12:45 pm, Justin Doh <Justin...@discussions.microsoft.com>
wrote:
> "Active Server Pages error 'ASP 0113'
> Script timed out"
[quoted text clipped - 17 lines]
> Any idea?
> Thanks.