Hello,
I have written a fairly complex ASP page which does some file processing, and can take up to an hour to execute. This normally works fine, but recently has started having problems.
I have placed proper error handling into the code to report any errors back to the user in a controlled manner. I have also used the Server.ScriptTimeOut instruction to ensure the ASP page has enough time to complete.
The problem I am having is that an error is occurring after about 30 mins, but by this time the browser has given up trying to retrieve the page, so the displayed error message does not appear. Is there any way to extend the maximum period of time that the browser waits for a page to be retrieved? The alternative is that I write the resulting error message to a file, but I would rather not do this for general debugging.
Thanks for any help you can offer
Mark
I have written a fairly complex ASP page which does some file processing, and can take up to an hour to execute. This normally works fine, but recently has started having problems.
I have placed proper error handling into the code to report any errors back to the user in a controlled manner. I have also used the Server.ScriptTimeOut instruction to ensure the ASP page has enough time to complete.
The problem I am having is that an error is occurring after about 30 mins, but by this time the browser has given up trying to retrieve the page, so the displayed error message does not appear. Is there any way to extend the maximum period of time that the browser waits for a page to be retrieved? The alternative is that I write the resulting error message to a file, but I would rather not do this for general debugging.
Thanks for any help you can offer
Mark