IIS hanging

I've got an IIS5 on WIN2K server that hangs intermittantly, one of the
DLLHOST.EXE processes just gobbles up gigs of mem. I have a number of other
sites running the same code (asp pages talking to SQL server) including 2 on
the same server, none have had any problems. When it hung the last time it
hung I tried the IISDump.exe and below is the result:------- Anyone have any
ideas what could be wrong or what else I can do to figure out whats
happening?????


IIS Debug Dump Utility v01.01.00.3800 (File Version 2003.07.22.0
Microsoft Corporation (c)2003. All Rights Reserved.

Command line:
"C:\IISDebugTools\IISDump.exe"


Log files will be placed at:
C:\IISDebugTools\logs\20031001-175424\

Running specified commands. This may take a few minutes...
Processing Application Event Log.
Processing IIS Metabase...
Processing debug script for target process: 4448...
Processing debug script for target process: 2260...
GetSysInfo failed against process 2100.
Error code: 0 (0)
Processing debug script for target process: 4084...
Processing debug script for target process: 3848...
Processing debug script for target process: 2516...
Processing debug script for target process: 2900...
Processing modules in: C:\WINNT\SYSTEM32\INETSRV\...
Application Event Log completed.
Processing System Event Log.
IIS Metabase log completed.
System Event Log completed.
IISDump.EXE [cec.604] GetSysFileInfo(): LoadLibraryExW failed for
C:\WINNT\SYSTEM32\INETSRV\HTTPEXT.DLL. GetLastError: 5 [ sysinfo.cxx(1516) ]
Finished processing modules in: C:\WINNT\SYSTEM32\INETSRV\.
Processing modules in: C:\WINNT\SYSTEM32\...
Debug script for target process 2900 completed.
Debug script for target process 2260 completed.
Debug script for target process 3848 completed.
Debug script for target process 4448 completed.
Debug script for target process 4084 completed.
Debug script for target process 2516 completed.
Finished processing modules in: C:\WINNT\SYSTEM32\.
Processing modules in: CLSID...
Finished processing modules in: CLSID.
Processing modules for target process: 4448...
Finished processing modules for target process: 4448.
Processing modules for target process: 2260...
Finished processing modules for target process: 2260.
Processing modules for target process: 4084...
Finished processing modules for target process: 4084.
Processing modules for target process: 3848...
Finished processing modules for target process: 3848.
Processing modules for target process: 2516...
Finished processing modules for target process: 2516.
Processing modules for target process: 2900...
Finished processing modules for target process: 2900.
SysInfo log completed.

IIS Debug Dump completed. Log files may be found at:
C:\IISDebugTools\logs\20031001-175424\



Rgds

Kieran

What you listed is the log file created. The .dmp for the process that hung
is going to possibly have the necessary information needed to see what is
causing the problem. You can also look at the .log file for the problematic
process and see if that shows any information. The .dmp file can be read
using windbg. I've listed an article that discusses getting windbg.

313109 HOW TO: Find the Problem Exception Stack When You Receive an
http://support.microsoft.com/?id=313109

192754 HOWTO: Debug InProc COM Components Inside IIS Using WINDBG
http://support.microsoft.com/?id=192754

Thank you for choosing Microsoft
Miriam Green
Microsoft Developer Support

This posting is provided “AS IS” with no warranties, and confers no rights.
You assume all risk for your use. © 2002 Microsoft Corporation. All rights
reserved.