WER is designed for third-parties...not Microsoft...
Wednesday, July 14, 2004 at 10:52 am
Posted by Ghostie
(2 messages posted)
WER (Windows Error Reporting) is actually a very valuable tool for MSDN Universal
subscribers - primarily third-party ISVs:
https://winqual.microsoft.com/info/default.aspx#WER
Basically, when any application crashes, Microsoft can be sent a crash report. Initially
the WER servers actually throw away crash reports until the software vendor goes
in and says they want to receive them. What the vendor receives is a CAB file (compressed
- kind of like ZIP, but different and is Windows-specific) containing a number of
minidump files. A minidump file contains just enough information for the vendor
to see what line of code the program was executing on at the time of the crash/freeze/etc.
They get the stack, the DLLs that were loaded in, and maybe a little extra information.
The files are digitally signed to prevent tampering. So, sending error reports
never hurts and actually helps in a lot of cases.
From what I understand the Office and most other teams ignore the error reports,
but the Visual Studio .NET (2005 - Whidbey) team pays attention to them.
[Reply or follow-up to this message]
|
re: WER is designed for third-parties...not Microsoft...
Monday, October 3, 2005 at 10:53 pm
Posted by Debra schnon
(1 messages posted)
I'm receiving an error(yellow upside triangle with an explanation mark) always telling
me it's an error. This always happens when I either log on to the computer, or even
log off. It's telling me I have unsent e-mails, but continously asking me for details.
Please get rid of this. Thank you.
On Wednesday, July 14, 2004 at 10:52 am, Ghostie wrote:
>WER (Windows Error Reporting) is actually a very valuable tool for MSDN Universal
>subscribers - primarily third-party ISVs:
>
>https://winqual.microsoft.com/info/default.aspx#WER
>
>Basically, when any application crashes, Microsoft can be sent a crash report.
Initially
>the WER servers actually throw away crash reports until the software vendor goes
>in and says they want to receive them. What the vendor receives is a CAB file (compressed
>- kind of like ZIP, but different and is Windows-specific) containing a number of
>minidump files. A minidump file contains just enough information for the vendor
>to see what line of code the program was executing on at the time of the crash/freeze/etc.
> They get the stack, the DLLs that were loaded in, and maybe a little extra information.
> The files are digitally signed to prevent tampering. So, sending error reports
>never hurts and actually helps in a lot of cases.
>
>From what I understand the Office and most other teams ignore the error reports,
>but the Visual Studio .NET (2005 - Whidbey) team pays attention to them.
[Reply or follow-up to this message]
|
