Excel won't open

[jive_turkey]

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

Hi,

I have a fully updated (version 12.1.9) copy of office 2008. I have run the disk permission utilities. Every time I open excel, it crashes. Every time i close word, it crashes. Holding shift does not help The error:
Microsoft Error Reporting log version: 2.0

Error Signature:
Exception: EXC_BAD_ACCESS
Date/Time: 2009-06-15 22:12:25 -0400
Application Name: Microsoft Excel
Application Bundle ID: com.microsoft.Excel
Application Signature: XCEL
Application Version: 12.0.0.071130
Crashed Module Name: MicrosoftComponentPlugin
Crashed Module Version: unknown
Crashed Module Offset: 0x000b5d4b
Blame Module Name: MicrosoftComponentPlugin
Blame Module Version: unknown
Blame Module Offset: 0x000b5d4b
Application LCID: 1033
Extra app info: Reg=en Loc=0x0409

Thread 0 crashed:

# 1 0x01513d4b in MAccessibility::MAccessibility(MHIView&, __CFString const*, __CFString const*, MAccessibility::SupportedAttributes, MAccessibility::SupportedAttributes, MAccessibility::SupportedActions) + 0x00000171 (MicrosoftComponentPlugin + 0x000b5d4b)
# 2 0x00a3f3a7 in __mh_execute_header + 0x00A3E3A7 (Microsoft Excel + 0x00a3e3a7)
# 3 0x00a4330a in __mh_execute_header + 0x00A4230A (Microsoft Excel + 0x00a4230a)
# 4 0x008821cc in __mh_execute_header + 0x008811CC (Microsoft Excel + 0x008811cc)
# 5 0x00210287 in __mh_execute_header + 0x0020F287 (Microsoft Excel + 0x0020f287)
# 6 0x0087d19c in __mh_execute_header + 0x0087C19C (Microsoft Excel + 0x0087c19c)
# 7 0x0087d86f in __mh_execute_header + 0x0087C86F (Microsoft Excel + 0x0087c86f)
# 8 0x0088123d in __mh_execute_header + 0x0088023D (Microsoft Excel + 0x0088023d)
# 9 0x00205230 in __mh_execute_header + 0x00204230 (Microsoft Excel + 0x00204230)
# 10 0x0051a6ef in __mh_execute_header + 0x005196EF (Microsoft Excel + 0x005196ef)
# 11 0x0088d626 in __mh_execute_header + 0x0088C626 (Microsoft Excel + 0x0088c626)
# 12 0x0088df3b in __mh_execute_header + 0x0088CF3B (Microsoft Excel + 0x0088cf3b)
# 13 0x0088c503 in __mh_execute_header + 0x0088B503 (Microsoft Excel + 0x0088b503)
# 14 0x00002d8e in __mh_execute_header + 0x00001D8E (Microsoft Excel + 0x00001d8e)
# 15 0x00002cb5 in __mh_execute_header + 0x00001CB5 (Microsoft Excel + 0x00001cb5)

X86 Thread State:
eax: 0x00000000 ebx: 0x01513be8 ecx: 0x04600e74 edx:0x00000000
edi: 0x04600e70 esi: 0x1a53a918 ebp: 0xbfffea28 esp:0xbfffe9e0
ss: 0x0000001f eip: 0x01513d4b cs: 0x00000017 ds:0x0000001f
es: 0x0000001f fs: 0x00000000 gs: 0x00000037 eflags:0x00010246

Thread 1:

# 1 0x94f1c3a6 in _signgam + 0x94D75482 (libSystem.B.dylib + 0x000013a6)
# 2 0x94fa3eab in _signgam + 0x94DFCF87 (libSystem.B.dylib + 0x00088eab)
# 3 0x020f3d7d in _MerpCreateSession + 0x00000B07 (merp + 0x00002d7d)
# 4 0x020f33e5 in _MerpCreateSession + 0x0000016F (merp + 0x000023e5)
# 5 0x020f346c in _MerpCreateSession + 0x000001F6 (merp + 0x0000246c)
# 6 0x020f3f25 in _MerpCreateSession + 0x00000CAF (merp + 0x00002f25)
# 7 0x94f4d155 in _signgam + 0x94DA6231 (libSystem.B.dylib + 0x00032155)
# 8 0x94f4d012 in _signgam + 0x94DA60EE (libSystem.B.dylib + 0x00032012)

X86 Thread State:
eax: 0xffffffa6 ebx: 0x94f93287 ecx: 0xb00a0a5c edx:0x94f1c3a6
edi: 0x0000c724 esi: 0x219c3cea ebp: 0xb00a0ac8 esp:0xb00a0a5c
ss: 0x0000001f eip: 0x94f1c3a6 cs: 0x00000007 ds:0x0000001f
es: 0x0000001f fs: 0x0000001f gs: 0x00000037 eflags:0x00000206

