CRASHING EXCEL :(

[AlexRob]

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

Hi Guys(and girls),

I am really pulling my hair out over this. All other office programs work. But excel crashes every time I load it, sometimes immediately sometimes after about 10 seconds...

I have reinstalled to no avail.
Microsoft Error Reporting log version: 2.0

Error Signature:
Exception: EXC_BAD_ACCESS
Date/Time: 2009-10-29 21:30:02 +0000
Application Name: Microsoft Excel
Application Bundle ID: com.microsoft.Excel
Application Signature: XCEL
Application Version: 12.2.0.090605
Crashed Module Name: libobjc.A.dylib
Crashed Module Version: unknown
Crashed Module Offset: 0x00000d88
Blame Module Name: libobjc.A.dylib
Blame Module Version: unknown
Blame Module Offset: 0x00000d88
Application LCID: 1033
Extra app info: Reg=en Loc=0x0409

Thread 0 crashed:

# 1 0x914f5d88 in _objc_assign_strongCast + 0x91444D6A (libobjc.A.dylib + 0x00000d88)
# 2 0x914f5b7e in _objc_assign_strongCast + 0x91444B60 (libobjc.A.dylib + 0x00000b7e)
# 3 0x914f9c17 in _objc_assign_strongCast + 0x91448BF9 (libobjc.A.dylib + 0x00004c17)
# 4 0x915023de in _objc_assign_strongCast + 0x914513C0 (libobjc.A.dylib + 0x0000d3de)
# 5 0x91503698 in _objc_assign_strongCast + 0x9145267A (libobjc.A.dylib + 0x0000e698)
# 6 0x914fada7 in _objc_assign_strongCast + 0x91449D89 (libobjc.A.dylib + 0x00005da7)
# 7 0x914fa953 in _objc_assign_strongCast + 0x91449935 (libobjc.A.dylib + 0x00005953)
# 8 0x91f80df0 in .objc_class_name_CTGlyphStorageInterface + 0x91F19CBC (CoreText + 0x00004df0)
# 9 0x91f80cf3 in .objc_class_name_CTGlyphStorageInterface + 0x91F19BBF (CoreText + 0x00004cf3)
# 10 0x97117ddd in .objc_class_name_IMKInkInputSession + 0x96DD3485 (HIToolbox + 0x0000bddd)
# 11 0x97117d31 in .objc_class_name_IMKInkInputSession + 0x96DD33D9 (HIToolbox + 0x0000bd31)
# 12 0x97117a8e in .objc_class_name_IMKInkInputSession + 0x96DD3136 (HIToolbox + 0x0000ba8e)
# 13 0x9711674c in .objc_class_name_IMKInkInputSession + 0x96DD1DF4 (HIToolbox + 0x0000a74c)
# 14 0x971165c3 in .objc_class_name_IMKInkInputSession + 0x96DD1C6B (HIToolbox + 0x0000a5c3)
# 15 0x01621772 in _InitTestSuite + 0x00004296 (MicrosoftComponentPlugin + 0x0010b772)
# 16 0x0162164f in _InitTestSuite + 0x00004173 (MicrosoftComponentPlugin + 0x0010b64f)
# 17 0x0161f1e5 in _InitTestSuite + 0x00001D09 (MicrosoftComponentPlugin + 0x001091e5)
# 18 0x0161dd3e in _InitTestSuite + 0x00000862 (MicrosoftComponentPlugin + 0x00107d3e)
# 19 0x0161dc3c in _InitTestSuite + 0x00000760 (MicrosoftComponentPlugin + 0x00107c3c)
# 20 0x0166773c in _McpASGetObjProperty + 0x00000E5A (MicrosoftComponentPlugin + 0x0015173c)
# 21 0x01608e1e in _McpEnableTooltips + 0x00000B98 (MicrosoftComponentPlugin + 0x000f2e1e)
# 22 0x015ef4fc in MHIView::HandleEvent(OpaqueEventHandlerCallRef*, MEvent&) + 0x000006F4 (MicrosoftComponentPlugin + 0x000d94fc)
# 23 0x015f10d8 in MHIView::Retain() + 0x000000C2 (MicrosoftComponentPlugin + 0x000db0d8)
# 24 0x015f9408 in MEventHandler::RemoveGlobalListener(MEventListener*) + 0x000001A6 (MicrosoftComponentPlugin + 0x000e3408)
# 25 0x97114129 in .objc_class_name_IMKInkInputSession + 0x96DCF7D1 (HIToolbox + 0x00008129)
# 26 0x971133f0 in .objc_class_name_IMKInkInputSession + 0x96DCEA98 (HIToolbox + 0x000073f0)
# 27 0x9711324f in .objc_class_name_IMKInkInputSession + 0x96DCE8F7 (HIToolbox + 0x0000724f)
# 28 0x9713b15d in .objc_class_name_IMKInkInputSession + 0x96DF6805 (HIToolbox + 0x0002f15d)
# 29 0x9713aab1 in .objc_class_name_IMKInkInputSession + 0x96DF6159 (HIToolbox + 0x0002eab1)
# 30 0x9713ad24 in .objc_class_name_IMKInkInputSession + 0x96DF63CC (HIToolbox + 0x0002ed24)
# 31 0x9713ad24 in .objc_class_name_IMKInkInputSession + 0x96DF63CC (HIToolbox + 0x0002ed24)
# 32 0x9713ad24 in .objc_class_name_IMKInkInputSession + 0x96DF63CC (HIToolbox + 0x0002ed24)
# 33 0x97139ad7 in .objc_class_name_IMKInkInputSession + 0x96DF517F (HIToolbox + 0x0002dad7)
# 34 0x9713971d in .objc_class_name_IMKInkInputSession + 0x96DF4DC

 

[John McGhie]

I think you HAVE installed without installing the update, and that's what is
wrong

There is an Apple bug in OS 10.6.1 that we're chasing that takes Excel out.
Apple will apparently release a fix in 10.6.2 for this.

Until then, your only option might be to roll back to OS 10.5.8.

Search this group for posts by "XinXin" ‹ he is the Microsoft Software
Engineer who is looking into this.

But so far, all he has found is that it's falling over in an OS X module.

The maddening thing is that it does not do it on all systems: it's fine here
in OS 10.6.1.

Cheers

Oh it cut off the bottom... I have reinstalled to no avail, but now am
thinking I should re install without installing the update.. What do you guys
think?

Thanks

--

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]

