Running such a long request out of an ASP.Net page is a bad idea as it ties up a system thread for that whole time. I would presume nobody is waiting for that request to complete, so I would suggest offloading it to some sort of worker process (an Async manager if you need a response or a queue that handles this and other long requests).


+++ Rick ---

>An ASP.NET page calls a method on an COM EXE. The request is a report that should take about 20 minutes to finish. In the web.config I've upped the executionTimeOut to 1 hour (as below).
>
>

>   <httpRuntime
>			maxRequestLength="4096"
>			executionTimeout="3600"
>	/>
>

>
>The ASP.NET page still times out after 3 minutes with the error message below. Any idea why the timeout is still happening?
>
>***
>Server Application Unavailable
>The web application you are attempting to access on this web server is currently unavailable. Please hit the "Refresh" button in your web browser to retry your request.
>
>Administrator Note: An error message detailing the cause of this specific request failure can be found in the system event log of the web server. Please review this log entry to discover what caused this error to occur.
>****