Re: "Microsoft Reporting Error" bug in Tiger?

Haven't a clue re the error reporting bug, sorry Norman. :( Obviously, not
everyone is seeing this.

Norman, John, and Mark: Can you shift-login into your user account (to turn
off all startup programs) for a little bit and see if possibly one of them
was interfering? Or see if the same happens in a new user account?

John, at present, these newsgroups *are* the indirect way to report bugs to
the MacBU. The MVPs have been told/promised that MacBU is working on a real
feedback method. :(

Pete, you actually don't seem to have the same problem. Yours is just an
ordinary problem of Word crashing, and it's generally known how to fix that.
Having the MS Error Report show up is not a new bug--but having the error
reporting app itself *crash* is a new bug in Tiger, without known cause or
fix.

Pete, if I'm wrong, can you confirm that you also were seeing the MS Error
Report app crash *on top* of a Word crash?

--
Daiya Mitchell, MVP Mac/Word
Word FAQ: http://www.word.mvps.org/
MacWord Tips: <http://www.word.mvps.org/MacWordNew/>
What's an MVP? A volunteer! Read the FAQ: http://mvp.support.microsoft.com/


On 9/2/05 7:50 PM, "Norman R. Nager, Ph.D." wrote:

> Unlike some of the others in this thread my biggest problem is in the
> Microsoft Reporting Error process.
>
> Office 2004's "Microsoft Reporting Error" sub-application or script, itself,
> appears to have bugs.
>
> On every single occasion that it's been activated during Entourage or Word
> operations, "Microsoft Reporting Error" ITSELF freezes.
>
> Force-quit, then, has failed to quit either "MRE" or the in-trouble Office
> application.
>
> Usually, after after MRE is dancing in the dock (but never functioning),
> it has jammed even Activity Monitor and normal Finder shutdown. It has
> never responded to Force Quit and only on a couple occasions responded to
> killing the MRE and other frozen Office process in Activity Monitor.
>
> On re-starting the computer, no problems can be found when running Disk
> Utility, DiskWarrior 3.0.3, or TechTool Pro 4.0.5. Rebuilding Entourage
> 11.1 does not prevent the problem from re-occurring nor does removing the
> Word normal template.
>
> Respectfully, Norm
>
>
>
> On 9/2/05 2:03 PM, in article BF3E3645.25888%dummy@xxxxxxxxxxxxxxxxx, "Pete"
> <dummy@xxxxxxxxxxxxxxxxx> wrote:
>
>> I just remembered that in addition to doing what I wrote below, I also
>> opened up font book and resolved any duplicate fonts I had. For me at
>> least, the combination of those two things seemed to have fixed things...for
>> now...
>>
>>
>> On 9/2/05 4:49 PM, in article BF3E330C.25881%dummy@xxxxxxxxxxxxxxxxx, "Pete"
>> <dummy@xxxxxxxxxxxxxxxxx> wrote:
>>
>>>
>>> Make that three! (1.25 gHz AlPB, 512). Although
>>>
>>> I may have recently tracked down a solution (or at least a fix that has
>>> worked for me thus far...). With some detective work help from posters at
>>> arstechnica.com, it looked like Word was crashing when it was trying to save
>>> the normal template just before it quit. I went to the MUD folder, removed
>>> the normal template and restarted Word, forcing it to create a new normal
>>> template. I had customized my previous normal template with some toolbars,
>>> styles, etc. and, using the style organizer, I moved the customizations from
>>> the old template into the newly created one. I haven't had a Word crash on
>>> quit since then! /fingers crossed
>>>
>>> Let the list know if this works for you too!
>>>
>>
>

.