I really like to use ProcDump for troubleshooting crashes, memory/cpu utilization issues and hangs. I have written a number of other blogs that discuss how to use it here, here and here. The tool is small and unobtrusive, yet very powerful. The new version of the tool has recently been released and can be downloaded […]
Read More →Sometimes when I execute: !runaway in WinDbg I receive the following error: ERROR: !runaway: extension exception 0x80004002. “Unable to get thread times – dumps may not have time information” The error message says it all, but how do you fix it. In my case ProcDump was used to create the dump and it appears that […]
Read More →I have written articles about how to capture a W3WP memory dump on Windows 2003 and Windows 2008. Once you have the memory dump, you need to analyze it to find out what is causing the problem. One command I use while analyzing a memory dump is !DumpThreadConfig or !dtc. Figure 1 shows the output […]
Read More →
When you are troubleshooting IIS issues there are tools like Failed Request Tracing, IIS logs, etc. which will let you see what is going on. But what do you do when IIS itself is not working? A common cause is that the applicationHost.config file is corrupted. Perhaps there was a manual modification made to it […]
Read More →On a web server with multiple application pools, there most likely will be multiple W3WP processes. Therefore, the first action to take when creating a memory dump of a W3WP worker process is to find which W3WP process you need to get the dump of. To do this, open IIS 7 and select the web […]
Read More →When you have multiple websites running under different application pools on the same server, you may need to trouble shoot a specific worker process. On Windows 2003 and Internet Information Services 6 (IIS6), I use the iisapp.vbs script as shown in following command, as shown in Figure 1: Figure 1, Find AppPoolId using IIS 6 […]
Read More →