Word crashes on opening after changing to Intel

[Prasm]

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

I just ended migrating Office to an iMac intel. Now I cannot open Word. I tried reinstalling Office but the error remains. Here is the repport:

Microsoft Error Reporting log version: 2.0

Error Signature:
Exception: EXC_BAD_ACCESS
Date/Time: 2009-06-17 08:14:45 +0000
Application Name: Microsoft Word
Application Bundle ID: com.microsoft.Word
Application Signature: MSWD
Application Version: 12.1.9.090515
Crashed Module Name: MicrosoftComponentPlugin
Crashed Module Version: unknown
Crashed Module Offset: 0x000d2607
Blame Module Name: MicrosoftComponentPlugin
Blame Module Version: unknown
Blame Module Offset: 0x000d2607
Application LCID: 1033
Extra app info: Reg=en Loc=0x0409

Thread 0 crashed:

# 1 0x0164f607 in _MsoPvCallocExCore + 0x0000004D (MicrosoftComponentPlugin + 0x000d2607)
# 2 0x0070b3c1 in _wdCommandDispatch + 0x003EE725 (Microsoft Word + 0x0070a3c1)
# 3 0x0071728e in _wdCommandDispatch + 0x003FA5F2 (Microsoft Word + 0x0071628e)
# 4 0x007173ed in _wdCommandDispatch + 0x003FA751 (Microsoft Word + 0x007163ed)
# 5 0x006f23ec in _wdCommandDispatch + 0x003D5750 (Microsoft Word + 0x006f13ec)
# 6 0x006fb990 in _wdCommandDispatch + 0x003DECF4 (Microsoft Word + 0x006fa990)
# 7 0x00262af7 in __mh_execute_header + 0x00261AF7 (Microsoft Word + 0x00261af7)
# 8 0x00194fa2 in __mh_execute_header + 0x00193FA2 (Microsoft Word + 0x00193fa2)
# 9 0x0019215a in __mh_execute_header + 0x0019115A (Microsoft Word + 0x0019115a)
# 10 0x020a5f2e in CNamespaceManager::Initialize(int) + 0x000024AE (MicrosoftOffice + 0x002f2f2e)
# 11 0x020a4e90 in CNamespaceManager::Initialize(int) + 0x00001410 (MicrosoftOffice + 0x002f1e90)
# 12 0x01b56adb in (MSXML + 0x00086adb)
# 13 0x01b56a1b in (MSXML + 0x00086a1b)
# 14 0x01b57f26 in (MSXML + 0x00087f26)
# 15 0x01b57fa9 in (MSXML + 0x00087fa9)
# 16 0x01b58502 in (MSXML + 0x00088502)
# 17 0x01b410f9 in (MSXML + 0x000710f9)
# 18 0x020a2a1a in CNamespaceManager::~CNamespaceManager() + 0x000007EA (MicrosoftOffice + 0x002efa1a)
# 19 0x020a5d6e in CNamespaceManager::Initialize(int) + 0x000022EE (MicrosoftOffice + 0x002f2d6e)
# 20 0x001f56bc in __mh_execute_header + 0x001F46BC (Microsoft Word + 0x001f46bc)
# 21 0x001f6fb4 in __mh_execute_header + 0x001F5FB4 (Microsoft Word + 0x001f5fb4)
# 22 0x0018e9cd in __mh_execute_header + 0x0018D9CD (Microsoft Word + 0x0018d9cd)
# 23 0x001f78c2 in __mh_execute_header + 0x001F68C2 (Microsoft Word + 0x001f68c2)
# 24 0x001f8070 in __mh_execute_header + 0x001F7070 (Microsoft Word + 0x001f7070)
# 25 0x001f860e in __mh_execute_header + 0x001F760E (Microsoft Word + 0x001f760e)
# 26 0x005d2511 in _wdCommandDispatch + 0x002B5875 (Microsoft Word + 0x005d1511)
# 27 0x00b8f01e in _wdGetApplicationObject + 0x00459EF4 (Microsoft Word + 0x00b8e01e)
# 28 0x0067862a in _wdCommandDispatch + 0x0035B98E (Microsoft Word + 0x0067762a)
# 29 0x006791ff in _wdCommandDispatch + 0x0035C563 (Microsoft Word + 0x006781ff)
# 30 0x00ae7516 in _wdGetApplicationObject + 0x003B23EC (Microsoft Word + 0x00ae6516)
# 31 0x00aefe77 in _wdGetApplicationObject + 0x003BAD4D (Microsoft Word + 0x00aeee77)
# 32 0x0225649c in __WlmMain + 0x00000047 (MicrosoftOffice + 0x004a349c)
# 33 0x00ad553c in _wdGetApplicationObject + 0x003A0412 (Microsoft Word + 0x00ad453c)
# 34 0x00002c82 in __mh_execute_header + 0x00001C82 (Microsoft Word + 0x00001c82)
# 35 0x00002ba9 in __mh_execute_header + 0x00001BA9 (Microsoft Word + 0x00001ba9)

