MS Word 2008 always "quits unexpectedly"

[Stokvis1]

Version: 2008 Operating System: Mac OS X 10.6 (Snow Leopard) Processor: Intel For some reasons Word 2008 (and NOT all other components of Office Mac 2008) consistently crashes when attempting to open. I trashed version on computer including preferences and then reinstalled and upgraded, but same problem continues. Here is the error code:
Process: Microsoft Word [63444]
Path: /Applications/Microsoft Office 2008/Microsoft Word.app/Contents/MacOS/Microsoft Word
Identifier: com.microsoft.Word
Version: 12.2.4 (12.2.4)
Build Info: Unknown-100205~0
Code Type: X86 (Native)
Parent Process: launchd [121]

Date/Time: 2010-05-07 12:03:55.165 -0400
OS Version: Mac OS X 10.6.3 (10D578)
Report Version: 6

Interval Since Last Report: 1164 sec
Crashes Since Last Report: 3
Per-App Interval Since Last Report: 26 sec
Per-App Crashes Since Last Report: 3
Anonymous UUID: 7489F603-E898-4874-AE8D-8444CF299934

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 com.microsoft.Word 0x0081a0a2 wdGetApplicationObject + 898264
1 com.microsoft.Word 0x0068249c wdCommandDispatch + 3529568
2 com.microsoft.Word 0x00af2a7e wdGetApplicationObject + 3882676
3 com.microsoft.Word 0x00afb3df wdGetApplicationObject + 3917845
4 com.microsoft.office_library 0x022d0554 _WlmMain + 71
5 com.microsoft.Word 0x00ae0a54 wdGetApplicationObject + 3808906
6 com.microsoft.Word 0x00003022 0x1000 + 8226
7 com.microsoft.Word 0x00002f49 0x1000 + 8009

Thread 1: Dispatch queue: com.apple.libdispatch-manager
0 libSystem.B.dylib 0x92c9bb42 kevent + 10
1 libSystem.B.dylib 0x92c9c25c _dispatch_mgr_invoke + 215
2 libSystem.B.dylib 0x92c9b719 _dispatch_queue_invoke + 163
3 libSystem.B.dylib 0x92c9b4be _dispatch_worker_thread2 + 240
4 libSystem.B.dylib 0x92c9af41 _pthread_wqthread + 390
5 libSystem.B.dylib 0x92c9ad86 start_wqthread + 30

Thread 2:
0 libSystem.B.dylib 0x92c9abd2 __workq_kernreturn + 10
1 libSystem.B.dylib 0x92c9b168 _pthread_wqthread + 941
2 libSystem.B.dylib 0x92c9ad86 start_wqthread + 30

Thread 3:
0 libSystem.B.dylib 0x92c752fa mach_msg_trap + 10
1 libSystem.B.dylib 0x92c75a67 mach_msg + 68
2 com.microsoft.merp 0x01b29f0e MerpCreateSession + 3224
3 libSystem.B.dylib 0x92ca2a19 _pthread_start + 345
4 libSystem.B.dylib 0x92ca289e thread_start + 34

Thread 0 crashed with X86 Thread State (32-bit):
  eax: 0x00000000 ebx: 0x0152e100 ecx: 0x00000016 edx: 0xbfffee7c
  edi: 0x00000001 esi: 0x01520820 ebp: 0xbffff178 esp: 0xbffff130
   ss: 0x0000001f efl: 0x00010286 eip: 0x0081a0a2 cs: 0x00000017
   ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
  cr2: 0x00000000

Binary Images:
    0x1000 - 0x1379fff +com.microsoft.Word 12.2.4 (12.2.4) /Applications/Microsoft Office 2008/Microsoft Word.app/Contents/MacOS/Microsoft Word
 0x15e9000 - 0x1815fee +com.microsoft.mcp 12.2.4 (12.2.4) /Applications/Microsoft Office 2008/Office/MicrosoftComponentPlugin.framework/Versions/12/MicrosoftComponentPlugin
 0x18c2000 - 0x1942fff +com.microsoft.netlib 12.2.3 (12.2.3) /Applications/Microsoft Office 2008/Office/Netlib.framework/Versions/12/Netlib
 0x1962000 - 0x1997fe6 +com.microsoft.urlmon 12.2.3 (12.2.3) /Applications/Microsoft Office 2008/Office/StdUrlMoniker.framework/Versions/12/StdUrlMoniker
 0x19a4000 - 0x1a43fff +com.microsoft.ole 12.2.3 (12.2.3)

 

[CyberTaz]

I'm afraid this is one of the worst things you could have done;

I trashed version on computer including preferences and then reinstalled
and upgraded, but same problem continues.

