Excel Instant Crash

[joe.spagnola]

Version: 2008
Operating System: Mac OS X 10.6 (Snow Leopard)
Processor: Intel

Today my excel has started crashing instantly upon opening it. Please help me figure this out. I'm in grad school and really need this program.

Here is the crash report:

Microsoft Error Reporting log version: 2.0

Error Signature:
Exception: EXC_BAD_ACCESS
Date/Time: 2009-10-28 21:02:56 -0400
Application Name: Microsoft Excel
Application Bundle ID: com.microsoft.Excel
Application Signature: XCEL
Application Version: 12.2.0.090605
Crashed Module Name: CoreFoundation
Crashed Module Version: unknown
Crashed Module Offset: 0x0005c67c
Blame Module Name: CoreFoundation
Blame Module Version: unknown
Blame Module Offset: 0x0005c67c
Application LCID: 1033
Extra app info: Reg=en Loc=0x0409

Thread 0 crashed:

# 1 0x97ad667c in .objc_class_name___CFx606449CPF + 0x97946A50 (CoreFoundation + 0x0005c67c)
# 2 0x97a93f7c in .objc_class_name___CFx606449CPF + 0x97904350 (CoreFoundation + 0x00019f7c)
# 3 0x97aac763 in .objc_class_name___CFx606449CPF + 0x9791CB37 (CoreFoundation + 0x00032763)
# 4 0x908074ed in CUISharedArtReader::sFileHeader + 0x907BCD95 (CoreUI + 0x000304ed)
# 5 0x9080601b in CUISharedArtReader::sFileHeader + 0x907BB8C3 (CoreUI + 0x0002f01b)
# 6 0x907f4139 in CUISharedArtReader::sFileHeader + 0x907A99E1 (CoreUI + 0x0001d139)
# 7 0x907f7c35 in CUISharedArtReader::sFileHeader + 0x907AD4DD (CoreUI + 0x00020c35)
# 8 0x952deeaf in .objc_class_name_IMKInkInputSession + 0x94F9A557 (HIToolbox + 0x0012deaf)
# 9 0x952defb5 in .objc_class_name_IMKInkInputSession + 0x94F9A65D (HIToolbox + 0x0012dfb5)
# 10 0x951e02e0 in .objc_class_name_IMKInkInputSession + 0x94E9B988 (HIToolbox + 0x0002f2e0)
# 11 0x951dffec in .objc_class_name_IMKInkInputSession + 0x94E9B694 (HIToolbox + 0x0002efec)
# 12 0x951dfab1 in .objc_class_name_IMKInkInputSession + 0x94E9B159 (HIToolbox + 0x0002eab1)
# 13 0x951dead7 in .objc_class_name_IMKInkInputSession + 0x94E9A17F (HIToolbox + 0x0002dad7)
# 14 0x951de71d in .objc_class_name_IMKInkInputSession + 0x94E99DC5 (HIToolbox + 0x0002d71d)
# 15 0x951de66d in .objc_class_name_IMKInkInputSession + 0x94E99D15 (HIToolbox + 0x0002d66d)
# 16 0x951e7a7d in .objc_class_name_IMKInkInputSession + 0x94EA3125 (HIToolbox + 0x00036a7d)
# 17 0x951e7496 in .objc_class_name_IMKInkInputSession + 0x94EA2B3E (HIToolbox + 0x00036496)
# 18 0x97af9b02 in .objc_class_name___CFx606449CPF + 0x97969ED6 (CoreFoundation + 0x0007fb02)
# 19 0x97ab5d09 in .objc_class_name___CFx606449CPF + 0x979260DD (CoreFoundation + 0x0003bd09)
# 20 0x97ab5b61 in .objc_class_name___CFx606449CPF + 0x97925F35 (CoreFoundation + 0x0003bb61)
# 21 0x951e5f6f in .objc_class_name_IMKInkInputSession + 0x94EA1617 (HIToolbox + 0x00034f6f)
# 22 0x952db7d9 in .objc_class_name_IMKInkInputSession + 0x94F96E81 (HIToolbox + 0x0012a7d9)
# 23 0x952dbd4c in .objc_class_name_IMKInkInputSession + 0x94F973F4 (HIToolbox + 0x0012ad4c)
# 24 0x952e0077 in .objc_class_name_IMKInkInputSession + 0x94F9B71F (HIToolbox + 0x0012f077)
# 25 0x951b9129 in .objc_class_name_IMKInkInputSession + 0x94E747D1 (HIToolbox + 0x00008129)
# 26 0x951b83f0 in .objc_class_name_IMKInkInputSession + 0x94E73A98 (HIToolbox + 0x000073f0)
# 27 0x951b824f in .objc_class_name_IMKInkInputSession + 0x94E738F7 (HIToolbox + 0x0000724f)
# 28 0x9547e995 in .objc_class_name_IMKInkInputSession + 0x9513A03D (HIToolbox + 0x002cd995)
# 29 0x01a72396 in _MsoPitchTbsSwatchCaches + 0x00000214 (MicrosoftOffice + 0x0033b396)
# 30 0x01a726d6 in _MsoPitchTbsSwatchCaches + 0x00000554 (MicrosoftOffice + 0x0033b6d6)
# 31 0x00a394ea in __mh_execute_header + 0x00A384EA (Microsoft Excel + 0x00a384ea)
# 32 0x00a3a9a1 in __mh_execute_header + 0x00A399A1 (Microsoft Excel + 0x00a399a1)
# 33 0x00a322b3 in __mh_execute_header + 0x00A312B3 (Microsoft Excel + 0x00a312b3)
# 34 0x014bf612 in _McpCleanupFontFallbacks + 0x000001B6 (MicrosoftComponentPlugin + 0x00061612)
# 35 0x951b9129 in .objc_class_name_IMKInkInputSession + 0x94E747D1 (HIToolbox + 0x00

 