Thread 2:

# 1 0x94f2346e in _signgam + 0x94D7C54A (libSystem.B.dylib + 0x0000846e)
# 2 0x94f4ddcd in _signgam + 0x94DA6EA9 (libSystem.B.dylib + 0x00032dcd)
# 3 0x9206d45c in __CMProfileID + 0x91F9A338 (ColorSync + 0x0003345c)
# 4 0x9207fd8e in __CMProfileID + 0x91FACC6A (ColorSync + 0x00045d8e)
# 5 0x94f4d155 in _signgam + 0x94DA6231 (libSystem.B.dylib + 0x00032155)
# 6 0x94f4d012 in _signgam + 0x94DA60EE (libSystem.B.dylib + 0x00032012)

X86 Thread State:
eax: 0x0000014e ebx: 0x94f4dded ecx: 0xb0

 

[Doolittle]

L.S.

I am experiencing exactly the same problem. However in my case Word, Entourage and Powerpoint are running perfectly fine. Anyone familiar with this problem and knows how to fix this?

Thanx in advance!

 

[CyberTaz]

Well, you say "fully updated" to 12.1.9 but you're error report says
otherwise... On the 7th line it specifies "Application Version:
12.0.0.071130", so I'd suggest that you first launch Word or PPt, open the
application menu & select "About [program name]" to see what appears there.

Depending on that info you may need to re-apply some updates. There could be
something else involved as well, btu that's the place to start.

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

 

[CyberTaz]

No offense, but how can you start by saying you have "exactly the same
problem" then in the very next sentence indicate what is *different*? Just
because the symptoms are similar doesn't mean the cause is even related, let
a lone "the same"... And even if it were, "me too" replies to another post
have a tendency to muddy the water for those trying to respond & follow the
conversation. That becomes increasingly complex as those "same" issues start
to take their respective different twists & turns.

If you're certain that your problem *is* the same simply monitor the thread
& follow the suggestions & solutions offered to the original poster. There's
no need to post a reply in someone's thread unless you have a suggestion to
contribute. If those solutions don't resolve your issue -- or if there are
differences from the beginning -- please post a New message giving all
particulars pertinent to your situation. That way you'll get responses
specific to your needs & won't be misled by suggestions made for a different
situation... Especially since those actions might very well complicate the
matter you're trying to resolve.

Thanks for your understanding & cooperation

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

 

[Doolittle]

No offense, but how can you start by saying you have "exactly the same

problem" then in the very next sentence indicate what is *different*? Just
because the symptoms are similar doesn't mean the cause is even related, let
a lone "the same"... And even if it were, "me too" replies to another post
have a tendency to muddy the water for those trying to respond & follow the
conversation. That becomes increasingly complex as those "same" issues start
to take their respective different twists & turns.

If you're certain that your problem *is* the same simply monitor the thread
& follow the suggestions & solutions offered to the original poster. There's
no need to post a reply in someone's thread unless you have a suggestion to
contribute. If those solutions don't resolve your issue -- or if there are
differences from the beginning -- please post a New message giving all
particulars pertinent to your situation. That way you'll get responses
specific to your needs & won't be misled by suggestions made for a different
situation... Especially since those actions might very well complicate the
matter you're trying to resolve.

Thanks for your understanding & cooperation

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

Hey Bob,

I guess I don't have the problem then, only the same 'symptom'. Thanx in advance! My error log report:

Microsoft Error Reporting log version: 2.0

Error Signature:
Exception: EXC_BAD_ACCESS
Date/Time: 2009-06-16 14:36:29 +0200
Application Name: Microsoft Excel
Application Bundle ID: com.microsoft.Excel
Application Signature: XCEL
Application Version: 12.1.7.090302
Crashed Module Name: libobjc.A.dylib
Crashed Module Version: unknown
Crashed Module Offset: 0x0001568c
Blame Module Name: libobjc.A.dylib
Blame Module Version: unknown
Blame Module Offset: 0x0001568c
Application LCID: 1033
Extra app info: Reg=en Loc=0x0409

Thread 0 crashed:

# 1 0x9215568c in .objc_class_name_List + 0x9204D54C (libobjc.A.dylib + 0x0001568c)
# 2 0x91f64f81 in .objc_class_name_CTGlyphStorageInterface + 0x91F04E41 (CoreText + 0x00032f81)
# 3 0x91f3767f in .objc_class_name_CTGlyphStorageInterface + 0x91ED753F (CoreText + 0x0000567f)
# 4 0x9653e8ac in .objc_class_name_IPMDFontRange + 0x96213C6C (HIToolbox + 0x000278ac)
# 5 0x9653e800 in .objc_class_name_IPMDFontRange + 0x96213BC0 (HIToolbox + 0x00027800)
# 6 0x9653e546 in .objc_class_name_IPMDFontRange + 0x96213906 (HIToolbox + 0x00027546)
# 7 0x9653d3d6 in .objc_class_name_IPMDFontRange + 0x96212796 (HIToolbox + 0x000263d6)
# 8 0x9653d238 in .objc_class_name_IPMDFontRange + 0x962125F8 (HIToolbox + 0x00026238)
# 9 0x014dade2 in _McpFBuildCMLinkableTextStyleTag + 0x000064CE (MicrosoftComponentPlugin + 0x00072de2)
# 10 0x014db003 in _McpFBuildCMLinkableTextStyleTag + 0x000066EF (MicrosoftComponentPlugin + 0x00073003)
# 11 0x014dc501 in _McpFBuildCMLinkableTextStyleTag + 0x00007BED (MicrosoftComponentPlugin + 0x00074501)
# 12 0x014dde12 in _McpFBuildCMLinkableTextStyleTag + 0x000094FE (MicrosoftComponentPlugin + 0x00075e12)
# 13 0x014de900 in _McpFBuildCMLinkableTextStyleTag + 0x00009FEC (MicrosoftComponentPlugin + 0x00076900)
# 14 0x01495414 in _McpDispTBCBDataFromIMcpControl + 0x00000580 (MicrosoftComponentPlugin + 0x0002d414)
# 15 0x014f468e in _McpFCreateControl + 0x00001B3C (MicrosoftComponentPlugin + 0x0008c68e)
# 16 0x0150d450 in MHIView::HandleEvent(OpaqueEventHandlerCallRef*, MEvent&) + 0x000006F4 (MicrosoftComponentPlugin + 0x000a5450)
# 17 0x0150c26c in MHIView::GetMHIView(OpaqueControlRef*) + 0x000000F0 (MicrosoftComponentPlugin + 0x000a426c)
# 18 0x01504098 in MEventHandler::FRemoveHandler(unsigned long, unsigned long) + 0x000001DE (MicrosoftComponentPlugin + 0x0009c098)
# 19 0x9651f11d in .objc_class_name_IPMDFontRange + 0x961F44DD (HIToolbox + 0x0000811d)
# 20 0x9651e55b in .objc_class_name_IPMDFontRange + 0x961F391B (HIToolbox + 0x

 

[Doolittle]

From Thread 0; #20 onwards cont'd:

# 20 0x9651e55b in .objc_class_name_IPMDFontRange + 0x961F391B (HIToolbox + 0x0000755b)
# 21 0x9651e3c0 in .objc_class_name_IPMDFontRange + 0x961F3780 (HIToolbox + 0x000073c0)
# 22 0x96541dcd in .objc_class_name_IPMDFontRange + 0x9621718D (HIToolbox + 0x0002adcd)
# 23 0x965418a6 in .objc_class_name_IPMDFontRange + 0x96216C66 (HIToolbox + 0x0002a8a6)
# 24 0x96541a0f in .objc_class_name_IPMDFontRange + 0x96216DCF (HIToolbox + 0x0002aa0f)
# 25 0x96541a0f in .objc_class_name_IPMDFontRange + 0x96216DCF (HIToolbox + 0x0002aa0f)
# 26 0x96541a0f in .objc_class_name_IPMDFontRange + 0x96216DCF (HIToolbox + 0x0002aa0f)
# 27 0x96540cac in .objc_class_name_IPMDFontRange + 0x9621606C (HIToolbox + 0x00029cac)
# 28 0x965409bf in .objc_class_name_IPMDFontRange + 0x96215D7F (HIToolbox + 0x000299bf)
# 29 0x9654090f in .objc_class_name_IPMDFontRange + 0x96215CCF (HIToolbox + 0x0002990f)
# 30 0x96548d47 in .objc_class_name_IPMDFontRange + 0x9621E107 (HIToolbox + 0x00031d47)
# 31 0x9654875e in .objc_class_name_IPMDFontRange + 0x9621DB1E (HIToolbox + 0x0003175e)
# 32 0x92cfb942 in .objc_class_name___NSCFSet + 0x92BB0A02 (CoreFoundation + 0x00071942)
# 33 0x92cfcb72 in .objc_class_name___NSCFSet + 0x92BB1C32 (CoreFoundation + 0x00072b72)
# 34 0x92cfdc78 in .objc_class_name___NSCFSet + 0x92BB2D38 (CoreFoundation + 0x00073c78)
# 35 0x9654728c in .objc_class_name_IPMDFontRange + 0x9621C64C (HIToolbox + 0x0003028c)
# 36 0x96546fde in .objc_class_name_IPMDFontRange + 0x9621C39E (HIToolbox + 0x0002ffde)
# 37 0x9668a357 in .objc_class_name_IPMDFontRange + 0x9635F717 (HIToolbox + 0x00173357)
# 38 0x01555b38 in _McpRunApplicationEventLoop + 0x0000006A (MicrosoftComponentPlugin + 0x000edb38)
# 39 0x00a3893e in __mh_execute_header + 0x00A3793E (Microsoft Excel + 0x00a3793e)
# 40 0x00a38ec7 in __mh_execute_header + 0x00A37EC7 (Microsoft Excel + 0x00a37ec7)
# 41 0x00890d83 in __mh_execute_header + 0x0088FD83 (Microsoft Excel + 0x0088fd83)
# 42 0x00002aae in __mh_execute_header + 0x00001AAE (Microsoft Excel + 0x00001aae)
# 43 0x000029d5 in __mh_execute_header + 0x000019D5 (Microsoft Excel + 0x000019d5)

X86 Thread State:
eax: 0x1e9825b0 ebx: 0x92c9055e ecx: 0x921a7a04 edx:0xa0776e96
edi: 0x00000000 esi: 0x1e9825b0 ebp: 0xbfffdf38 esp:0xbfffdf14
ss: 0x0000001f eip: 0x9215568c cs: 0x00000017 ds:0x0000001f
es: 0x0000001f fs: 0x00000000 gs: 0x00000037 eflags:0x00010202

Thread 1:

# 1 0x940a73a6 in _signgam + 0x93F00482 (libSystem.B.dylib + 0x000013a6)
# 2 0x9412eeab in _signgam + 0x93F87F87 (libSystem.B.dylib + 0x00088eab)
# 3 0x020fdd7d in _MerpCreateSession + 0x00000B07 (merp + 0x00002d7d)
# 4 0x020fd3e5 in _MerpCreateSession + 0x0000016F (merp + 0x000023e5)
# 5 0x020fd46c in _MerpCreateSession + 0x000001F6 (merp + 0x0000246c)
# 6 0x020fdf25 in _MerpCreateSession + 0x00000CAF (merp + 0x00002f25)
# 7 0x940d8155 in _signgam + 0x93F31231 (libSystem.B.dylib + 0x00032155)
# 8 0x940d8012 in _signgam + 0x93F310EE (libSystem.B.dylib + 0x00032012)

X86 Thread State:
eax: 0xffffffa6 ebx: 0x9411e287 ecx: 0xb00a0a5c edx:0x940a73a6
edi: 0x00000043 esi: 0xc5def951 ebp: 0xb00a0ac8 esp:0xb00a0a5c
ss: 0x0000001f eip: 0x940a73a6 cs: 0x00000007 ds:0x0000001f
es: 0x0000001f fs: 0x0000001f gs: 0x00000037 eflags:0x00000202

Thread 2:

# 1 0x940ae46e in _signgam + 0x93F0754A (libSystem.B.dylib + 0x0000846e)
# 2 0x940d8dcd in _signgam + 0x93F31EA9 (libSystem.B.dylib + 0x00032dcd)
# 3 0x93ffd45c in __CMProfileID + 0x93F2A338 (ColorSync + 0x0003345c)
# 4 0x9400fd8e in __CMProfileID + 0x93F3CC6A (ColorSync + 0x00045d8e)
# 5 0x940d8155 in _signgam + 0x93F31231 (libSystem.B.dylib + 0x00032155)
# 6 0x940d8012 in _signgam + 0x93F310EE (libSystem.B.dylib + 0x00032012)

X86 Thread State:
eax: 0x0000014e ebx: 0x940d8ded ecx: 0xb0122e7c edx:0x940ae46e
edi: 0x048643a4 esi: 0xb0123000 ebp: 0xb0122ef

 

[Doolittle]

Below the "X86 Thread state" (complete), would it be necessary to also post the Loaded modules (113 total)? Thank you!

X86 Thread State:
eax: 0x0000014e ebx: 0x940d8ded ecx: 0xb0122e7c edx:0x940ae46e
edi: 0x048643a4 esi: 0xb0123000 ebp: 0xb0122ef8 esp:0xb0122e7c
ss: 0x0000001f eip: 0x940ae46e cs: 0x00000007 ds:0x0000001f
es: 0x0000001f fs: 0x0000001f gs: 0x00000037 eflags:0x00000246

 

[jive_turkey]

Bob,

When I go to "about," my version is 12.0.0 (071130)

It would not let me install 12.1.0 but i did (supposedly) successfully apply the update 12.1.9 and a combo Mac OSX update combo 10.5.7.

Another note that I should have mentioned before: Excel was updated and working last week but i think i messed up because i had an error and tried to fix it by reinstalling the office suite entirely which is when this all started.

Any guidance you can offer will be greatly appreciated.

Stephen