error 'ASP 0113'

Question

Post reply

error 'ASP 0113'

tyang

SSCrazy

Points: 2231
More actions
September 4, 2003 at 7:44 am

#64721

The client keeps getting error 'ASP 0113'.

Script timed out.

/formDGVBody.asp

The maximum amount of time for a script to excute was exceeded.

I checked MS knowledge base on the ASP and IIS issues, but also notice that an increase in timeout value can have a negative effect on server performance. You should design scripts that run within the default timeout settings. For example, an increase in script timeout value can keep IIS threads occupied and reduce the number of users that the server can serve.

Can anyone give me a suggestion?

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

Frank Kalis SSC Guru Points: 111183 More actions · Answer 1

quote:

The client keeps getting error 'ASP 0113'.

Script timed out.

/formDGVBody.asp

The maximum amount of time for a script to excute was exceeded.

I checked MS knowledge base on the ASP and IIS issues, but also notice that an increase in timeout value can have a negative effect on server performance. You should design scripts that run within the default timeout settings. For example, an increase in script timeout value can keep IIS threads occupied and reduce the number of users that the server can serve.

Can anyone give me a suggestion?

without having further information a suggestion will be like a shot in the dark.

I increased CommandTimout or ConnectionTimeout?!? (will investigate which) for a small transfer app that stores LOB's in my db. The default value was too small for this task.

And after all what is better:

Releasing the threads as early as you can or

Having a working app?

Frank

--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/[/url]

Steven. SSCrazy Eights Points: 9806 More actions · Answer 2

Steven.

SSCrazy Eights

Points: 9806

September 4, 2003 at 1:46 pm

#472665

Perhaps it would be worth looking at the code the page was running to try and speed it up.

Steven

Bill Burkett Old Hand Points: 328 More actions · Answer 3

I have increased both timeouts in the ADO script. Sometimes it works and sometimes it does not. However, I start putting the following code in the top of page that timeout.

<% Server.ScriptTimeout = 150 %>

If this is the first line on the page, before the <HTML> tag, then

the page should allow 150 seconds before time out instead of the

usual 90 seconds.

This seemed to have fixed the issue. I have some pages that have this variable set to 600 seconds.