It does absolutely nothing to address the causes of problems & most often
complicates the matter as well as causing other issues. *If* it is ever
necessary to re-install there is a special Remove Office utility provided
for the purpose. I understand that "trashing" simple, stand-alone apps is a
customary fix, but Word is a very complex app with many supporting files &
is a part of an integrated suite... It can't be treated like a freeware
utility app & it is rarely the content installed from the DVD that need
fixing.

When you say "open", are you referring to launching Word or are you
referring to 'opening' a file after Word has been successfully launched?
That can make a difference in how to proceed.

In the former case, though, it is the responsibility of the OS to launch the
app & the log you posted is one generated by OS X. The first suggestion is
to run Apple's Disk Utility - Repair Disk Permissions on your HD, then
restart your Mac to see if the problem continues. If it does;

1- Log in using a different User Account to see if that makes a difference.

2- As another diagnostic step, hold the Shift key while to log in using your
regular account.

Reply with the requested info & results of both 1 & 2 above.

--
HTH |:>)
Bob Jones
[MVP] Office:Mac

Version: 2008 Operating System: Mac OS X 10.6 (Snow Leopard) Processor:
Intel For some reasons Word 2008 (and NOT all other components of Office
Mac 2008) consistently crashes when attempting to open. I trashed version
on computer including preferences and then reinstalled and upgraded, but
same problem continues. Here is the error code:
Process: Microsoft Word [63444]
Path: /Applications/Microsoft Office 2008/Microsoft
Word.app/Contents/MacOS/Microsoft Word
Identifier: com.microsoft.Word
Version: 12.2.4 (12.2.4)
Build Info: Unknown-100205~0
Code Type: X86 (Native)
Parent Process: launchd [121]

Date/Time: 2010-05-07 12:03:55.165 -0400
OS Version: Mac OS X 10.6.3 (10D578)
Report Version: 6

Interval Since Last Report: 1164 sec
Crashes Since Last Report: 3
Per-App Interval Since Last Report: 26 sec
Per-App Crashes Since Last Report: 3
Anonymous UUID: 7489F603-E898-4874-AE8D-8444CF299934

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 com.microsoft.Word 0x0081a0a2 wdGetApplicationObject + 898264
1 com.microsoft.Word 0x0068249c wdCommandDispatch + 3529568
2 com.microsoft.Word 0x00af2a7e wdGetApplicationObject + 3882676
3 com.microsoft.Word 0x00afb3df wdGetApplicationObject + 3917845
4 com.microsoft.office_library 0x022d0554 _WlmMain + 71
5 com.microsoft.Word 0x00ae0a54 wdGetApplicationObject + 3808906
6 com.microsoft.Word 0x00003022 0x1000 + 8226
7 com.microsoft.Word 0x00002f49 0x1000 + 8009

Thread 1: Dispatch queue: com.apple.libdispatch-manager
0 libSystem.B.dylib 0x92c9bb42 kevent + 10
1 libSystem.B.dylib 0x92c9c25c _dispatch_mgr_invoke + 215
2 libSystem.B.dylib 0x92c9b719 _dispatch_queue_invoke + 163
3 libSystem.B.dylib 0x92c9b4be _dispatch_worker_thread2 + 240
4 libSystem.B.dylib 0x92c9af41 _pthread_wqthread + 390
5 libSystem.B.dylib 0x92c9ad86 start_wqthread + 30

Thread 2:
0 libSystem.B.dylib 0x92c9abd2 __workq_kernreturn + 10
1 libSystem.B.dylib 0x92c9b168 _pthread_wqthread + 941
2 libSystem.B.dylib 0x92c9ad86 start_wqthread + 30

Thread 3:
0 libSystem.B.dylib 0x92c752fa mach_msg_trap + 10
1 libSystem.B.dylib 0x92c75a67 mach_msg + 68
2 com.microsoft.merp 0x01b29f0e MerpCreateSession + 3224
3 libSystem.B.dylib 0x92ca2a19 _pthread_start + 345
4 libSystem.B.dylib 0x92ca289e thread_start + 34

Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x0152e100 ecx: 0x00000016 edx: 0xbfffee7c
edi: 0x00000001 esi: 0x01520820 ebp: 0xbffff178 esp: 0xbffff130
ss: 0x0000001f efl: 0x00010286 eip: 0x0081a0a2 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
cr2: 0x00000000

Binary Images:
0x1000 - 0x1379fff +com.microsoft.Word 12.2.4 (12.2.4)
<8890846B-FF01-4001-9D7A-EA80C6721FFE> /Applications/Microsoft Office
2008/Microsoft Word.app/Contents/MacOS/Microsoft Word
0x15e9000 - 0x1815fee +com.microsoft.mcp 12.2.4 (12.2.4)
<4EBF2131-BBCB-45C6-A3FE-7E75E0E8B6CD> /Applications/Microsoft Office
2008/Office/MicrosoftComponentPlugin.framework/Versions/12/MicrosoftComponentPlugin
0x18c2000 - 0x1942fff +com.microsoft.netlib 12.2.3 (12.2.3)
/Applications/Microsoft Office
2008/Office/Netlib.framework/Versions/12/Netlib
0x1962000 - 0x1997fe6 +com.microsoft.urlmon 12.2.3 (12.2.3)
/Applications/Microsoft Office
2008/Office/StdUrlMoniker.framework/Versions/12/StdUrlMoniker
0x19a4000 - 0x1a43fff +com.microsoft.ole 12.2.3 (12.2.3) <34

 

[Stokvis1]

Did as you said; ran disk utility but problem reoccured.
could not find MS way to remove MS OFfice. how do you get the program. it was not on the MS office for mac 2007 cd and there was no uninstall either. that is why I was frustrated.

Can I remove and then reinstall?

 

[Stokvis1]

here is latest error message:
Process: Microsoft Word [760]
Path: /Applications/Microsoft Office 2008/Microsoft Word.app/Contents/MacOS/Microsoft Word
Identifier: com.microsoft.Word
Version: 12.2.4 (12.2.4)
Build Info: Unknown-100205~0
Code Type: X86 (Native)
Parent Process: launchd [119]

Date/Time: 2010-05-07 17:07:31.280 -0400
OS Version: Mac OS X 10.6.3 (10D578)
Report Version: 6

Interval Since Last Report: 19301 sec
Crashes Since Last Report: 8
Per-App Interval Since Last Report: 185 sec
Per-App Crashes Since Last Report: 7
Anonymous UUID: 7489F603-E898-4874-AE8D-8444CF299934

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 com.microsoft.Word 0x0081a0a2 wdGetApplicationObject + 898264
1 com.microsoft.Word 0x0068249c wdCommandDispatch + 3529568
2 com.microsoft.Word 0x00af2a7e wdGetApplicationObject + 3882676
3 com.microsoft.Word 0x00afb3df wdGetApplicationObject + 3917845
4 com.microsoft.office_library 0x022d0554 _WlmMain + 71
5 com.microsoft.Word 0x00ae0a54 wdGetApplicationObject + 3808906
6 com.microsoft.Word 0x00003022 0x1000 + 8226
7 com.microsoft.Word 0x00002f49 0x1000 + 8009

Thread 1: Dispatch queue: com.apple.libdispatch-manager
0 libSystem.B.dylib 0x92c9bb42 kevent + 10
1 libSystem.B.dylib 0x92c9c25c _dispatch_mgr_invoke + 215
2 libSystem.B.dylib 0x92c9b719 _dispatch_queue_invoke + 163
3 libSystem.B.dylib 0x92c9b4be _dispatch_worker_thread2 + 240
4 libSystem.B.dylib 0x92c9af41 _pthread_wqthread + 390
5 libSystem.B.dylib 0x92c9ad86 start_wqthread + 30

Thread 2:
0 libSystem.B.dylib 0x92c9abd2 __workq_kernreturn + 10
1 libSystem.B.dylib 0x92c9b168 _pthread_wqthread + 941
2 libSystem.B.dylib 0x92c9ad86 start_wqthread + 30

Thread 3:
0 libSystem.B.dylib 0x92c9abd2 __workq_kernreturn + 10
1 libSystem.B.dylib 0x92c9b168 _pthread_wqthread + 941
2 libSystem.B.dylib 0x92c9ad86 start_wqthread + 30

Thread 4:
0 libSystem.B.dylib 0x92c752fa mach_msg_trap + 10
1 libSystem.B.dylib 0x92c75a67 mach_msg + 68
2 com.microsoft.merp 0x01b29f0e MerpCreateSession + 3224
3 libSystem.B.dylib 0x92ca2a19 _pthread_start + 345
4 libSystem.B.dylib 0x92ca289e thread_start + 34

Thread 0 crashed with X86 Thread State (32-bit):
&nbsp;&nbsp;eax: 0x00000000 ebx: 0x0152e100 ecx: 0x00000016 edx: 0xbfffee7c
&nbsp;&nbsp;edi: 0x00000001 esi: 0x01520820 ebp: 0xbffff178 esp: 0xbffff130
&nbsp;&nbsp;&nbsp;ss: 0x0000001f efl: 0x00010286 eip: 0x0081a0a2 cs: 0x00000017
&nbsp;&nbsp;&nbsp;ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
&nbsp;&nbsp;cr2: 0x00000000