X86 Thread State:
eax: 0x9e969c86 ebx: 0x00000000 ecx: 0x04ff92ae edx:0x9e969c8e
edi: 0xfffffffc esi: 0x0492423c ebp: 0xbfff9658 esp:0xbfff9640
ss: 0x0000001f eip: 0x0164f607 cs: 0x00000017 ds:0x0000001f
es: 0x0000001f fs: 0x00000000 gs: 0x00000037 eflags:0x00010286

Thread 1:

# 1 0x958153a6 in _signgam + 0x9566E482 (libSystem.B.dylib + 0x000013a6)
# 2 0x9589ceab in _signgam + 0x956F5F87 (libSystem.B.dylib + 0x00088eab)
# 3 0x01ac2d7d in _MerpCreateSessio

 

[JE McGimpsey]

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

I just ended migrating Office to an iMac intel. Now I cannot open Word. I
tried reinstalling Office but the error remains. Here is the repport:

Migration is always a bad idea. Likewise, reinstalling, unless you run
the Remove Office application first.

Run Remove Office (on your install CD), then reinstall and update Office.

 

[Prasm]

Sorry. I tried. I didn't work. Same reaktion and the other Office applications work fine.

New suggestions?

 

[Diane Ross]

Sorry. I tried.

Did you drag Office to the trash or did you use "Remove Office" to remove?

 

[Diane Ross]

Crashed Module Name: MicrosoftComponentPlugin
Crashed Module Version: unknown
Crashed Module Offset: 0x000d2607
Blame Module Name: MicrosoftComponentPlugin
Blame Module Version: unknown

The Microsoft Component Plugin is the key file that shows if Office is
updated.

Steps to re-install Office

<http://www.entourage.mvps.org/install/reinstall_steps.html>

In step 3 it tells you to drag the Office folder to the trash. I suggest you
use "Remove Office".

<http://www.entourage.mvps.org/install/remove_office.html>

you should make a backup copy of the preferences and templates in another
location on the machine before running the removal tool. You'll also need
your CD key when you re-install.

 

[Prasm]

I used Remove Office, and I actually also threw away the storges with the key numbers.
I noticed however that the usertemplates and the Normal.dotm were untouched.
I will try again and this time remove the templates to a secure place and remember to restart between actions.
This is very tiring but your information about the crucial file is a great help.

Pétur

 

[Prasm]

Now I tried to start from scratch. I used Remove Office og removed other things too. After installing 12.0.0 I opended Word and got the same message.

Has nobody else experienced this?

Pétur

 

[Diane Ross]

I used Remove Office, and I actually also threw away the storges with the key
numbers.
I noticed however that the usertemplates and the Normal.dotm were untouched.
I will try again and this time remove the templates to a secure place and
remember to restart between actions.

With all Microsoft applications quit, move the Microsoft User Data folder in
Documents to the desktop. When you open any Office application, it will
create a new one. If this clears the problem, you can look to the old folder
for any files that you might need. Some you can just drag back, but you
might need to copy the contents into the new file.

Delete the Microsoft User Data folder after you are satisfied that you have
recovered all your data. Entourage stores your mail in the Office 2008
Identities folder.

 

[Prasm]

I have succeeded. The thing is that not even "Remove Office" removes what should be removed. I Removed Office and everything in the Office folders in User/Library/Application Support and in User/Library/Preferences.

