In the System event log of a computer running Internet Information Services (IIS) 6.0, a Warning message similar to the following is displayed:
Event Type: Warning Event Source: W3SVC Event Category: None Event ID: 1013 Date: 1/1/2011 Time: 12:00:00 AM User: N/A Computer: SERVER Description: A process serving application pool 'DefaultAppPool' exceeded time limits during shut down. The process id was '1111'.
On a computer running Internet Information Services (IIS) 7.0 or 7.5, the message will look similar to the following:
Log Name: System Source: Microsoft-Windows-WAS Date: 1/1/2011 12:00:00 AM Event ID: 5013 Task Category: None Level: Warning Keywords: Classic User: N/A Computer: SERVER Description: A process serving application pool 'DefaultAppPool' exceeded time limits during shut down. The process id was '1111'.
This message is logged to the event log when an application pool takes longer than the configured ShutdownTimeLimit property to shut down. When this time limit is exceeded, the worker process will be forcibly shut down and recycled and the event log message created.
It is possible that this message will appear in the event log without any negative observed behavior to end users browsing the web sites hosted in that application pool. However, the presence of the event suggests one of the following is true:
The ShutdownTimeLimit is set to too low of a number
A problem has occurred inside of the web application that is hindering it from shutting down in a timely manner.
NOTE: The default value of the ShutdownTimeLimit configuration property in IIS is 90 seconds.
To resolve this problem, choose one of the following methods.
Method 1 - Increase the ShutdownTimeLimit value
It is possible that the default ShutdownTimeLimit value was modified from its default value of 90 seconds. It can be expect that an application pool needs time to fully shut down, as any requests currently processing when the shutdown is initiated need to be given a certain amount of time to complete. Setting the ShutdownTimeLimit value too low may cause these erroneous event log warnings in high traffic web applications or in web applications that have requests that are expected to take some time to complete.
To modify the ShutdownTimeLimit value in IIS 6.0, please see the following documentation:
Configuring Startup and Shutdown Time Limits (IIS 6.0)
Method 2 - Troubleshoot why the application pool is not shutting down in a timely manner
As mentioned earlier, it is possible that something is going on inside of the application pool that is hindering it from being able to shut down in a timely manner. One of the more common problems that occur here is when existing HTTP requests are not able to complete. To troubleshoot why the application pool is taking too long to shutdown, capture a memory dump of the w3wp.exe process in which the application pool is running, when the shutdown problem is occurring.
For more information on capturing memory dumps of IIS processes, please see the following documentation regarding the Debug Diagnostics Toolkit v1.2: