Word for Mac 2011 keeps crashing every time I work with a document, relatively large (50Mb), on MacBook Pro. When I work at the same document, in iMac, there is no problem. What could it be?

Anonymous
2012-02-15T23:33:07+00:00

Word for Mac 2011 keeps crashing every time I work with a document, relatively large (50Mb), on MacBook Pro. When I work at the same document, in iMac, there is no problem. What could it be?

I keep receiving these messages:

"This is not a valid time name. try one or more of the following..."

"You cannot save while the file is in use by another process. Try saving the file with a new name"

"There is an unrecoverable disk error on file.

The disk you're working on has a media problem that prevents Word from using it. Try the following:

*try formatting another disk

*save document to another disk"

And I'm sure there's no disk issues, as well as problem in file names.

Anyone could help?

Regards,

Muriel

Microsoft 365 and Office | Word | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

53 answers

Sort by: Newest
  1. Anonymous
    2012-03-01T17:31:34+00:00

    John McGhie,

    Per your suggestion:

    • We set up a test Word doc (38MB)in a dedicated file this AM (clean start of Word). Made changes to the doc, but did not save. Minimized the doc to the Desktop Dock. Time Machine preformed back-up as scheduled. Note that the doc sits in the Dock with no activity.
    • At lunch attempted to save the doc in preparation to shutting Word down per your suggestion. Immediately received the notice " You cannot save while the file is in use by another process. Try saving the file with a new name"  This requires entering the doc name again and showing the path to the file folder.  In the folder is a "Word Work File L_......tmp" which was the original doc.
    • We then shut down Word and restarted to repeat.

    Same behavior as originally described.

    Respectfully,

    John

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2012-03-01T16:28:57+00:00

    Daniel,

    Here is the result:

    Per your suggestion, I set up a test doc (38MB) in a dedicated file folder that I excluded from Time Machine Back-Up, setting the Word preferences as you described ( Always create a back-up copy and auto-recovery was set  at 10 minutes. I also excluded the auto-recovery file from Time Machine back-up (TMBU)) Then made some changes to the doc and let it sit in the Desktop Dock awaiting the scheduled TMBU.

    I also set up a control test doc in a dedicated file folder that was not excluded from TMBU.Then made some changes to the doc and let it sit in the Dock awaiting the scheduled TMBU.

    • Immediately after the TMBU Word went into major failure mode: Hard drive spinning at full speed, with the Spinning Disk icon showing. Waited 10 minutes - no change. Then Force quit Word.
    • Messages: "You have forced Word to quit" - Report " You quit Word because of a problem" - Report
    • At this time HD still spinning at full speed, Word restarted, both docs reopened.  The Docs had lost their latest work.
    • Close both docs - Force quit Word a second time.  HD still at full speed.
    • Restart computer. HD still at full speed.
    • As programs start over (2) minutes, HD costs down to normal speed.
    • Open Word docs to confirm that both docs had lost their work. Upon reviewing the Word preferences "Always create a back-up copy" is no longer checked.

    I'll run this again to check the results.

    Respectfully,

    John

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2012-03-01T11:33:53+00:00

    Thanks John McGhie!

    I have been trying this approach, and it's working. The problem is when we forget about it!

    Best Regards,

    Muriel

    Hi Muriel:

    OK, the work-around to your issue is "Never leave Word open when suspending/pausing/sleeping the OS".

    It should work, but it doesn't.  Because when Word re-starts, it instantly attempts to lock the 20 or 30 files it has open for each document.

    The OS then gets very confused because some of the files already are locked...

    So:  Your answer is "Quit Word before closing the lid."  If you do, you will not see this problem again.

    Microsoft will try to make this "better" in service packs, but I would not want you to hope that this issue will ever completely go away.

    Close Word, then close the lid :-)

    Hope this helps

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2012-03-01T11:32:21+00:00

    John

    My issue is the same that he described... Besides that, the order of problems is the same that he enlisted.

    Best Regards,

    Muriel

    Hi John:

    Your issue is completely different to Muriels :-)

    You are suffering the "Can't Save" bug.  Microsoft is currently trying to find the cause of this one (I know this because I am sitting ion the Microsoft offices in Redmond as we type...).

    It appears to be a file deadlock, and yes, Time Machine could be the culprit (but there are several other possible sources of bother).  It appears to be worse in OS 10.7.

    The only thing I can recommend as a work-around is:

    1.  Every two or three hours (e.g. morning tea, lunchtime, afternoon tea) close and re-open Word.  This releases Word's hold on all the files it holds open when you are working.  Whenever you are editing a Word document, you have between 20 and 30 other temporary files open; these can run the OS X file system out of resources.
    2.  At the finish of work each day, log out of your Mac.  This cleans up the memory and enabels certain house-keeping tasks.
    3.  At the end of each week, shut the Mac down.  When you restart on Monday or whenever, OS X will completely clean p the memory and temporary files for you.

    Hope this helps

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2012-03-01T03:22:55+00:00

    Thank you, Daniel

    I'll try this on one machine for a week and recomment.

    Respectfully,

    John

    Was this answer helpful?

    0 comments No comments