Board index Windows

Moderator: chandranjoy

IIS - Diagnostics - Troubleshooting

Postby chandranjoy » Sun Nov 21, 2010 3:35 pm

How to use the Debug Diagnostics tool to troubleshoot a process that has stopped responding in IIS
http://support.microsoft.com/kb/919792/en-us
IIS Diagnostics Tool:
http://www.microsoft.com/downloads/en/d ... laylang=en

IIS Error Log location:

%SYSTEMROOT%\System32\LogFiles\HTTPERR\

When an IIS process stops responding, we recommend that you create a full memory dump file of the IIS process while IIS is processing client requests. You can use the Debug Diagnostics tool to capture and analyze memory dump files that are captured when IIS is processing client requests.

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

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

Note The Debug Diagnostics Tool 1.0 is included with the IIS Diagnostics Toolkit.
http://www.microsoft.com/downloadS/deta ... laylang=en (http://www.microsoft.com/downloadS/deta ... laylang=en)
Note If you are configuring the Debug Diagnostics tool for use with IIS 6.0, go to step 3.
2. In Microsoft Internet Information Services 5.1 and in Microsoft Internet Information Services 5.0, turn off the debug exception catching feature. To do this, follow these steps:
1. Click Start, click Run, type Inetmgr.exe, and then click OK.
2. Right-click the computer that you want to configure, and then click Properties.
3. In the Master Properties list, click WWW Service, and then click Edit.
4. On the Home Directory tab, click Configuration.
5. On the Process Options tab, click to clear the Enable debug exception catching check box, and then click OK.
6. Restart IIS. You must restart IIS for this change to take effect.
3. Create a dump file by using one of the following methods:
* Create a hang rule. To do this, follow these steps:
1. Click Start, click Run, type the path of the Debug Diagnostics tool, and then click OK.

Note By default, the Debug Diagnostics tool is located in the C:\Program Files\IIS Resources\DebugDiag folder.
2. On the Rules tab, click Add Rule.
3. Click IIS Hang, and then click Next.
4. Click Add URL, type the URL for a Web site on which you experience the issue, click OK, and then click Yes to test the URL.
5. Click OK, and then click Next.
6. Click Add Dump Target.
7. In the Target Type list, click the target type that you want, click OK, and then click Next.
8. Type a name for the rule, type a path for the user dump file location, and then click Next.
9. Click Activate the rule now, and then click Finish.
10. On the Rules tab, notice that the rule is Active in the Status column.
* Manually create an IIS Hang Dump file. To do this, follow these steps:
1. Click Start, click Run, type the path of the Debug Diagnostics tool, and then click OK.

Note By default, the Debug Diagnostics tool is located in the C:\Program Files\IIS Resources\DebugDiag folder.
2. On the Tools menu, click Create IIS Hang Dump.
* Create a user dump file for a process. To do this, follow these steps:
1. Click Start, click Run, type the path of the Debug Diagnostics tool, and then click OK.

Note By default, the Debug Diagnostics tool is located in the C:\Program Files\IIS Resources\DebugDiag folder.
2. On the Processes tab, right-click the process that you want to troubleshoot, and then click Create Full Userdump.
4. Analyze the dump file. To analyze the dump file, follow these steps:
1. Click Start, click Run, type the path ofthe Debug Diagnostics tool, and then click OK.

Note By default, the Debug Diagnostics tool is located in the C:\Program Files\IIS Resources\DebugDiag folder.
2. On the Advanced Analysis tab, click Add Data Files.
3. Locate and then click the dump file that you want to analyze, and then click Open.
4. On the Advanced Analysis tab, click Crash/Hang Analysis, and then click Start Analysis.
5. Review the report that is displayed in Microsoft Internet Explorer. A copy of this report is also stored in the IIS Resources\DebugDiag\Reports folder.

Note If you want to troubleshoot a custom DLL, you can include the custom PDB files. To include the custom PDB files, click Options and Settings on the Tools menu, click Folder and Search Paths, type the path in the Symbol Search Path for Debugging box, and then click OK.

IIS Troubleshooting :


Users receive a "The page cannot be displayed" error message, and "Connections_refused" entries are logged in the Httperr.log file on a server that is running Windows Server 2003, Exchange 2003, and IIS 6.0


http://support.microsoft.com/kb/934878

SYMPTOMS
You experience the following symptoms on a server that is running Microsoft Wind...
You experience the following symptoms on a server that is running Microsoft Windows Server 2003, Microsoft Exchange Server 2003, and Microsoft Internet Information Services (IIS) 6.0:

* When a user tries to use Microsoft Office Outlook Web Access or view a Web page that is hosted on the server, the user receives the following error message:
The page cannot be displayed.
The page you are looking for is currently unavailable. The Web site might be experiencing technical difficulties, or you may need to adjust your browser settings.

Cannot find server or DNS Error.
* When you view the Httperr.log file, you see multiple occurrences of entries that resemble the following:
Number_Connections_refused

Notes

* You must have error logging enabled for the HTTP APIs.
* The Httperrlog_number.log file is located in the following folder:
\System32\LogFiles\HTTPERR

CAUSE
This issue occurs if less than 20 megabytes (MB) of nonpaged pool memory is avai...
This issue occurs if less than 20 megabytes (MB) of nonpaged pool memory is available on the server. When less than 20 megabytes (MB) of nonpaged pool memory is available, the Http.sys kernel mode driver stops accepting new connections.

This issue may occur in situations in which the /3GB switch is enabled in the Boot.ini file on the server.

WORKAROUND
Important This section, method, or task contains steps that tell you how to modi...
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 (http://support.microsoft.com/kb/322756/ ) How to back up and restore the registry in Windows


To work around this issue, add the EnableAggressiveMemoryUsage registry entry to the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP\Parameters
Then, set the EnableAggressiveMemoryUsage registry entry to 1.

To do this, follow these steps:

1. Click Start, click Run, type regedit in the Open box, and then click OK.
2. Click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP\Parameters
3. On the Edit menu, point to New, and then click DWORD Value.
4. Type EnableAggressiveMemoryUsage, and then press ENTER.
5. On the Edit menu, click Modify.
6. In the Value data box, type 1, and then click OK.
7. On the File menu, click Exit to exit Registry Editor.
8. Restart the HTTP service. To do this, follow these steps:
1. Click Start, click Run, type cmd in the Open box, and then click OK.
2. At the command prompt, type net stop http /y, and then press ENTER.
3. At the command prompt, type iisreset /restart, and then press ENTER.


Enjoy folks :)
chandranjoy
Site Admin
 
Posts: 283
Joined: Fri Oct 23, 2009 11:19 pm

Return to Windows

Who is online

Users browsing this forum: No registered users and 1 guest


cron