Binary Images:
&nbsp;&nbsp;&nbsp;&nbsp;0x1000 - 0x1379fff +com.microsoft.Word 12.2.4 (12.2.4) /Applications/Microsoft Office 2008/Microsoft Word.app/Contents/MacOS/Microsoft Word
&nbsp;0x15e9000 - 0x1815fee +com.microsoft.mcp 12.2.4 (12.2.4) /Applications/Microsoft Office 2008/Office/MicrosoftComponentPlugin.framework/Versions/12/MicrosoftComponentPlugin
&nbsp;0x18c2000 - 0x1942fff +com.microsoft.netlib 12.2.3 (12.2.3) /Applications/Microsoft Office 2008/Office/Netlib.framework/Versions/12/Netlib
&nbsp;0x1962000 - 0x1997fe6 +com.microsoft.urlmon 12.2.3 (12.2.3) /Applications/Microsoft Office 2008/Office/StdUrlMoniker.framework/Versions/12/StdUrlMoniker
&nbsp;0x19a4000 - 0x1a43fff +com.microsoft.ole 12.2.3 (12.2.3)

 

[Stokvis1]

MS Office for Mac worked perfectly two days ago and I have everything backed up using Time Machine. How can I use time machine to restore MS office as it worked before?

 

[CyberTaz]

Please put the thought of reinstalling out of your mind -- at least for the
time being. That is a Windows fix which is one of the distinctions of the
Mac Operating System. The 2 work quite differently in that regard.

Besides, it hasn't even been determined that Word or Office is actually the
cause of the problem - it may be the victim. I don't claim to be able to
interpret these crash logs very well, but there are a few things about yours
that suggest that it may be an OS X related issue, such as:

Thread 0 Crashed: Dispatch queue: com.apple.main-thread

Try these 3 individual troubleshooting steps separately & reply with the
results of each:

1- Run Word from a different [preferably new] User Account,

2- In your regular User Account hold Shift while you launch Word ,

3- Log out then hold shift while you log in using your regular User Account.

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

 

[Randy Singer (MacAttorney)]

Version: 2008 Operating System: Mac OS X 10.6 (Snow Leopard) Processor: Intel For some reasons Word 2008 (and NOT all other components of Office Mac2008) consistently crashes when attempting to open. I trashed version on computer including preferences and then reinstalled and upgraded, but same problem continues.

Application crashes are not common for any version of OS X.  
When a program repeatedly unexpectedly quits under OS X, or its icon
bounces in the Dock but the application does not open, there are three
or four common reasons for this that you can investigate:

1) Corrupted user preference file for that application. 
Try this. Create a new user, log in as that 
new user, and see if
things are better. If they aren't, your problem 
isn't a corrupted
user preferences file. If they are, then you 
probably have a
corrupted user preferences file. 

The first thing to try is:
Preferential Treatment (free)
http://www.jonn8.com/html/pt.html
Note: While Preferential Treatment is quick and easy to use, it
unfortunately doesn't always find user preferences files that are
corrupted. If you are experiencing an application that is suddenly
quitting on you, and Preferential Treatment doesn't find anything,
you should look in your user preferences folder 
(~/Library/
Preferences/), located at:
[hard drive]/Users/[your user name]/Library/Preferences
for any preferences files with the name of the application, (or
sometimes the 
name of the developer of the application) in the name
of the file. 
For example, if you are having a problem with Safari, you will 
find
this file in your user preferences 
folder: 
com.apple.Safari.plist
Drag that file to the desktop and restart. A new preferences file
will be created in your user preferences folder when you launch
Safari the next time. See if things are better. If they are, you 
can
trash the Safari preferences file that you now have on your 
desktop. 

Note that Word keeps some preferences files in the Microsoft Office
folder. You can identify them by the extension ".plist".

2) You need to repair permissions on your disk. 
See:
http://www.macattorney.com/ts.html 
Item #1 
For many applications, repairing permissions doesn't help. But
Microsoft Word is the exception. It is unusually touchy about
incorrectly set permissions.

3) If your problem is with a browser, or another program that
maintains a cache, you should try resetting its cache. 
Download and
run:
CacheOutX (free)
http://www.trilateralsystems.com/cacheoutx/
to clear your caches. 

4) If your problem is with a word processor (i.e. Word), or some
program that
uses typography, you should suspect a corrupted font.
Often this
font is left over from Classic/OS 9. 
Often it is a
dingbats font. 
Use Font Book (installed with OS X) to verify and
repair your fonts.  Also use Font Book to check for duplicate fonts.
See: 
http://www.macattorney.com/tutorial.html 
Item #26 
http://support.apple.com/kb/HT2509

Microsoft Office is fairly well known for installing fonts that can
cause font conflicts.

Microsoft fonts to delete after installing Snow Leopard (includes help
deleting font caches)
http://www.entourage.mvps.org/troubleshoot/remove_fonts_snowleopard.html


More info:
http://word.mvps.org/mac/Diagnose.html
http://word.mvps.org/Mac/TroubleshootingIndex.html
http://www.entourage.mvps.org/troubleshoot/crashes.html#crash30

___________________________________________

Randy B. Singer
Co-author of The Macintosh Bible (4th, 5th, and 6th editions)

