Thursday, April 26, 2007

how to troubleshoot a COM+ exception

Guidelines to follow when crash of COM+ package happen on production environment

1. Don't close crash dialog with prompt to send file to Microsoft, therefore dmp file could saved into another location (details will provide file location) or consider to enable dump for COM+ package
2. Use WinDbg to analyze dump file - download symbols for system where crush happen

Problems:
  • No symbol files available for msxml dlls
  • Debug Diagnostic tools is old and didn't help, gives empty report
  • How to debug crash from another operating system (like use XP to debug 2003)

Resources:

INFO: MTS/COM+ Events 4104 and 4194
http://support.microsoft.com/?id=291365

How to use ADPlus to troubleshoot "hangs" and "crashes"
http://support.microsoft.com/kb/286350/EN-US/

Windows does not save memory dump file after a crash
http://support.microsoft.com/kb/130536

Debug Diagnostic Tool v1.1
http://www.microsoft.com/downloads/details.aspx?FamilyID=28bd5941-c458-46f1-b24d-f60151d875a3&DisplayLang=en

No comments: