No luck with Word 2008: crash at launch

E

el_coda

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

Dears,
I cannot get Word 2008 italian to run.
I've just followed:
<http://word.mvps.org/mac/word2008Issues.html#LaunchCrash>
I've reinstalled from scratch.
I've tried to start it with the shift key pressed.
I've removed poofing tools from user's library and also from system libraries.
Other Office2008 tools are working.

Anyone is able to help me?
Many thanks

I attach the crash's log:
Microsoft Error Reporting log version: 2.0

Error Signature:
Exception: EXC_BAD_ACCESS
Date/Time: 2008-04-19 22:20:43 +0200
Application Name: Microsoft Word
Application Bundle ID: com.microsoft.Word
Application Signature: MSWD
Application Version: 12.0.1.080305
Crashed Module Name: libRIP.A.dylib
Crashed Module Version: unknown
Crashed Module Offset: 0x0002f6fe
Blame Module Name: libRIP.A.dylib
Blame Module Version: unknown
Blame Module Offset: 0x0002f6fe
Application LCID: 1040
Extra app info: Reg=en Loc=0x0410

Thread 0 crashed:

# 1 0x91b496fe in __mem.13393 + 0x91B0684A (libRIP.A.dylib + 0x0002f6fe)
# 2 0x91b4c71c in __mem.13393 + 0x91B09868 (libRIP.A.dylib + 0x0003271c)
# 3 0x91b4d73b in __mem.13393 + 0x91B0A887 (libRIP.A.dylib + 0x0003373b)
# 4 0x91b3a731 in __mem.13393 + 0x91AF787D (libRIP.A.dylib + 0x00020731)
# 5 0x91b34c88 in __mem.13393 + 0x91AF1DD4 (libRIP.A.dylib + 0x0001ac88)
# 6 0x91b1eb7d in __mem.13393 + 0x91ADBCC9 (libRIP.A.dylib + 0x00004b7d)
# 7 0x91b2f274 in __mem.13393 + 0x91AEC3C0 (libRIP.A.dylib + 0x00015274)
# 8 0x94e382fd in _glProgramSnippetTable + 0x9477F47D (CoreGraphics + 0x000272fd)
# 9 0x9244ae98 in .objc_class_name_IPMDFontRange + 0x92120278 (HIToolbox + 0x000c1e98)
# 10 0x00453895 in _wdCommandDispatch + 0x00137C2D (Microsoft Word + 0x00452895)
# 11 0x00456f9e in _wdCommandDispatch + 0x0013B336 (Microsoft Word + 0x00455f9e)
# 12 0x00457149 in _wdCommandDispatch + 0x0013B4E1 (Microsoft Word + 0x00456149)
# 13 0x00b66263 in _wdCommandDispatch + 0x0084A5FB (Microsoft Word + 0x00b65263)
# 14 0x00b670b2 in _wdCommandDispatch + 0x0084B44A (Microsoft Word + 0x00b660b2)
# 15 0x00438780 in _wdCommandDispatch + 0x0011CB18 (Microsoft Word + 0x00437780)
# 16 0x00b5beae in _wdCommandDispatch + 0x00840246 (Microsoft Word + 0x00b5aeae)
# 17 0x00aebc34 in _wdCommandDispatch + 0x007CFFCC (Microsoft Word + 0x00aeac34)
# 18 0x02237936 in _ImmUseInputWindowForMac + 0x00000BC8 (MicrosoftOffice + 0x004a3936)
# 19 0x0222b702 in _SendMessageA + 0x00000104 (MicrosoftOffice + 0x00497702)
# 20 0x02241ffa in _GetOpenFileNameW + 0x00001B8B (MicrosoftOffice + 0x004adffa)
# 21 0x022469fb in _WrapViewInWLMWrapper + 0x00002CC1 (MicrosoftOffice + 0x004b29fb)
# 22 0x0161a4c0 in MHIView::HandleEvent(OpaqueEventHandlerCallRef*, MEvent&) + 0x000006F4 (MicrosoftComponentPlugin + 0x000a44c0)
# 23 0x016192f9 in MHIView::GetMHIView(OpaqueControlRef*) + 0x000000ED (MicrosoftComponentPlugin + 0x000a32f9)
# 24 0x01611128 in MEventHandler::FRemoveHandler(unsigned long, unsigned long) + 0x000001DE (MicrosoftComponentPlugin + 0x0009b128)
# 25 0x92390fc3 in .objc_class_name_IPMDFontRange + 0x920663A3 (HIToolbox + 0x00007fc3)
# 26 0x923903fd in .objc_class_name_IPMDFontRange + 0x920657DD (HIToolbox + 0x000073fd)
# 27 0x92390262 in .objc_class_name_IPMDFontRange + 0x92065642 (HIToolbox + 0x00007262)
# 28 0x923b3d1d in .objc_class_name_IPMDFontRange + 0x920890FD (HIToolbox + 0x0002ad1d)
# 29 0x923b380a in .objc_class_name_IPMDFontRange + 0x92088BEA (HIToolbox + 0x0002a80a)
# 30 0x923b396e in .objc_class_name_IPMDFontRange + 0x92088D4E (HIToolbox + 0x0002a96e)
# 31 0x923b396e in .objc_class_name_IPMDFontRange + 0x92088D4E (HIToolbox + 0x0002a96e)
# 32 0x923b396e in .objc_class_name_IPMDFontRange + 0x92088D4E (HIToolbox + 0x0002a96e)
# 33 0x923b396e in .objc_class_name_IPMDFontRange + 0x92088D4E (HIToolbox + 0x0002a96e)
# 34 0x923b396e in .objc_class_name_IPMDFontRange + 0x92088D4E (HIToolbox + 0x0002a96e)
# 35 0x923b396e in .objc_class_name_IPMDFontRang
 
J

John McGhie

I hope you put the proofing tools back? That's not it.

It's probably your Custom Dictionary that has become corrupt.

Drag your custom dictionary to the desktop, reboot the computer, and see if
that clears it.

Hope this helps


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

Dears,
I cannot get Word 2008 italian to run.
I've just followed:
<http://word.mvps.org/mac/word2008Issues.html#LaunchCrash>
I've reinstalled from scratch.
I've tried to start it with the shift key pressed.
I've removed poofing tools from user's library and also from system libraries.
Other Office2008 tools are working.

Anyone is able to help me?
Many thanks

I attach the crash's log:
Microsoft Error Reporting log version: 2.0

Error Signature:
Exception: EXC_BAD_ACCESS
Date/Time: 2008-04-19 22:20:43 +0200
Application Name: Microsoft Word
Application Bundle ID: com.microsoft.Word
Application Signature: MSWD
Application Version: 12.0.1.080305
Crashed Module Name: libRIP.A.dylib
Crashed Module Version: unknown
Crashed Module Offset: 0x0002f6fe
Blame Module Name: libRIP.A.dylib
Blame Module Version: unknown
Blame Module Offset: 0x0002f6fe
Application LCID: 1040
Extra app info: Reg=en Loc=0x0410

Thread 0 crashed:

# 1 0x91b496fe in __mem.13393 + 0x91B0684A (libRIP.A.dylib + 0x0002f6fe)
# 2 0x91b4c71c in __mem.13393 + 0x91B09868 (libRIP.A.dylib + 0x0003271c)
# 3 0x91b4d73b in __mem.13393 + 0x91B0A887 (libRIP.A.dylib + 0x0003373b)
# 4 0x91b3a731 in __mem.13393 + 0x91AF787D (libRIP.A.dylib + 0x00020731)
# 5 0x91b34c88 in __mem.13393 + 0x91AF1DD4 (libRIP.A.dylib + 0x0001ac88)
# 6 0x91b1eb7d in __mem.13393 + 0x91ADBCC9 (libRIP.A.dylib + 0x00004b7d)
# 7 0x91b2f274 in __mem.13393 + 0x91AEC3C0 (libRIP.A.dylib + 0x00015274)
# 8 0x94e382fd in _glProgramSnippetTable + 0x9477F47D (CoreGraphics +
0x000272fd)
# 9 0x9244ae98 in .objc_class_name_IPMDFontRange + 0x92120278 (HIToolbox +
0x000c1e98)
# 10 0x00453895 in _wdCommandDispatch + 0x00137C2D (Microsoft Word +
0x00452895)
# 11 0x00456f9e in _wdCommandDispatch + 0x0013B336 (Microsoft Word +
0x00455f9e)
# 12 0x00457149 in _wdCommandDispatch + 0x0013B4E1 (Microsoft Word +
0x00456149)
# 13 0x00b66263 in _wdCommandDispatch + 0x0084A5FB (Microsoft Word +
0x00b65263)
# 14 0x00b670b2 in _wdCommandDispatch + 0x0084B44A (Microsoft Word +
0x00b660b2)
# 15 0x00438780 in _wdCommandDispatch + 0x0011CB18 (Microsoft Word +
0x00437780)
# 16 0x00b5beae in _wdCommandDispatch + 0x00840246 (Microsoft Word +
0x00b5aeae)
# 17 0x00aebc34 in _wdCommandDispatch + 0x007CFFCC (Microsoft Word +
0x00aeac34)
# 18 0x02237936 in _ImmUseInputWindowForMac + 0x00000BC8 (MicrosoftOffice +
0x004a3936)
# 19 0x0222b702 in _SendMessageA + 0x00000104 (MicrosoftOffice + 0x00497702)
# 20 0x02241ffa in _GetOpenFileNameW + 0x00001B8B (MicrosoftOffice +
0x004adffa)
# 21 0x022469fb in _WrapViewInWLMWrapper + 0x00002CC1 (MicrosoftOffice +
0x004b29fb)
# 22 0x0161a4c0 in MHIView::HandleEvent(OpaqueEventHandlerCallRef*, MEvent&) +
0x000006F4 (MicrosoftComponentPlugin + 0x000a44c0)
# 23 0x016192f9 in MHIView::GetMHIView(OpaqueControlRef*) + 0x000000ED
(MicrosoftComponentPlugin + 0x000a32f9)
# 24 0x01611128 in MEventHandler::FRemoveHandler(unsigned long, unsigned long)
+ 0x000001DE (MicrosoftComponentPlugin + 0x0009b128)
# 25 0x92390fc3 in .objc_class_name_IPMDFontRange + 0x920663A3 (HIToolbox +
0x00007fc3)
# 26 0x923903fd in .objc_class_name_IPMDFontRange + 0x920657DD (HIToolbox +
0x000073fd)
# 27 0x92390262 in .objc_class_name_IPMDFontRange + 0x92065642 (HIToolbox +
0x00007262)
# 28 0x923b3d1d in .objc_class_name_IPMDFontRange + 0x920890FD (HIToolbox +
0x0002ad1d)
# 29 0x923b380a in .objc_class_name_IPMDFontRange + 0x92088BEA (HIToolbox +
0x0002a80a)
# 30 0x923b396e in .objc_class_name_IPMDFontRange + 0x92088D4E (HIToolbox +
0x0002a96e)
# 31 0x923b396e in .objc_class_name_IPMDFontRange + 0x92088D4E (HIToolbox +
0x0002a96e)
# 32 0x923b396e in .objc_class_name_IPMDFontRange + 0x92088D4E (HIToolbox +
0x0002a96e)
# 33 0x923b396e in .objc_class_name_IPMDFontRange + 0x92088D4E (HIToolbox +
0x0002a96e)
# 34 0x923b396e in .objc_class_name_IPMDFontRange + 0x92088D4E (HIToolbox +
0x0002a96e)
# 35 0x923b396e in .objc_class_name_IPMDFontRang
Click to expand...

--

Don't wait for your answer, click here: http://www.word.mvps.org/

Please reply in the group. Please do NOT email me unless I ask you to.

John McGhie, Microsoft MVP, Word and Word:Mac
Nhulunbuy, NT, Australia. mailto:[email protected]
 
E

el_coda

Thanks John,
but one question... which is the location of my custom dictionary file?
 
J

John McGhie

At the risk of sounding like your mother, the only reliable answer to that
is "Where you put it".

The custom dictionary can be literally anywhere the user cares to put it.
The only reliable way to find it is to go to Word>Preferences>Spelling and
Grammar>Dictionaries...

If there was not a bug in the user interface, you would be able to read the
path there. Since there is, click "Add". A Finder window will open showing
you where it is.

Cheers


Thanks John,
but one question... which is the location of my custom dictionary file?
Click to expand...

--

Don't wait for your answer, click here: http://www.word.mvps.org/

Please reply in the group. Please do NOT email me unless I ask you to.

John McGhie, Microsoft MVP, Word and Word:Mac
Nhulunbuy, NT, Australia. mailto:[email protected]
 
J

jonfreid

At the risk of sounding like your mother, the only reliable answer to that
is "Where you put it".

The custom dictionary can be literally anywhere the user cares to put it.
The only reliable way to find it is to go to Word>Preferences>Spelling and
Grammar>Dictionaries...

If there was not a bug in the user interface, you would be able to read the
path there.  Since there is, click "Add".  A Finder window will open showing
you where it is.

Cheers



--

Don't wait for your answer, click here:http://www.word.mvps.org/

Please reply in the group.  Please do NOT email me unless I ask you to.

John McGhie, Microsoft MVP, Word and Word:Mac
Nhulunbuy, NT, Australia.  mailto:[email protected]
Click to expand...

FOUND THE ANSWER ON MY OWN. PLEASE HELP OTHERS WITH THIS FIX!!!!!

Folks who know how to use quartz debug to enable quartz 2D extreme.
This is what is crashing word on launch. Please disable this until MS
finds a fix so their software is compliant with quartz 2D extreme.
 
E

el_coda

Thanks!!!
I executed this from Terminal:

defaults write /Library/Preferences/com.apple.windowserver QuartzGLEnabled -bool
ean NO

and now Word is Working!!!
Gooood Idea!
Thanks
ivan
 
J

John McGhie

If you believe that this will help other users, it would be best if you told
them what Quartz 2D Extreme is, on which computers it exists, and how to
disable it if you have it.

There are a lot of new users in here: please make your suggestions complete
and self-explanatory.

I understand that this is not something new users should be expected to know
how to do. But just because they are new, we should not assume that they
cannot follow complex instructions :)

FOUND THE ANSWER ON MY OWN. PLEASE HELP OTHERS WITH THIS FIX!!!!!

Folks who know how to use quartz debug to enable quartz 2D extreme.
This is what is crashing word on launch. Please disable this until MS
finds a fix so their software is compliant with quartz 2D extreme.
Click to expand...

--

Don't wait for your answer, click here: http://www.word.mvps.org/

Please reply in the group. Please do NOT email me unless I ask you to.

John McGhie, Microsoft MVP, Word and Word:Mac
Nhulunbuy, NT, Australia. mailto:[email protected]
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Mac Word shuts down sometimes when saving ordoing spell check in another language 1
Word Crashes when selecting help menu 6
Word 2008 Crashes Consistently 28
Word crash - don't know the reason 8
Word 2008 crashes after update 5
Word 2008 crashes when creating tables 2
Error upon opening any word document or clicking on the help 6
Recurring Error on Word Launch 1

Top