Macintosh OS X Routine Maintenance
http://www.macattorney.com/ts.html
___________________________________________

 

[John McGhie]

Like Bob, I struggle to read these crash dumps. Looking at that one, my
guess is that you have one or more software modules in there that did not
get the 12.2.4 update correctly applied.

We typically see crash dumps like this after users have attempted to reduce
the size of Microsoft Office by running hack-ware such as Monolingual and a
few others that promise to "remove unnecessary files" to "improve
performance". That all make your system much faster to crash

Please try Bob's three steps first. If none of them prevents the crash,
then:

Look for the "Remove Office.app". It's on your Office CD, and in
/Applications/Microsoft Office 2008/Additional Tools/Remove Office

Run that first to ensure you have cleanly removed all the several thousand
files involved.

Then re-install Office 2008 without any customisation. You MUST install it
on the Boot Volume (Mac HD).

Then re-apply ALL the updates before running it.

That should work.

here is latest error message:
Process: Microsoft Word [760]
Path: /Applications/Microsoft Office 2008/Microsoft
Word.app/Contents/MacOS/Microsoft Word
Identifier: com.microsoft.Word
Version: 12.2.4 (12.2.4)
Build Info: Unknown-100205~0
Code Type: X86 (Native)
Parent Process: launchd [119]

--

The email below is my business email -- Please do not email me about forum
matters unless I ask you to; or 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 | mailto:[email protected]

 

[Stokvis1]

I followed Bob and John's directions exactly and this time Word worked properly. Don't understand what happened but it now works!
Thanks a million!

 

[Stokvis1]

Unfortunately, my previous message was premature: Word opened without a problem but after I restarted the computer, the same problems reoccurred. Therefore, I found the &quot;Remove Office&quot; program, ran it, but it said that there were NO versions of Office on my Mac. I double checked and sure enough, it was in its folder under applications.

No I am really stumped and hope that someone can help! Thanks

 

[Stokvis1]

I attempted to repeat the above and the program showed up suddendlyu. I then removed Word and reinstalled it BUT the same problem reoccurs as originally. The error code is below:
Process: Microsoft Word [180]
Path: /Applications/Microsoft Office 2008/Microsoft Word.app/Contents/MacOS/Microsoft Word
Identifier: com.microsoft.Word
Version: 12.2.4 (12.2.4)
Build Info: Unknown-100205~0
Code Type: X86 (Native)
Parent Process: launchd [122]

Date/Time: 2010-05-10 17:32:56.291 -0400
OS Version: Mac OS X 10.6.3 (10D578)
Report Version: 6

Interval Since Last Report: 197017 sec
Crashes Since Last Report: 23
Per-App Interval Since Last Report: 69071 sec
Per-App Crashes Since Last Report: 13
Anonymous UUID: 7489F603-E898-4874-AE8D-8444CF299934

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 com.microsoft.Word 0x0081a0a2 wdGetApplicationObject + 898264
1 com.microsoft.Word 0x0068249c wdCommandDispatch + 3529568
2 com.microsoft.Word 0x00af2a7e wdGetApplicationObject + 3882676
3 com.microsoft.Word 0x00afb3df wdGetApplicationObject + 3917845
4 com.microsoft.office_library 0x022d0554 _WlmMain + 71
5 com.microsoft.Word 0x00ae0a54 wdGetApplicationObject + 3808906
6 com.microsoft.Word 0x00003022 0x1000 + 8226
7 com.microsoft.Word 0x00002f49 0x1000 + 8009

Thread 1: Dispatch queue: com.apple.libdispatch-manager
0 libSystem.B.dylib 0x92c9bb42 kevent + 10
1 libSystem.B.dylib 0x92c9c25c _dispatch_mgr_invoke + 215
2 libSystem.B.dylib 0x92c9b719 _dispatch_queue_invoke + 163
3 libSystem.B.dylib 0x92c9b4be _dispatch_worker_thread2 + 240
4 libSystem.B.dylib 0x92c9af41 _pthread_wqthread + 390
5 libSystem.B.dylib 0x92c9ad86 start_wqthread + 30

Thread 2:
0 libSystem.B.dylib 0x92c752fa mach_msg_trap + 10
1 libSystem.B.dylib 0x92c75a67 mach_msg + 68
2 com.microsoft.merp 0x01b29f0e MerpCreateSession + 3224
3 libSystem.B.dylib 0x92ca2a19 _pthread_start + 345
4 libSystem.B.dylib 0x92ca289e thread_start + 34

Thread 3:
0 libSystem.B.dylib 0x92c9abd2 __workq_kernreturn + 10
1 libSystem.B.dylib 0x92c9b168 _pthread_wqthread + 941
2 libSystem.B.dylib 0x92c9ad86 start_wqthread + 30

