Troubleshoot IIS request timed out issue

How to troubleshoot HttpException Request timed out (ASP.NET 2.0 32-bit)
How to troubleshoot HttpException Request timed out (ASP.NET 4.0 64-bit)
By XinJin

The user may receive the following response intermittently:
Request timed out.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where 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.

——————————————————–
[HttpException (0x80004005): Request timed out.]
The following warning may occur in application event logs:
Log Name: Application
Source: ASP.NET 4.0.30319.0
Event ID: 1309
Task Category: Web Event
Level: Warning
Keywords: Classic
User: N/A
Description:
Event code: 3001
Event message: The request has been aborted.

Application information:

Process information:

Process name: w3wp.exe
Account name: IIS APPPOOL\ASP.NET v4.0
Exception information:
Exception type: HttpException
Exception message: Request timed out.

This kind of issue is typically occurs when the ASP.NET request executes for a period of time longer than the maximum timeout period allowed for server-side code execution.

This maximum timeout period can be set by executionTimeout attribute of httpRuntime element in config file. (The default value is 110 seconds in .Net 4.0)

HttpException “Request timed out” error occurs even if executionTimeout attribute is set to a large value
By XinJin

Request timed out.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where 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.]

This issue typically occurs when the ASP.NET request executes for a period of time longer than the maximum timeout period allowed for server-side code execution.
My customer knows it will take 5 minutes to execute his ASP.NET page because the page needs to retrieve large data from database to generate a report. Therefore he has already set the value of executionTimeout attribute of httpRuntime element to 600 seconds in web.config. However he still receives HttpException “Request timed out” error while the ASP.NET page executes for 2 or 3 minutes.

One thought on “Troubleshoot IIS request timed out issue”

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>