WER (Windows Error Reporting)

When troubleshooting intermittent or stability issues and not checking WER is like leaving money on the table.

https://learn.microsoft.com/en-us/windows/win32/wer/collecting-user-mode-dumps

Problem:

Collect WER files (3-4 typical locations) from BOBJ nodes (could be dozens).

Too much work.

Trade-off – collect samples from each tier (CMS DB, Audit DB, CMS node, Production node, Web node), multiply by locations, still 5*~4=~20

Ok, WER does not that often give helpful information, so maybe check CMS DB or just one CMS node or Production node, depending on the problem.

Let’s collect WERs from one node, and we have, well… 50 folders!

Solution:

BiWhy will collect WERs from all machines (with logs, configurations, and other desired files, filtered by file type and timestamp) and give you an excellent summary with just a few clicks.

Have you found a helpful lead? Good!

Haven’t? You spent only a few minutes and can continue with calm in your heart troubleshooting with other approaches.