Thread 0 crashed with X86 Thread State (32-bit):
&nbsp;&nbsp;eax: 0x00000000 ebx: 0x0152e100 ecx: 0x00000016 edx: 0xbfffee9c
&nbsp;&nbsp;edi: 0xbffff7a8 esi: 0x01520820 ebp: 0xbffff198 esp: 0xbffff150
&nbsp;&nbsp;&nbsp;ss: 0x0000001f efl: 0x00010282 eip: 0x0081a0a2 cs: 0x00000017
&nbsp;&nbsp;&nbsp;ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
&nbsp;&nbsp;cr2: 0x00000000

Binary Images:
&nbsp;&nbsp;&nbsp;&nbsp;0x1000 - 0x1379fff +com.microsoft.Word 12.2.4 (12.2.4) /Applications/Microsoft Office 2008/Microsoft Word.app/Contents/MacOS/Microsoft Word
&nbsp;0x15e9000 - 0x1815fee +com.microsoft.mcp 12.2.4 (12.2.4) /Applications/Microsoft Office 2008/Office/MicrosoftComponentPlugin.framework/Versions/12/MicrosoftComponentPlugin
&nbsp;0x18c2000 - 0x1942fff +com.microsoft.netlib 12.2.3 (12.2.3) /Applications/Microsoft Office 2008/Office/Netlib.framework/Versions/12/Netlib
&nbsp;0x1962000 - 0x1997fe6 +com.microsoft.urlmon 12.2.3 (12.2.3) /Applications/Microsoft Office 2008/Office/StdUrlMoniker.framework/Versions/12/StdUrlMoniker
&nbsp;0x19a4000 - 0x1a43fff +com.microsoft.ole 12.2.3 (12.2.3) /Applications/Microsoft Office 2008/Office

 

[Stokvis1]

after reinstalling Word, noticed that it did NOT ask me to put in the product key so therefore the entire program was not removed. now at a total loss of what to do or why it happend.

 

[John_McGhie_[MVP]]

Yes, that's correct, the Office PID is stored in two files, one of which is
not removed by the Uninstall program.

Looking at your crash dump, all I can see is that it still appears that you
have a file in there that is at the wrong version. But I really can't be
sure, I am not from Microsoft, and I did not write this application

OK, here's the full agony. This is the most detailed procedure I have (and
if it doesn't work, I am afraid we're down to an "archive and re-install" of
the whole system, basically doing an erase of the boot partition).

When you work through the trouble-shooting list, you need to do it in
sequence: the sequence is critically important: if you do not do the whole
process in the correct sequence, it won't work at all because damaged
resources keep getting sucked back in to play.

Make sure you have your Office CD and your Product Key handy: if you Remove
Office without them, there¹s no way to get it going again.

Don¹t try to ³migrate² any part of Office, including the Preferences, from
anywhere. Many of the computers we see in a bad situation are that way as a
result of using the Migration Assistant. Bringing documents across is fine.
If you bring anything else across, chances are you will never get the bugs
out until you nuke the OS from Orbit and reinstall everything.

Be careful of utilities that offer to ³Help² or ³Improve² Microsoft Office.
Things such as Monolingual operate by ripping out software modules. After
that, it¹s not going to work properly, and there is no warranty cover for
³interfering with the software code².

The sequence is this:

1. Ascertain adequate machine resources

2. Get rid of Haxies and Helpers

3. Disconnect all but the boot drive.

4. Remove Office

5. Remove all previous resources and prefs from previous installations

6. Check and update the printer driver

7. Update the Operating System

8. Power-off restart

9. Fix disk permissions

10. Install Office 2008

11. Install two service packs and all the updates to 12.2.4

12. Resolve all Font Duplicates by removing the old versions from the
System.

13. Clear out all caches

14. Launch Word

15. Clean out old documents

16. DON¹T attempt to run any software that offers to ³reduce the size² of
Microsoft Office.


If you do all of that, in that sequence, Office 2008 will run fast and
stable (well: I have not yet run into a copy that doesn¹t...)

Now, let me explain each step:

1. Ascertain adequate machine resources

a. OS 10.6.2 requires 2 GB of RAM to run properly with Office 2008 plus
everything else you use.

b. If the processor is a PowerPC, you need twice as much, because PPC code
unpacks to twice the size in memory.

c. If you are prepared to discipline yourself to Quit each application
whenever you are not actively using it, you will ³get away² with half the
memory, but the system will always be slow, and will lock up on complex
documents.

2. Get rid of Haxies and Helpers

a. Things such as SpellCatcher and TypeItForMe insert themselves between
your keyboard and Word.

b. Some of them will make Word glue-slow.

c. Take them all out (uninstallŠ Many of them load background processes
that you may not be aware ofŠ)

d. Once you have resolved the problems, you can re-introduce the Haxies,
one-by-one.

3. Disconnect all but the boot drive.

