Resolve processes that are not responding in IIS

Profile

This article describes how to use the Debug Diagnostic v1.2 tool to troubleshoot a Microsoft Internet information Services (IIS) process that has stopped responding.

Back to Top | Provide feedback

When IIS (such as the Inetinfo.exe, Dllhost.exe, or W3wp.exe process stops responding (hangs), you may experience the following symptoms:

The Web page is not loaded correctly. For example, the Web page appears empty or stops responding.

You are experiencing performance degradation on the server running IIS. For example, if the progress bar is slow to move you try to view the Web page, or you will notice the message shown in the status bar as follows:

Found the site. Waiting for reply

IIS version 6.0 or later running on the server warns that messages similar to one of the following are written to the system log:

Warning message 1

Event Type: Warning

Source: Iisservice

Event Category: None

Event id:1013 Year

Description: The application pool exceeds the time limit, and the process that provides the service is closed. Process ID is result '.

Warning Message2

Event Type: Warning

Source: Iisservice

Event Category: None

Event id:1010 Year

Description: Provides application pool services such a process cannot respond to a ping. Process ID is result '.

Note Iisservice is an IIS service that is running on a computer. The result is the process ID of the process that is running on the computer.

This article discusses how to install and configure the Debug Diagnostics tool. Debug Diagnostics tool can be used to troubleshoot the IIS process has stopped responding

When the IIS process stops responding, we recommend that you create a full memory dump file for the IIS process that is created when IIS processes client requests. You can use the Debug Diagnostics tool to capture and analyze a memory dump file when IIS processes client requests.

To install and configure the Debug Diagnostics tool, follow these steps:

Download and install the Debug Diagnostics tool. To install the Debug Diagnostics tool, visit the following Microsoft Web site:

http://www.microsoft.com/download/en/details.aspx?id=26798 Note If you are configuring the Debug Diagnostics tool for use with IIS 6.0 or later, go to step 3.

Turn off the debug Exception capture feature at Microsoft Internet Information Services 5.1 and Microsoft Internet Information Services 5.0. To perform this action, perform the following steps:

Click Start, click Run, type Inetmgr.exe, and then click OK.

Right-click the computer that you want to configure, and then click Properties.

In the Master Properties list, click the WWW service, and then click Edit.

On the Home Directory tab, click Configure.

Process Options tab, click to clear the Enable Exception capture debugging check box, and then click OK.

Restart IIS. You must restart IIS for this change to take effect.

Create a dump file by using one of the following methods:

Create a performance rule. To perform this action, perform the following steps:

Click Start, click Run, type the path to the Debug Diagnostics tool, and then click OK.

Note By default, C:Program the location in the Filesdebugdiag folder to debug the Diagnostics tool.

On the Rules tab, click Add Rule.

Click Performance, select the time of the HTTP response, and then click Next.

Click the Add URL, type the problem you are experiencing, click OK, and then click the URL of the Web site that is to test the URL.

Click OK, and then click Next.

Click Add Dump Target.

In the list of target types, click the desired, click OK, Target type, and then click Next.

Type a name for the rule, type a path for the location of the user dump file, and then click $ Next.

Click the Activate rule now, and then click Finish.

On the Rules tab, note that the rule is active in the Status column.

Manually create an IIS suspend dump file. To perform this action, perform the following steps:

Click Start, click Run, type the path to the Debug Diagnostics tool, and then click OK.

Note By default, C:Program the location in the Filesdebugdiag folder to debug the Diagnostics tool.

On the Tools menu, click Create IIS COM + Suspend dump/.

The process of creating a user dump file. To perform this action, perform the following steps:

Click Start, click Run, type the path to the Debug Diagnostics tool, and then click OK.

Note By default, C:Program the location in the Filesdebugdiag folder to debug the Diagnostics tool.

On the Process tab, right-click the process you want to troubleshoot, and then click Create Full User dump.

Analyze the dump file. To analyze the dump file, follow these steps:

Click Start, click Run, type the path to the Debug Diagnostics tool, and then click OK.

Note By default, C:Program the location in the Filesdebugdiag folder to debug the Diagnostics tool.

In the Advanced Analysis tab, click Add Data File.

Locate and click the file you want to analyze, dump, and then click Open.

On the Advanced Analysis tab, click Crash/Suspend analysis, and then click Start Profiling.

View the reports that are displayed in Microsoft Internet Explorer. A copy of this report is also stored in the Debugdiagreports folder.

Note If you are troubleshooting a custom DLL, you can include a custom PDB file. To include a custom PDB file, click Options and Settings on the Tools menu, click the folder and search path, type the path in the Debug symbol search Path box, and then click OK