Imp: Microsoft Error Reporting now working fine with SP2

[Priyanka Singhal [MSFT]]

Hi,

If you have disabled Microsoft Error Reporting because of issues it had on
Tiger, I am pleased to report that these issues have been fixed in the
latest upgrade. Please enable the feature by following the steps listed
below:

This is how you can enable Microsoft error reporting:


1. Go into the Office folder under the folder where Office 2004 is
installed
2. Start Microsoft Error Reporting,
3. Go to Microsoft Error Reporting->Preferences, check Enable Microsoft
Error Reporting
4. Command-Q to quit Microsoft Error Reporting



This feature is a very useful tool that helps us in gathering data about
your problems with the product and thus enables us to provide high quality
products.

Thanks,

Priyanka

 

[Priyanka Singhal [MSFT]]

As our developer Nathan says :

This cannot be stressed enough.

Our testing environment, while large, and our set of beta environments,
while also large, do not see all the setups and users interactions that
exist in the real world.

Crashes that get reported serve two purposes:
1) To give us developers extra information to try and determine what is
happening when it's a crash that we may have never heard about, do not see
in-house, and cannot easily come up with a reliably reproducable case.
2) The quantity of reports for a given problem affects the priority it gets
when we consider which bugs to try and fix first.

So if you don't report, we may either know about the bug but not consider it
as worth fixing as other problems, or not even know about the bug.

Inform us. Use Microsoft Error Reporting.

-nh

P.S., The same holds true for the Apple Crash reporter, Talkback (for
Mozilla-based products) and other similar reporting mechanisms, though in
the case of the Apple Crash reporter, Apple sometimes has to route the
reports to the appropriate third party.

 

[Priyanka Singhal [MSFT]]

As our developer Nathan points out :

This cannot be stressed enough.

Our testing environment, while large, and our set of beta environments,
while also large, do not see all the setups and users interactions that
exist in the real world.

Crashes that get reported serve two purposes:
1) To give us developers extra information to try and determine what is
happening when it's a crash that we may have never heard about, do not see
in-house, and cannot easily come up with a reliably reproducable case.
2) The quantity of reports for a given problem affects the priority it gets
when we consider which bugs to try and fix first.

So if you don't report, we may either know about the bug but not consider it
as worth fixing as other problems, or not even know about the bug.

Inform us. Use Microsoft Error Reporting.

-nh

P.S., The same holds true for the Apple Crash reporter, Talkback (for
Mozilla-based products) and other similar reporting mechanisms, though in
the case of the Apple Crash reporter, Apple sometimes has to route the
reports to the appropriate third party.

 

[Priyanka Singhal [MSFT]]

As our Developer Nathan points out :

This cannot be stressed enough.

Our testing environment, while large, and our set of beta environments,
while also large, do not see all the setups and users interactions that
exist in the real world.

Crashes that get reported serve two purposes:
1) To give us developers extra information to try and determine what is
happening when it's a crash that we may have never heard about, do not see
in-house, and cannot easily come up with a reliably reproducable case.
2) The quantity of reports for a given problem affects the priority it gets
when we consider which bugs to try and fix first.

So if you don't report, we may either know about the bug but not consider it
as worth fixing as other problems, or not even know about the bug.

Inform us. Use Microsoft Error Reporting.

-nh

P.S., The same holds true for the Apple Crash reporter, Talkback (for
Mozilla-based products) and other similar reporting mechanisms, though in
the case of the Apple Crash reporter, Apple sometimes has to route the
reports to the appropriate third party.

 

[John McGhie [MVP - Word and Word Macintosh]]

Hi All:

What she really means is "PLEASE turn it back on, we NEED the information"


There are a couple of bugs we have been chasing in these newsgroups that
have NOT been fixed in SP 2, because they simply haven't been able to
reproduce them in the Microsoft Test Lab.

You can't fix what you can't see, so they haven't been fixed. We KNOW
they're out there (or rather: in there...) because they keep getting
reported. But without the MERP data, the programmers do not have enough
information to be able to FIND them.

So please: do us ALL a favour: if you turned MERP off, please turn it back
on after you have applied SP 2 to Office 2004. That way your bug reports
will get to Priyanka's team in a form that they can actually do something
about

Cheers

Hi,

If you have disabled Microsoft Error Reporting because of issues it had on
Tiger, I am pleased to report that these issues have been fixed in the
latest upgrade. Please enable the feature by following the steps listed
below:

This is how you can enable Microsoft error reporting:


1. Go into the Office folder under the folder where Office 2004 is
installed
2. Start Microsoft Error Reporting,
3. Go to Microsoft Error Reporting->Preferences, check Enable Microsoft
Error Reporting
4. Command-Q to quit Microsoft Error Reporting



This feature is a very useful tool that helps us in gathering data about
your problems with the product and thus enables us to provide high quality
products.

Thanks,

Priyanka

--

Please reply to the newsgroup to maintain the thread. Please do not email
me unless I ask you to.

John McGhie <[email protected]>
Microsoft MVP, Word and Word for Macintosh. Consultant Technical Writer
Sydney, Australia +61 4 1209 1410