[joe.spagnola]

Today I installed a program called "chemdraw" and it required a program from apple called "Rosetta" I think. Could this have done it, and if so is there any way to use "Time Machine" to go back to the way my computer was yesterday?

 

[XinXin]

Hi Joe, I dug into our crash database, and it seems you are the first one seeing this crash (or the first one who reported it). Can you please try use "font book" to validate and repair your fonts? In addition, you can try repair the disk permissions. One more thing to try is to hold "shift" when launching Excel. If this crash continues, could you please send me ([email protected]) a complete crash log?

Thanks,
XinXin
Macintosh Business Unit, Microsoft

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[OlaS]

Hi,
I can report a similar behavior - I have the following configuration:
Macbook 13,3", early 2009
Mac OS X Snow Leopard 10.6.1
MacOffice 2008 enterprise, ver 12.2.1
The symptoms are that I can't boot excel, nor by starting it via the dock, neither by clicking a file. It instantly crashes. By holding down shift throughout the entire startup of excel I can start the program. After that it is no problem opening and editing and saving files as long as excel runs.
The problem may have started after viewing and editing an excel file with an OH-projector about 2 weeks ago, with screen settings as "extended desktop", but I'm not sure, I have seen other reports about multi screen theorys connected to this type of error, though.

I have made the following steps to try to solve the problem:
I did uninstall macoffice, and tried to find all folders that contain Microsoft related files, e.g. in /home/library, home/library/application support, /library, library/application support. There is obviously more files hidden in the system, since I don't need to enter my license key when re-installing…
Before reinstalling I have been refreshing the system with Onyx, and have as a consequence of that been running disc tool from Mac OS X install DVD (repair disk and restore disk rights). I have been running FontDoctor in order to repair the font database.
I do not perform a standard install since I exclude Messenger, Entourage and all spelling support except for swedish.
The problem remains as described above.
Crash report has been sent in for a couple of hundred times :-/.
I can attach one here if somebody wants..

Regards
Ola

 

[John McGhie]

Hi Ola:

No, you have a completely different crash. Please open a new thread, so we
can attend to your problem separately.

Thanks.

Hi,
I can report a similar behavior - I have the following configuration:
Macbook 13,3", early 2009
Mac OS X Snow Leopard 10.6.1
MacOffice 2008 enterprise, ver 12.2.1
The symptoms are that I can't boot excel, nor by starting it via the dock,
neither by clicking a file. It instantly crashes. By holding down shift
throughout the entire startup of excel I can start the program. After that it
is no problem opening and editing and saving files as long as excel runs.
The problem may have started after viewing and editing an excel file with an
OH-projector about 2 weeks ago, with screen settings as "extended desktop",
but I'm not sure, I have seen other reports about multi screen theorys
connected to this type of error, though.

