# asp.net – How to increase request timeout in IIS?

## The Question :

152 people think this question is useful

How to increase request timeout in IIS 7.0? The same is done under application tab in ASP configuration settngs in IIS 6.0. I am not able to find the asp.net configuration section in IIS 7.0

185 people think this answer is useful

<system.web>
<httpRuntime executionTimeout="180" />
</system.web>



https://msdn.microsoft.com/en-us/library/e1f13641(v=vs.85).aspx

Optional TimeSpan attribute.

Specifies the maximum number of seconds that a request is allowed to execute before being automatically shut down by ASP.NET.

This time-out applies only if the debug attribute in the compilation element is False. To help to prevent shutting down the application while you are debugging, do not set this time-out to a large value.

The default is “00:01:50” (110 seconds).

72 people think this answer is useful

In IIS Manager, right click on the site and go to Manage Web Site -> Advanced Settings. Under Connection Limits option, you should see Connection Time-out.

48 people think this answer is useful

To Increase request time out add this to web.config

<system.web>
<httpRuntime executionTimeout="180" />
</system.web>



and for a specific page add this

<location path="somefile.aspx">
<system.web>
<httpRuntime executionTimeout="180"/>
</system.web>
</location>



The default is 90 seconds for .NET 1.x.

The default 110 seconds for .NET 2.0 and later.

29 people think this answer is useful

In IIS >= 7, a <webLimits> section has replaced ConnectionTimeout, HeaderWaitTimeout, MaxGlobalBandwidth, and MinFileBytesPerSec IIS 6 metabase settings.

Example Configuration:

<configuration>
<system.applicationHost>
<webLimits connectionTimeout="00:01:00"
dynamicIdleThreshold="150"
minBytesPerSecond="500"
/>
</system.applicationHost>
</configuration>



For reference: more information regarding these settings in IIS can be found here. Also, I was unable to add this section to the web.config via the IIS manager’s “configuration editor”, though it did show up once I added it and searched the configuration.

18 people think this answer is useful

Below are provided steps to fix your issue.

2. Go to “Sites” option.
3. Mouse right click.
4. Then open property “Manage Web Site“.
5. Then click on “Advance Settings“.
6. Expand section “Connection Limits“, here you can set your “connection time out

11 people think this answer is useful

If you have a server behind the IIS 7.5 (e.g. Tomcat). In my case I have a server farm with Tomcat server configured. In such case you can change the timeout using the IIS Manager:

• go to Server Farms -> {Server Name} -> Proxy
• change the value in the Time-out entry box
• click Apply (top-right corner)

or you can change it in the cofig file:

• open %WinDir%\System32\Inetsrv\Config\applicationHost.config
• adjust the server webFarm configuration to be similar to the following

Example:

<webFarm name="${SERVER_NAME}" enabled="true"> <server address="${SERVER_ADDRESS}" enabled="true">
<applicationRequestRouting httpPort="${SERVER_PORT}" /> </server> <applicationRequestRouting> <protocol timeout="${TIME}" />
</applicationRequestRouting>
</webFarm>



The \${TIME} is in HH:mm:ss format (so if you want to set it to 90 seconds then put there 00:01:30)

In case of Tomcat (and probably other servlet containers) you have to remember to change the timeout in the %TOMCAT_DIR%\conf\server.xml (just search for connectionTimeout attribute in Connector tag, and remember that it is specified in milliseconds)

3 people think this answer is useful

Use the below Power shell command to change the execution timeout (Request Timeout)

Please note that I have given this for default web site, before using these please change the site and then try to use this.

 Set-WebConfigurationProperty -pspath 'MACHINE/WEBROOT/APPHOST/Default Web Site'  -filter "system.web/httpRuntime" -name "executionTimeout" -value "00:01:40"



Or, You can use the below C# code to do the same thing

using System;
using System.Text;

internal static class Sample {

private static void Main() {

using(ServerManager serverManager = new ServerManager()) {
Configuration config = serverManager.GetWebConfiguration("Default Web Site");

ConfigurationSection httpRuntimeSection = config.GetSection("system.web/httpRuntime");
httpRuntimeSection["executionTimeout"] = TimeSpan.Parse("00:01:40");

serverManager.CommitChanges();
}
}
}



Or, you can use the JavaScript to do this.

var adminManager = new ActiveXObject('Microsoft.ApplicationHost.WritableAdminManager');

appcmd.exe set config "Default Web Site" -section:system.web/httpRuntime /executionTimeout:"00:01:40"