50
votes

Anyone have any idea how to go about resolving this error? This is happening on my live server, but when i run the project local pc or different server there is no error

Server Error in '/' Application. 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.]

2
Normally a 0x80004005 code is something with access denied, can you provide the stacktrace and some code? - Peter
peer: this is all what i got (copied everything what was in page) & this is why i got so confused... - cpoDesign
I have exactly the same issue in my environment. When I'm working on dev , or locally no errors. But when I'm working on live environment, it gives me the same issue. I've tried to change the timeout value of IIS in the live server machine , but nothing changed. And the solution down here won't help. - UnuS76
I see this, too, on a request that should take no more than 1 second. looking for tips on where it can be getting stuck. - Garr Godfrey

2 Answers

98
votes

I don't know if there's any underlying problem, but to solve the timeout issue you can specify the request timeout (in seconds) in the web.config, like this:

<httpRuntime executionTimeout="300" />

For context, here's a complete web.config with just this setting:

<configuration>
    <system.web>
        <httpRuntime executionTimeout="300" />
    </system.web>
</configuration>
5
votes

Open IIS -> click on the your siteName -> configuration Editor on the Section, scroll to system.web/httpRuntime. Increase the executionTimeout to the time you think it will take to execute your process...

You can also set it in the web.config like the answer above However in my case it work when I do it from IIS.