by dotnetpete
21. January 2009 11:40
Had a long running process that was kicked off from an ASP.NET page which was getting the request timeout error below:
Request timed out.
Description: An unhandled exception occurred during the execution of the current webrequest. Please review the stack trace for more information about the error andwhere it originated in the code.
Exception Details: System.Web.HttpException: Request timed out.
Source Error:
| An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. |
Stack Trace:
| [HttpException (0x80004005): Request timed out.] |
I knew that the SQL was not timing out because I would hgacve
I was able to solve this by adding a httpRuntime element called executionTimeout to the web.config under the system.web section. This value is in seconds and the default is 90 (for .NET 1.0 and 1.1) or 110 otherwise.
The full specification for httpRuntime can be found here.
c13a6eeb-8599-492c-ab52-0110a81edf8e|0|.0
Tags:
General | SQL
Subscribe