The SitePoint Forums have moved.

You can now find them here.
This forum is now closed to new posts, but you can browse existing content.
You can find out more information about the move and how to open a new account (if necessary) here.
If you get stuck you can get support by emailing forums@sitepoint.com

If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

(ASP) "Script timed out" error... huh?!

Hello... I have been getting this error all night on my site...

Active Server Pages error 'ASP 0113'

Script timed out

/howto.asp

The maximum amount of time for a script to execute was exceeded. You can change this limit by specifying a new value for the property Server.ScriptTimeOut or by changing the value in the ASP administration tools.

I dont quite understand why though... I have changed nothing on my scripts and so why would they work fine for days, then all of the sudden begin doing this?

Could someone give me any ideas on how to fix this?

By the way... Its every single ASP page on my site that is returning this... not just a specific one or two.

It's possible that the problem is created by your internet connection or something. When your script does something and your browser doesn't receive it in a timely fashion such things can occur. You may try to use response.buffer=true to buffer all the content and then flush it at the end.

Does the problem occur with all scripts or just those connecting to a db?

If it's all scripts it may be a problem with the server (eg load, config) but if it just affects those connecting to a db then you may want to double check everythings still ok with the db and db connection string.

Download the db (i take it you're using Access) and try opening it. If it opens ok the db's probably ok. Can you try running your site locally? If so, and everything's ok, then it's probably the server thats causing the grief.

As to 'Catostrophic error' try the following link as I posted a couple of urls that may help.