I have made the following steps to try to solve the problem:
I did uninstall macoffice, and tried to find all folders that contain
Microsoft related files, e.g. in /home/library, home/library/application
support, /library, library/application support. There is obviously more files
hidden in the system, since I don't need to enter my license key when
re-installing…
Before reinstalling I have been refreshing the system with Onyx, and have as a
consequence of that been running disc tool from Mac OS X install DVD (repair
disk and restore disk rights). I have been running FontDoctor in order to
repair the font database.
I do not perform a standard install since I exclude Messenger, Entourage and
all spelling support except for swedish.
The problem remains as described above.
Crash report has been sent in for a couple of hundred times :-/.
I can attach one here if somebody wants..

Regards
Ola

--

This email is my business email -- Please do not email me about forum
matters unless you intend to pay!

John McGhie, Microsoft MVP (Word, Mac Word), Consultant Technical Writer,
McGhie Information Engineering Pty Ltd
Sydney, Australia. | Ph: +61 (0)4 1209 1410
+61 4 1209 1410, mailto:[email protected]

 

[joe.spagnola]

I tried validating and repairing my font libraries and doing the disc maintenance you suggested, but the problem still persists. Holding the "shift" key also doesn't seem to help.

 

[XinXin]

I worked offline with Joe to get his crashes fixed. Basically, he had 2 crashes: one was caused by the corrupted fonts, which was fixed by repairing the fonts with "font book". The other one was due to a corrupted preference file. After removing all XL preferences, his XL launches smoothly without any more crashes.

Thanks,
XinXin
Macintosh Business Unit, Microsoft

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[John McGhie]

Thanks XinXin.

Was there something we can look for in the crash-dump to show each of these
conditions?

Cheers

I worked offline with Joe to get his crashes fixed. Basically, he had 2
crashes: one was caused by the corrupted fonts, which was fixed by repairing
the fonts with "font book". The other one was due to a corrupted preference
file. After removing all XL preferences, his XL launches smoothly without any
more crashes.

Thanks,
XinXin
Macintosh Business Unit, Microsoft

This posting is provided "AS IS" with no warranties, and confers no rights.

--

This email is my business email -- Please do not email me about forum
matters unless you intend to pay!

John McGhie, Microsoft MVP (Word, Mac Word), Consultant Technical Writer,
McGhie Information Engineering Pty Ltd
Sydney, Australia. | Ph: +61 (0)4 1209 1410
+61 4 1209 1410, mailto:[email protected]

 

[XinXin]

Good question, John! Crashes caused by corrupted font or preferences can theoretically happen at different points. It's impossible to collect a complete list. The first section of the crash log gives a lot of useful information. One of the most useful data is the offset of the code when the crash happens. In Joe's case, it is 0x0005c67c. 2 of the most popular crashes:

1. Corrupted font: 0x0000b644
2. Corrupted preferences: 0x0000591b

Thanks,
XinXin
Macintosh Business Unit, Microsoft

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[John McGhie]

Clickety click... Ain't Entourage Notes grand

That will be faithfully regurgitated for anyone who posts a crash dump.

If you get any more, please add them to our list

Cheers

Good question, John! Crashes caused by corrupted font or preferences can
theoretically happen at different points. It's impossible to collect a
complete list. The first section of the crash log gives a lot of useful
information. One of the most useful data is the offset of the code when the
crash happens. In Joe's case, it is 0x0005c67c. 2 of the most popular crashes:

1. Corrupted font: 0x0000b644
2. Corrupted preferences: 0x0000591b

Thanks,
XinXin
Macintosh Business Unit, Microsoft

--

This email is my business email -- Please do not email me about forum
matters unless you intend to pay!

John McGhie, Microsoft MVP (Word, Mac Word), Consultant Technical Writer,
McGhie Information Engineering Pty Ltd
Sydney, Australia. | Ph: +61 (0)4 1209 1410
+61 4 1209 1410, mailto:[email protected]