Yuriy's blog

Windows Error Reporting (WER) provides a very useful information for debugging production issues, especially when it comes to the unhandled exceptions. CLR integrates WER seamlessly and gives everything you need to track the issue. WER generates an event log record which gives you a path to the .wer file. A common .wer file contains a section of Problem Signatures Sig[0].Name=Problem Signature 01 Sig[0].Value=WerTest.exe Sig[1].Name=Problem Signature 02 Sig[1].Value=1.0.0.0 Sig[2].Name=Problem Signature 03 Sig[2].Value=5b68a7e8 Sig[3].Name=Problem Signature 04 Sig[3].Value=WerTest Sig[4].Name=Problem Signature 05 Sig[4].Value=1.0.0.0 Sig[5].Name=Problem Signature 06 Sig[5].Value=5b68a7e8 Sig[6].Name=Problem Signature 07 Sig[6].Value=1 Sig[7].Name=Problem Signature 08 Sig[7].Value=5 Sig[8].Name=Problem Signature 09 Sig[8].Value=System.NotImplementedException Here Problem Signature 07 and Problem Signature 08 are very important pieces of information to find t