Sounds like you are running some program on IIS that is crashing it... and
it happens frequently.
Either use IIS State and attach to all the w3wp.exe and wait for the crash.
http://www.iisfaq.com/default.aspx?view=P197
Or configure a debugger to attach to all W3WP.EXE and catch the crash
red-handed. Download the debugger from here:
http://www.microsoft.com/whdc/devtools/debugging/default.mspx
Run this to configure debuggers for IIS:
SC CONFIG W3SVC type= interact type= share
REG ADD "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Image File
Execution Options\w3wp.exe" /v Debugger /d "NTSD.EXE -g -G" /t REG_SZ /f
NET STOP W3SVC & NET START W3SVC
If you make a request, you should see a debugger window pop up, attached to
a w3wp.exe.
Run this to remove the debuggers from IIS:
SC CONFIG W3SVC type= share
REG DELETE "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Image File
Execution Options\w3wp.exe" /v Debugger /f
NET STOP W3SVC & NET START W3SVC
--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Jeff Dillon" <jeff.RemoveThis@removemeemergencyreporting.com> wrote in message
news:esQEPuJTEHA.3700@TK2MSFTNGP09.phx.gbl...
We are running Windows 2003 Server here, and several times a day, we get in
the Event Log:
Faulting application w3wp.exe, version 6.0.3790.0, faulting module unknown,
version 0.0.0.0, fault address 0x00000000.
All current users lose their sessions, and have to log back in. I'm assuming
IIS automatically restarts. How do we do postmortem analysis?
What is the supported exception monitor for IIS6? Anything else we can look
for??
thx
Jeff
FAQ
Profile
Private Messages
Log in
