Command Q to quit Word 2004 & then I get "unexpectedly" quit message!

[Tony]

Hi,

About 25% of the times, mainly when I go to shut down the Mac OS X
10.3.8, if I select to Quit (Command Q) Word 2004 11.1.0 (Office
11.1.1), then the application shows the message of unexpectedly quit!

My Mac is up to date in latest versions. No problems with Disk Utility
permissions, DiskWarrior or Cocktail. Also PRAM reset.

Any idea? Thanks.

 

[Beth Rosengard]

Hi Tony,

You've been having various crash problems for a long time. The only thing
we can do is point you back to the troubleshooting procedures you're already
aware of and have already tried. Did you consider Doctor Mac Direct which I
suggested in a previous post?

[I'm assuming this is the same Tony. If not, please post back .]

--
***Please always reply to the newsgroup!***

Beth Rosengard
MacOffice MVP

Mac Word FAQ: <http://word.mvps.org/MacWordNew/index.htm>
(If using Safari, hit Refresh once or twice ­ or use another browser.)
Entourage Help Page: <http://www.entourage.mvps.org>

 

[Corentin Cras-Méneur]

Hi,

Hi Tony,

About 25% of the times, mainly when I go to shut down the Mac OS X
10.3.8, if I select to Quit (Command Q) Word 2004 11.1.0 (Office
11.1.1), then the application shows the message of unexpectedly quit!

My Mac is up to date in latest versions. No problems with Disk Utility
permissions, DiskWarrior or Cocktail. Also PRAM reset.

Any third party plug-in like EndNote or Acrobat or Stuffit Deluxe for
instance ??? Any chance the Normal template could be corrupted (making
Word crash when it tries to save in it as it quits ??

Anything recurrent in the crash logs ??

Corentin

 

[Tony]

Beth,

Thanks.

Same Tony here...



Have not tried yet Doctor Mac Direct ,but eventually I may consider it.
I will let you know.

Regards,

 

[Tony]

Corentin,

Thanks.

Actually, I have all EndNote, Acrobat and StuffIt, but a removed their
plug-ins long ago. As for the Normal template, it does not fix this.
Please note that the crash is not 100% consistent or reproducible all
the times (not 100% of the times), so it seems to me that this is
something else...

I have sent the crash logs to Microsoft, since I do not quite
understand them...

Looking forward to the next Word update...

Regards.

---

 

[John McGhie [MVP - Word and Word Macintosh]]

Tony:

That might be worth fixing disk permission again.

One of the things Word does on shut-down is attempt to release the temporary
files it had open if you have been editing documents. It may possibly crash
if it can't do that.

The other thing that can do it is if the Normal template has been set to
read-only. You get a whole lot of pending writes queued to the Normal
template: if Word can't clear them, it can tip over (you should get a
warning, but sometimes you won't).

Hope this helps

Corentin,

Thanks.

Actually, I have all EndNote, Acrobat and StuffIt, but a removed their
plug-ins long ago. As for the Normal template, it does not fix this.
Please note that the crash is not 100% consistent or reproducible all
the times (not 100% of the times), so it seems to me that this is
something else...

I have sent the crash logs to Microsoft, since I do not quite
understand them...

Looking forward to the next Word update...

Regards.

--

Please reply to the newsgroup to maintain the thread. Please do not email
me unless I ask you to.

John McGhie <[email protected]>
Microsoft MVP, Word and Word for Macintosh. Consultant Technical Writer
Sydney, Australia +61 4 1209 1410

 

[Tony]

John,

Thanks.

The Normal at

/Users/tony/Documents/Microsoft User Data/Normal

is set to read and write for me.

The permissions could be the culprit, but I usually fix them before and
after installing software, so they are usually OK. i will take more
care about it.

Thanks again.

---

 

[Corentin Cras-Méneur]

John,

Thanks.

The Normal at

/Users/tony/Documents/Microsoft User Data/Normal

is set to read and write for me.

The permissions could be the culprit, but I usually fix them before and
after installing software, so they are usually OK. i will take more
care about it.

Thanks again.

When you fix permissioaans, the SYstem only corrects permissions for
folders and files specified in the Bill of Material (basically, in the
..pkg receipts the system gets when you install through the MacOS X
installer. Everything else is disregarded.
It won;t correct thsi type of file and if won;t correct permissions on
Office X itself (repairing permissions in this case can still be useful
if a resource Office needs needs to get corrected).

You might consider reinstalling Office.....

Corentin

 

[Tony]

Corentin,

Thanks.

I also run Cocktail on a regular basis.

http://www.macosxcocktail.com/

Maybe it fixes all permissions. Is there other way to fix all permissions?

On the other hand, I have not only reinstalled, but completely removed
Office with the "Remove Office" application and reinstalled Office more
than 10 times already in the past six months or so...

---

 

[Corentin Cras-Méneur]

Corentin,

Thanks.

I also run Cocktail on a regular basis.

http://www.macosxcocktail.com/

Maybe it fixes all permissions. Is there other way to fix all permissions?

On the other hand, I have not only reinstalled, but completely removed
Office with the "Remove Office" application and reinstalled Office more
than 10 times already in the past six months or so...

:-( Yeah, that should have done it.

Cocktail and diskutility are both frontends for the terminal command:
sudo diskutil repairPermissions /
They both do exactly the same thing. This command was useful in Cocktail
when RepairPermissions was not part of DiskUtility (10.0, 10.1...)

You might want to use an application like BatChmod to batch-change
permissions on all the files in ~/Documents to make sure you have
read-write permissions on all of them. You could do the same thing on
~/Library actually.

My user account is called "corentin" so all fiels in there belong to the
user corentin and the group corentin (other users have no right).

Corentin

 

[Tony]

Corentin,

Thanks -- I will try.

---

:-( Yeah, that should have done it.

Cocktail and diskutility are both frontends for the terminal command:
sudo diskutil repairPermissions /
They both do exactly the same thing. This command was useful in Cocktail
when RepairPermissions was not part of DiskUtility (10.0, 10.1...)

You might want to use an application like BatChmod to batch-change
permissions on all the files in ~/Documents to make sure you have
read-write permissions on all of them. You could do the same thing on
~/Library actually.

My user account is called "corentin" so all fiels in there belong to the
user corentin and the group corentin (other users have no right).

Corentin