This article will detail the action plan you can implement to create a rule in Debug Diagnostic 1.2 to automate a dump generation when an IIS process is crashing (in example a "W3WP.exe" process).
This action plan can be applied when your W3WP.exe process is crashing which means, in an IIS context, the specified process has been killed or restarted for an obscure reason. This implies a stop of the process and if it has been restarted, a change in the Process ID. You really have to make the difference between a crash and a hang, as configuring a crash rule if you are facing a hang will not generate any dumps.
This will have for effect to only generate a dump on the W3WP.exe process corresponding to your Application Pool
The drawback of "A specific process" for a unique instance is you need to recreate the rule each time the process is restarted as his PID would have changed
The dumps are located by default in "C:\Program Files\DebugDiag\Logs\Crash rule for all IIS_COM+ related processes" or in "C:\Program Files\DebugDiag\Logs\Rule_Name".
We hope this article will help you out.
See you soon.
Sylvain Lecerf and the French IIS Microsoft Support Team