Re: 12.1.0 Excel "open recent files" command triggers corruption of preferences

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



Thanks for the report.

If you could copy the entire crash log from the Microsoft Error Reporting
tool and send it my way, it would be a great help. Without the full log we
usually can't fully investigate.

Also, could you describe the scenario a little further? Are you saying that
you got into a state where Excel would crash when selecting *any* file from
the Recently used file list? Or did the crash only happen with a particular
file? Also, after restarting your machine, are you able to get the crash to
occur again?

Thanks,

Pat McMillan
patmcmil@xxxxxxxxxxxxx


On 5/20/08 8:47 PM, in article
C458E964.8DD0%nnager@xxxxxxxxxxxxxxxxxxxxxxxxxx, "Norman R. Nager, Ph.D."
<nnager@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

Excel 12.1.0 was working fine, as did 12.0.1 before it with the PPC version
of OS 10.5.2.

After opening previous "recent files" (my preference was for 20) with no
difficulty, Excel crashed. I OKed the sending in of a crash report to
Microsoft.

After Excel re-launched, the same problem happened with "recent files" but
not if I just navigated to a file to open or double-clicked on a previously
saved file. But "open," also became corrupted.

Trashing Excel preferences did not initially fix the corruption. Trashing
and then re-starting the G5 worked fine, at least in opening previously
saved filed via simply navigating and "open," via "open recent," and
double-clicking.

The lengthy crash log, which was sent to MS, is way beyond my level of
technical understanding.

It starts with such information as:

Microsoft Error Reporting log version: 2.0

Error Signature:
Exception: EXC_BAD_ACCESS
Date/Time: 2008-05-20 15:47:56 -0700
Application Name: Microsoft Excel
Application Bundle ID: com.microsoft.Excel
Application Signature: XCEL
Application Version: 12.1.0.080409
Crashed Module Name: CoreFoundation
Crashed Module Version: unknown
Crashed Module Offset: 0x0006b6a8
Blame Module Name: CoreFoundation
Blame Module Version: unknown
Blame Module Offset: 0x0006b6a8 . . . .

The technical information for the four threads (0-4) that followed,
hopefully, will make sense to the person/s at Microsoft who read such user
crash reports. Would it help in this newsgroup for me to post or email
parts or all of the copy I made?

It would be good to know what caused the crashes and corruption so that I
could prevent it from happening again. Any hunches?

Respectfully, Norm



--
Pat McMillan
Macintosh Business Unit
Microsoft Corp.
This posting is provided ³AS IS² with no warranties, and confers no rights.


.



Relevant Pages

  • Re: 12.1.0 Excel "open recent files" command triggers corruption o
    ... i can't open files that were previously opened in excel and saved to excel 97 ... If you could copy the entire crash log from the Microsoft Error Reporting ... Crashed Module Name: CoreFoundation ...
    (microsoft.public.mac.office.excel)
  • Re: Word 2004 crashes when cutting text - FIXED!!!
    ... When the "Microsoft Error Reporting Program" is enabled in Office 2004, ... You get the Dialog after a crash that asks you if you want to send the ... no crash log is stored. ... > I understand that maybe such word crash log file has now other name. ...
    (microsoft.public.mac.office.word)
  • Re: Frequent Crashes for All Office 2008 Apps
    ... Just scanning your crash dump, that's either a bad font or a bad document. ... Find and remove to the desktop ALL instances of the Normal template that ... it should be in your Microsoft User Data folder. ... Crashed Module Name: ATS ...
    (microsoft.public.mac.office)
  • RE: Entourage 2008 reproducibly crashes
    ... As soon as the connection is down, it crashes. ... Below are the crash reports from the first crash and two Crash Reports of the Restarts while network is still not connected. ... Application Name: Microsoft Entourage ... Crashed Module Name: CoreFoundation ...
    (microsoft.public.mac.office.entourage)
  • Re: Word Crash
    ... Disk First Aid and repaired permissions and ... concerned about possible crash again. ... I went to the Crash Log and found: ... Thread 0 crashed with PPC Thread State 64: ...
    (microsoft.public.mac.office.word)