How to Use the debug diagnostic tool to solve a process that does not respond in IIS

SummaryThis article describes how to use the debug and diagnosis tool v1.2 to solve the problem that the Microsoft Internet Information Services (IIS) process has stopped responding. Back to the top | provide feedback when the IIS (such as Inetinfo.exe, Dllhost.exe, or W3wp.exe process stops responding (Hangs), you may encounter the following symptoms: the Web page is incorrectly loaded. For example, the Web page is displayed as blank or the response is stopped. You may encounter performance degradation on the server that runs IIS. For example, if the progress bar is slow, you can move it to view the Web page, or you will notice the following message in the status bar: the website found. Waiting for a response to IIS 6.0 or later running on the server, warning messages similar to one of the following are written into the System Log: Warning Message 1 event type: Warning Source: IISService event category: no event ID: February 1, 1013 Description: The application pool has exceeded the time limit, and the process that provides services in the process is closed. The process id is the result '. Warning message2 event type: Warning Source: IISService event category: No event ID: July 22, 1010 Note: processes that provide application pool services cannot respond to ping. Process id is the result. Note that IISService is an IIS service running on a computer. The result is the process ID of the running process on the computer. This article discusses how to install and configure debugging diagnostic tools. The debugging diagnostic tool can be used to check whether the IIS process has stopped responding when the IIS process has stopped responding. We recommend that you create a full memory dump file for the IIS process when IIS processes client requests. You can use the debug diagnostic tool to capture and analyze the memory dump files that are captured when IIS processes client requests. To install and configure the debugging diagnostic tool, follow these steps: download and install the debugging diagnostic tool. To install the debugging diagnostic tool, visit the following Microsoft Website: http://www.microsoft.com/download/en/details.aspx?id=26798 Note: If you are configuring a debug diagnostic tool for IIS 6.0 or later, go to step 3. Disable the exception capture function on Microsoft Internet Information Services 5.1 and Microsoft Internet Information Services 5.0. To perform this operation, perform the following steps: single-click Start, single-click Run, click inetmgr.exe, and then click OK. right-click the computer you want to configure and click Properties. in the master shape property list, click WWW Service, and then click Edit. on the Home Directory tab, click Configure. on the process options tab, click to clear the Enable exception capture debugging check box, and then click OK. restart IIS. You must restart IIS to make the change take effect. Create a dump file by using one of the following methods: Create a performance rule. To perform this operation, perform the following steps: Click Start, click Run, type the path of the debugging diagnostic tool, and then click OK. note that by default, the location debugging diagnostic tool in the C: \ Program Files \ DebugDiag folder is used. On the Rules tab, click Add rule. click performance, select the HTTP response time, and then click Next. click Add URL, type the problem on it, click OK, and then click the URL of the Web site to test the URL. Click OK, and then click Next. click Add dump target. in the target type list, click expected, click OK, and then click Next. enter the rule name, path of the user dump file location, and click $ next. click Activate rule now, and then click Finish. on the rule tab, note that the rule is active in the Status column. Manually create an IIS suspension dump file. To perform this operation, perform the following steps: Click Start, click Run, type the path of the debugging diagnostic tool, and then click OK. note that by default, the location debugging diagnostic tool in the C: \ Program Files \ DebugDiag folder is used. On the tool menu, click Create iis com + pause dump/. The process that creates the user dump file. To perform this operation, perform the following steps: Click Start, click Run, type the path of the debugging diagnostic tool, and then click OK. note that by default, the location debugging diagnostic tool in the C: \ Program Files \ DebugDiag folder is used. On the process tab, right-click the process you want to troubleshoot, and then click Create complete user dump. Analyze the dump file. To analyze the dump file, perform the following steps: Click Start, click Run, type the path of the debug diagnostic tool, and then click OK. note that by default, the location debugging diagnostic tool in the C: \ Program Files \ DebugDiag folder is used. On the advanced analysis tab, click Add data file. find and click you want to analyze, dump the file, and then click open. on the advanced analysis tab, click crash/suspend analysis, and then click Start analysis. view the reports displayed in Microsoft Internet Explorer. Copies of this report are also stored in the \ DebugDiag \ Reports folder. Note: If you want to troubleshoot a custom DLL, You can include a custom PDB file. To include custom PDB files, click Options and settings on the tool menu, click folders and search paths, In the debug symbol Search Path box, type a path, and click OK