I saved my templates in another place.

Then I installed from scratch and Restarted in between and started up Excel and Word every time in between.

Now I have reached 12.1.9 and Word is working!

Thank you for the assistance.

Pétur in Reykjavík, Iceland

 

[Prasm]

Now Word is working on its own but I cannot open a single file made before.

Then comes the same ugly message.

This is not fun.

Pétur in Reykjavík

 

[CyberTaz]

Are you dbl-clicking the files in Finder or using File> Open from within
Word? Or does it not matter which method?

Were the files created by Word 2008 or by a different version? What is the
file format of those that won't open (.doc, .docx. .rtf...)?

By "ugly message" do you mean that Word crashes when you attempt to open the
files? The only message alluded to in your prior posts is presumably the one
that precedes the MERP. The content of the message has not been stated. What
is the wording of the message involved if not the standard "...Word has to
close" notification generated on crash?

Try running Disk Utility - Repair Disk Permissions then restart & see if
Word will open the older files.

If that doesn't correct it, select one of those files in a Finder window,
key Cmd+I (Get Info), then reset the Open With: to MS Word (12.1.9) & click
the Change All button.

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

 

[Prasm]

The ugly message is the one in the error report above.
Besides I have done all the things you mentioned.
The files are made by the same Word and the same version of Word as the one I use now. The only difference being the new Intel-computer.
I tried using the new created Normal.dotm and then it opens. But if I transfer the style sheet from my old Normal.dotm then Word crashes again on start-up. Always the same error report.
I havn't tryed to open a file from within Word — that might work.

 

[Diane Ross]

I tried using the new created Normal.dotm and then it opens. But if I transfer
the style sheet from my old Normal.dotm then Word crashes again on start-up.
Always the same error report.
I havn't tryed to open a file from within Word — that might work.

This sounds like a corrupted style sheet. If you create a new style sheet,
can you copy/paste in the old one?

This site is excellent for help with Word:

<http://word.mvps.org/Mac/WordMacHome.html>

 

[CyberTaz]

Well this is apparently where the problem is coming from... except that Word
doesn't use "style sheets".

Please describe exactly what you are doing - step by step - in order to make
what you're calling a "transfer" & how you're going about it. Something in
that process is corrupt -- it's just a matter of figuring out what it is.

 

[Prasm]

What I call: "transfer a style sheet" means that I open Organiser. In Organiser I open the old Normal.dotm. Then I transfer the styles from the old Normal.dotm to the new one that Word created on opening the first time.
If I do that and quit Word then it never gets as far as to open a new document but crashes.
I am able to open old documents from within Word.

I believe that my only solution is what Diane Ross suggested: To recreate the settings of Word that I have used until now. It is a tiresom process but having read the article about Templates in Word.mvps it seems to me that Word simply would not allow me to replace the new Normal.dotm with my old one from my other computer, (which is what the Apple Migration did originally) — and that there might be some corruption in the styles in the old Normal.dotm. But again then it is strange that the old Normal.dotm works fine on my old computer.

Do we get any further?

Thank you for your kindness, both of you.

Pétur Rasmussen
Reykjavík

 

[CyberTaz]

Hello Pétur;

Yes, that clarifies things quite well & I think you're on the right track as
to the cause of the problem. Depending on the number of Styles involved,
however, you may want to try a different approach before recreating them.

Follow your current procedure but import only a few of the styles [perhaps
only one at a time], then see if you have any trouble launching Word. If
not, import a few more & attempt to launch Word again after each "batch". In
that way you may be able to narrow down the culprit(s). It may be comparably
time consuming but will insure accuracy of the styles that are salvageable.

Another option: Use Organizer to import the Styles from a viable document
rather than trying to import them from the old Normal.dotm -- If all Styles
were in the Template they also should be in any document based on it unless
you deleted them from the doc. Even if you have to import from several files
it may be an even faster approach.

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

 

[Prasm]

A suggestion:
Could the reason for crash be a stile name with the letter æ.
In my work on recovering old styles I tried to make a style with the name Optælling, and on creating it Word crashed. Then I did the same but now with the name Optal and that worked.

Maybe Word on Intel is more sensitive to „foreign" letters than Word on ppc?