For a production Win2003 web server, I’d like to be able to allways log minidumps whenever the w3wp.exe processes crash…I’ve read the documentation for ADPLUS, and have xcopy-deployed it to the production web server, and have started adplus.exe from the command line as follows:
adplus.exe -crash -MiniOnSecond -NoDumpOnFirst -pmn w3wp.exe -o C:\Dumps
This does log the “MiniOnSecond,” but it is also logging full dumps on first–and I don’t want those (they’re big fat files, and don’t have what I need). Has anyone found a way to get the “-NoDumpOnFirst” flag to actually work? Additionally, I’d like this behavior every time the box is rebooted–How can that be accomplished without running a batch file on-reboot? I’ve read about Windows Error Reporting (WER), and it is trivial to impliment this behavior on a Win2008R2 server–how to make that work on a 2003 server?
I’ve read the documentation for both ADPLUS and WER–but I need help with the actually command line and/or registry settings to make capturing minidumps simple on a Win 2003 Server. Thanks for your help!
I played with the configuration file that can be attached with the
-cflag…since i’m mostly interested in catching errors in my custom COM components, these settings create minidumps without fulldumps, and ignore CLR crashes, and don’t full-dump on IISReset.To have this run all the time, create a scheduled task. From an admin prompt:
Save this file as C:\Program Files\Debugging Tools for Windows (x86)\adplus_w3wp.xml
:
Can anyone improve on this? Have I missed any important crashing exceptions?