Resolving a process that provides service to an application pool has exceeded the time-off limit

The process shutdown time for application pool ' xxx ' has exceeded the limit. The process ID is ' 7480 '.
The ID of the hint can be many, such as 3844, 8004, 6124, and so on.
Search on Baidu, found a lot of similar problems, caused by the root cause unknown, but the direct cause of this situation is the IIS failure protection!
For example, setting the failure protection to close the application pool for more than 5 failures per 5 minutes will cause the service to be stopped, at which point the log is:
Application pool ' xxx ' is automatically disabled because of a series of errors in the process that provides services for this application pool.
The solution is as follows:
Internet Information Services (IIS) Manager-> Application pool->defaultapppool-> Properties-> Run status-> start quick fail protection hooks removed!
In order to avoid really encountering a lot of errors without prompting, can not be closed, but to increase the protection of the rapid protection, such as the failure of 50 times every 5 minutes to close the corresponding program pool

http://go.microsoft.com/fwlink/events.asp; Help and Support Center.
Note: ID number, is changed, can be any data such as 3124, each time this error occurs, the ID is not the same!
Server performance: IIS6.0 fake crash, the page can not open, ASP page, cannot be executed! Website can't open

My workaround: The current IIS server application pool settings are as follows:
Right-click the application pool DefaultAppPool and select Properties:
First, recycling
1. Recovery work process (minutes): checked, value is 1740
2. Recovery worker process (number of requests): Not selected (originally set to 35000)
3, the following time to recycle the work process: do not fill
4, consume too much memory when the process of recycling: all do not select. (2, 3, 4 May avoid the high traffic at the time of the forced recycling process may be caused by the server response problem, guess ^-^) server memory is big enough to give it to use.
Second, performance
Only the idle timeout is checked for 20 minutes. None of the other options. The maximum number of worker processes in the Web garden is 1 (default). The original request queue limit is 4000 and is now unrestricted.
Third, the Operation status
The first two entries are used, which is the original default setting. The start time limit is 90 seconds and the closing time limit is 180 seconds.

"Close time limit of 180 seconds" is necessary, because the process is closed time, is set here, the original 90-second limit, is the default value, if the process is closed for more than 90 seconds, it is considered time-out, resulting in: Process shutdown time exceeds the limit log, so, appropriate extension of this time, you can avoid this error!

Process shutdown time for application pool "DefaultAppPool" exceeded limit
The server often produces "application pool" DefaultAppPool "The process shutdown time for services exceeds the limit." The process ID is "2068″." "Error, which causes IIS to be in suspended animation, is known to be an IIS application pool Setup issue. Here's how to fix it:

Internet Information Services (IIS) Manager-> Application pool->defaultapppool-> right-click Properties
First, recycling
1. Recovery work process (minutes): checked, value is 1740
2. Recovery worker process (number of requests): Not selected (originally set to 35000)
3, the following time to recycle the work process: do not fill
4, consume too much memory when the process of recycling: all do not select. (2, 3, 4 items may avoid server response problems that may be caused by forcing the recycle process at high traffic levels , causing IIS to suspend animation)
Second, performance
Only the idle timeout is checked for 20 minutes. None of the other options. The maximum number of worker processes in the Web garden is 1 (default). Note that the Web Park here must remain the default, if you fill in the other more than 1 of the number will cause some of the website program background program can not open or refresh constantly.

The original request queue limit is 4000 and is now unrestricted.
Third, the Operation status
The first two entries are used, which is the original default setting. The start time limit is 90 seconds and the closing time limit is 180 seconds.

Start the quick fail protection hook to remove!
In order to avoid really encountering a lot of errors without prompting, you can not shut down, just to increase the protection of rapid protection, such as the number of failures 50 times the time period of 5 minutes to close the corresponding program.

"Close time limit of 180 seconds" is required, because the process shutdown time, the original 90-second limit, is the default value, if the process is closed for more than 90 seconds, it is considered time-out, resulting in: Process shutdown time exceeds the limit log, so, appropriate extension of this time, can avoid this error

The 2nd method:

Cause: The memory heap constricted of the standalone process is exhausted, and IIS cannot create more process workspaces to handle

Workaround:
1. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC
2. Create a new DWORD entry under the Parameters key named: Usesharedwpdesktop with a value of 1 restart IIS

3rd type

The problem has been resolved, found that the database connection can not be released, do not know what the reason, the same code in the local is good, the server side of the problem, and finally in the connection string to add the following statement to solve the problem.

Pooling=true; MAX Pool size=512; Min Pool size=50; Connection lifetime=30

4th type

Create a new application pool, with different Web sites referencing different program pools.

Resolving a process that provides service to an application pool has exceeded the time-off limit