a. The Installer is a simple-minded beastie. Unless you give it a choice
of precisely ONE drive, it can do strange things.

b. You can put the other drives back at the end of the process: but like
kids in candy stores, if other drives are visible during this process, bad
things can happen.

4. Run the Remove Office utility

a. It will be in /Applications/Microsoft Office 2008/Additional
Tools/Remove Office.



5. Remove all previous resources and prefs from previous installations

a. Find and delete the file Normal.dotm.

Unless you have moved it, it should be in:

/Users/~/Library/Application Support/Microsoft/Office/User Templates/

b. If the following files exist, remove or rename them:

~/Library/Preferences/Microsoft/Word Settings (10)

~/Library/Preferences/Microsoft/Word Settings (11)

~/Library/Preferences/com.Microsoft.Word.plist

~/Library/Preferences/Microsoft/Office 2008 (the whole folder!)

4. Check and update the printer driver
Some applications, particularly Excel, will run like treacle in
winter if all of the following is true:
· The Printer is Hewlett Packard

· The driver has not been updated

· The paper size is not US Letter

· The View is Page Layout View



5. Update the Operating System
Microsoft Office relies on updates to OS X being in place. If
your operating system is not at or above OS 10.6.2, some things won¹t work
well. There is no way to predict ³which² things.

6. Power-off restart
We want Unix to run its system clean-up tasks.
a. Shut down the computer and wait until the power turns off.

b. Then restart.

This triggers various Unix clean-up tasks.


6. Fix disk permissions

We need to ensure that the installer has permission to write to
the folders where we want it to place things.
a. Start Disk Utility

b. Choose ³Repair Permissions²

7. Install Office 2008

a. Stick the DVD in the hole and let it do its thing.

b. Do not attempt to install anywhere but the Applications folder of the
boot drive. If you really need to move stuff later (why?) then you can use
aliases.

c. If you neglected to disconnect the external drives, this is where the
fun times begin. It¹s better to start again than try to correct it!

d. If you migrate anything, it won¹t work and you will get to start again.

e. Once you have installed it, do not attempt to ³improve² it with other
applications such as Monolingual

8. Install two service packs and all the updates to 12.2.4:

Download and apply the following Microsoft updates in the following order:

a. Microsoft Office 2008 for Mac Service Pack 1 (12.1.0)
<http://www.microsoft.com/mac/downloads.mspx?pid=Mactopia_Office2008&fid=395
D1487-A3A6-4106-A0F8-4D6E1D6D89D2#viewer>

b. Microsoft Office 2008 for Mac Service Pack 2 (12.2.0)
<http://www.microsoft.com/mac/downloads.mspx?pid=Mactopia_Office2008&fid=300
133BB-B5F7-4946-BB7B-B0C6C6D6E28C#viewer>

c. Microsoft Office 2008 for Mac 12.2.3 Update
<http://www.microsoft.com/mac/downloads.mspx?pid=Mactopia_Office2008&fid=B84
FE57D-DDDA-451E-9EAD-69E10AEE7928#viewer>

d. Microsoft Office 2008 for Mac 12.2.4 Update
<http://www.microsoft.com/mac/downloads.mspx?pid=Mactopia_Office2008&fid=E0E
D1569-AB2F-407C-B728-4EDDC463C385#viewer>

When you re-installed, all your software went back to ³Version 0². Unless
you update at this point, you just reinstated all the bugs that have ever
been fixed. Chances are, you won¹t be able to open Entourage at all unless
you update, because the database was upgraded in one of the fixes.

9. Resolve all Font Duplicates by removing the old versions from the
System.

The Installer is a simple-minded beastie. It can¹t tell whether the fonts
it needs are already on the system or not (Apple can take part of the blame
for that: it won¹t tell the Installer whether a font is there or not...)

So the Installer adds a complete new set of Microsoft fonts when it runs.

If you don¹t get them out, the system will suffer constant problems.
Duplicate fonts is the most common cause of ³crashing² and ³slow
performance².

a. Run Font Book

b. Look in the Font Book help for information on how to find and disable
duplicate fonts.

c. The Help Topic is headed ³If a warning symbol appears next to a font
name².

d. If you don¹t do this, nothing will work right.

10. Clear out all caches

a. Download and run a copy of OnyX from
http://www.apple.com/downloads/macosx/system_disk_utilities/onyx.html

b. Follow its instructions.

c. It¹s best to use the ³Automatically do everything² tab: the
instructions are complex and require a high level of system knowledge.

d. Immediately restart OS X (before it has a chance to stick any junk back
in the caches).

11. Launch Word

a. Expect the startup to take a little longer because both the system and
Word must rebuild their font caches.

12. Clean out old documents

a. Documents will be slow if they contain lots of unresolved tracked
changes. If the Reviewing toolbar opens when you open a document, begin by
accepting all changes in the document. Then save and close the document to
force Word to clean it out.