Hi Alex, I looked into your crash in our database - this is not a popular crash. Could you please give a little more details? Did you launch Excel by clicking the icon or double click a file to launch Excel? I would suggest you hold "shift" and then launch Excel. Don't release it until Excel fully launches. Please let me know whether this crash reproduces. In addtion, trying to repair your duplicated/corrupted fonts with "font book" can be another good attempt.

Thanks,
XinXin
Macintosh Business Unit, Microsoft

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

 

[skull373]

I have the same thing happening to Excel as Alex. I'm running OSX 10.5.8.
When I open Excel while holding the shift key down, Excel does open correctly.
Any more information as to why this is happening?
What does the shift key do that makes it open while it's pressed?
Thanks,
Skull373

 

[CyberTaz]

Please understand that if you're running on a completely different version
of the operating system (Leopard 10.5.x as opposed to Snow Leopard 10.6.x)
that your problem can't be "the same thing" even though the symptoms may be
similar. Likewise, the suggestions or solutions that work for the OP here
may be totally inappropriate for your situation.

Submit a NEW message stating exact OS X & Office update levels as well as
any other details that might possibly relate to your issue. That way the
focus can be placed on that specific set of circumstances rather than being
mixed in with another conversation. Otherwise the thread becomes
inextricably tangled & confusing for everyone.

Launching while holding the Shift key is a simple troubleshooting technique
that helps identify where the problem lies but it doesn't necessarily mean
much if the other missing information isn't supplied.

Regards |:>)
Bob Jones
[MVP] Office:Mac