Hello Wei
Please use Debug Diag to capture IIS crashes on your web server. Here are
several good turtuorials telling how to do it:
http://www.shanmcarthur.net/technical-topics/debugging-a-crashing-iis-websit
e
http://blogs.msdn.com/tess/archive/2008/05/21/debugdiag-1-1-or-windbg-which-
one-should-i-use-and-how-do-i-gather-memory-dumps.aspx
IIS Diagnostics Toolkit (x86)
http://www.microsoft.com/downloads/details.aspx?familyid=9BFA49BC-376B-4A54-
95AA-73C9156706E7&displaylang=en
IIS Diagnostics Toolkit (x64)
http://www.microsoft.com/downloads/details.aspx?familyid=7E42B310-B2D1-496B-
8005-9D91782B9995&displaylang=en
Step 1 Download and install the tool on your web server.
Step2. Run the Debug Diagnostics Tool. The first time it is run, a wizard
will be presented.
Select Crash to set up a crash dump rule. Click Next.
Select "All IIS related processes". Click Next.
Select "Mini Userdump" for first chance exceptions. Set a limit. Click
Next.
Type in a rule name and path or use the defaults. Click Next.
Click Finish.
Step3. Wait for an IIS crash. Confirm the minidump file - it should have
first chance exception or second chance exception in the filename.
Step4. Click on the rule and select Deactivate after you have a good crash
dump. This will allow IIS to run in regular mode without having the
debugger attached.
Please follow the steps to get the crash dump, then you can either send the
dump to me or attempt to analyze it on your side with windbg.
Regards,
Jialiang Ge
Microsoft Online Community Support
=================================================
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
***@microsoft.com.
This posting is provided "AS IS" with no warranties, and confers no rights.
=================================================