b. Documents in the old binary .doc format will be slow. Update each to
..docx next time you need to make a change.

c. Documents with unresolved references to old non-existent fonts will be
slow. Run the Compatibility Report and if any fonts are shown as needing
substitution, replace them with fonts that are currently available.

d. Documents with unresolved references to unavailable printers or
templates will be VERY slow. Use Tools>Templates and Add-ins to attach a
current template, then print a page to the current printer. Save the
document after doing both of these.

Hope this helps

after reinstalling Word, noticed that it did NOT ask me to put in the product
key so therefore the entire program was not removed. now at a total loss of
what to do or why it happend.

--

The email below is my business email -- Please do not email me about forum
matters unless I ask you to; or 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 | mailto:[email protected]

 

[Stokvis1]

WOW! seems very complicated and lengthy process with no certainty that it would succeed. Wouldn't it be much easier and less complicated since I have Time Machine on my Mac to simply erase the entire HD, then do a clean install and then back up everything and reinstall all major applications including MS Office?

I know it will be very timely process but think that likelihood of success will be greater. I await your comment before deciding what to do.

Also, would it be helpful to pay Microsoft to help fix the problem either by email or telephone support. I have now spent 10 days without being able to use office.

thanks,
Jack

 

[John_McGhie_[MVP]]

I wouldn¹t go anywhere near Time Machine for this one. All that would do is
bring back the same files that are currently causing problems.

I would erase the HDD then re-install the system.

Then update OS X all the way up.

Then do a clean install of Office 2008.

Then update Office 2008 all the way up.

Then use FontBook to resolve the Duplicate Fonts.

Then disk utility to Repair Permissions.

Then reboot, and bring the other apps back from Time Machine.

Make sure you do not bring back any preferences or system software. It
appears that the error is affecting the Airport Base Station Utility.

Hope this helps

WOW! seems very complicated and lengthy process with no certainty that it
would succeed. Wouldn't it be much easier and less complicated since I have
Time Machine on my Mac to simply erase the entire HD, then do a clean install
and then back up everything and reinstall all major applications including MS
Office?

I know it will be very timely process but think that likelihood of success
will be greater. I await your comment before deciding what to do.

Also, would it be helpful to pay Microsoft to help fix the problem either by
email or telephone support. I have now spent 10 days without being able to use
office.

thanks,
Jack

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]

 

[fvdario]

I have a similar problem and it's driving me nuts. Mr. Jones mentioned this in the thread:
&quot;When you say &quot;open&quot;, are you referring to launching Word or are you
referring to 'opening' a file after Word has been successfully launched?
That can make a difference in how to proceed.&quot; Then suggested a solution for the former. My problem is the LATTER. Files sometimes open and sometimes do not. Pls HELP. I can relate to Stokvis1 - I just feel the urge to un-install the softwae, exchange the damn thing and re-install it, or even just go buy iWorks and forget all about this MS Office 2008 for MAC. IF I lose it and do just that (un-install MS and install iWorks) would that be a good idea, if only to simplify the matter? I NEED my word processor to work NOW and cannot waste any more time trying to restore documents and revising them, to find out they open later on then do not open the next time.

Naturally, if i don't have to, what should i do now? Thank you.

 

[John_McGhie_[MVP]]

Well, I can see you're upset about this, but sadly all the emotion is
getting in the way of communication

I can't tell how you are opening the files, nor can I see what the pattern
is.

If the issue is what I think it is, it is a problem with the computer, not
Word. So if you were to remove Word and use other software, you would
probably get the same problem with the other software.

But without lots of accurate information from you, I can't distinguish
between several problems.

I need to know how you are opening the files (what keystrokes are you
using?)

I need to know what your update level is (from the Word>About Word...) menu
item.

I need to know what file format your documents are in (.doc or .docx?) and
what extension you have on the file names.

If you get me that info, we should be able to help...

Cheers

I have a similar problem and it's driving me nuts. Mr. Jones mentioned this in
the thread:
"When you say "open", are you referring to launching Word or are you
referring to 'opening' a file after Word has been successfully launched?
That can make a difference in how to proceed." Then suggested a solution for
the former. My problem is the LATTER. Files sometimes open and sometimes do
not. Pls HELP. I can relate to Stokvis1 - I just feel the urge to un-install
the softwae, exchange the damn thing and re-install it, or even just go buy
iWorks and forget all about this MS Office 2008 for MAC. IF I lose it and do
just that (un-install MS and install iWorks) would that be a good idea, if
only to simplify the matter? I NEED my word processor to work NOW and cannot
waste any more time trying to restore documents and revising them, to find out
they open later on then do not open the next time.

Naturally, if i don't have to, what should i do now? Thank you.

--

The email below is my business email -- Please do not email me about forum
matters unless I ask you to; or 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 | mailto:[email protected]