What to do about Windows Server 2008 IIS 7 503 Error

Windows 2008 R2 often get a 503-wrong solution when visiting

Error Summary:

HTTP Error 503.2-service Unavailable

The Serverruntime@appconcurrentrequestlimit setting is being exceeded.

Detailed Error Information:

Module IIS Web Core

Notification beginrequest

Handler Staticfile

Error Code 0x00000000

Due to the default configuration used previously, the server can handle up to 5,000 simultaneous requests, and this afternoon due to a situation caused by more than 5000 concurrent requests, resulting in the above error.

To avoid such errors, we adjusted the settings based on the relevant documentation to allow the server to support 100,000 concurrent requests from the setup.

The specific settings are as follows:

1. Adjust the IIS 7 application pool queue Length

Change from the original default of 1000 to 65535.

IIS Manager > ApplicationPools > Advanced Settings

Queue length:65535

2. Adjust the Appconcurrentrequestlimit settings for IIS 7

Change from the original default of 5000 to 100000.

C:windowssystem32inetsrvappcmd.exe Set config/section:serverruntime/appconcurrentrequestlimit:100000

You can view this setting in%systemroot%system32inetsrvconfigapplicationhost.config:

3. Adjust the setting of Processmodel>requestqueuelimit in Machine.config

Change from the original default of 5000 to 100000.

Copy Code

Reference article: http://technet.microsoft.com/en-us/library/dd425294 (office.13). aspx

4. Modify the registry and adjust the number of simultaneous TCPIP connections supported by IIS 7

Change from the original default of 5000 to 100000.

REG ADD hklmsystemcurrentcontrolsetserviceshttpparameters/v maxconnections/t reg_dword/d 100000

By completing the 4 settings above, you can support 100,000 simultaneous requests, and the CC software server has enabled the above settings.