A client of mine has a strange problem. She has just moved to a Mac within the last six months. Her copy of Word 2008 appears to be crashing whenever she begins to edit an old word doc from Office 2003 (from her old PC). However, she has also begun experiencing crashes involving brand-new docx files. In addition, these crashes do not “recover” properly. The app says that it will re-start with a saved copy of what she was working on, but when the app gets back up and running there is nothing - no document, no auto-saved copy, nothing except a blank, new page. Any suggestions on what might be happening?
She lives about an hour and a bit away from me, so I am not going to visit for a few days, but I would love to have some sort of a clue/answer for her once I make the trip. Any and all help would be appreciated. TIA.Geshel PS, reposted from microsoft.public.word.application.errors on the suggestion of another poster. Would have crossposted rather than multiposted had I seen this NG originally. My return e-mail address is an automatically monitored spam honeypot.
Do not send e-mail there unless you wish to be reported as a spammer. Please send all e-mail to my first name at my last name dot org, with a subject-line of “NEWSGROUP REPLY FOR NEO GESHEL” (all uppercase). CyberTaz 7/5/2009, 5:49 น. The first considerations for any new user/installation when problems arise: First of all, Do Not take the typical PC approach of reinstalling the software:-) That's rarely more than a waste of time & could make matters more difficult to deal with. If that does become necessary there are appropriate steps to be taken to first Remove then properly re-install. Has the software been updated? Use Help AutoUpdate in any Office app.
Has OS X been updated? Get the latest Combo Update from Apple Downloads. Has Disk Utility - Repair Disk Permissions been run recently? Additional suggestions & troubleshooting procedures can be found here: Additionally, AutoRecover doesn't have an opportunity to start creating autorecovery files until a new doc has been saved at least once during that session.&. the 'Save AutoRecover data every:' time period set in Word Preferences has elapsed.
HTH :) Bob Jones Office:Mac MVP 'Neo Geshel' wrote in message news:[email protected]. Phillip Jones, C.E.T. 7/5/2009, 7:58 น. Taz, Its been so long since I've had a word Crash. Does when a crash occurs, does the File show up in the Trash like it use to? I can remember if word or excel crashed and you restarted the file would show up in the trash with some code name. CyberTaz wrote: The first considerations for any new user/installation when problems arise: First of all, Do Not take the typical PC approach of reinstalling the software:-) That's rarely more than a waste of time & could make matters more difficult to deal with.
![]()
Users of Microsoft's Office for Mac 2016 who upgraded to OS X 10.11, aka El Capitan, have become increasingly frustrated by repeated crashes of the Office apps. Close Microsoft Word for Mac. Open the Documents folder, and then open the Microsoft User Data folder. Locate the file that starts with the following words: “AutoRecovery save of” and select the document you want to recover, and rename the file Click the File menu, and then select Save As.
If that does become necessary there are appropriate steps to be taken to first Remove then properly re-install. Has the software been updated? Use Help AutoUpdate in any Office app. Has OS X been updated? Get the latest Combo Update from Apple Downloads. Has Disk Utility - Repair Disk Permissions been run recently?
Additional suggestions & troubleshooting procedures can be found here: Additionally, AutoRecover doesn't have an opportunity to start creating autorecovery files until a new doc has been saved at least once during that session.&. the 'Save AutoRecover data every:' time period set in Word Preferences has elapsed. Phillip M. Jones, C.E.T.
'If it Ain't Broke, Don't Fix it' mailto: Neo Geshel 7/5/2009, 18:30 น. After having visited my client, and found nothing wrong, she has now reported an additional problem. When having two files open, and trying to save the new one to the hard drive, she receives the following error message: “ The disk is full, trying to write to Macintosh HD. Free some space on this drive, or save the document on another disk. Try one or more of the following: 1 close any unneeded documents, programs and windows. 2 save the document on another disk.
” The problem is, her hard drive is 500Gb in size and she's only making use of around 80Gb of it!! In other words, W-T-F?!?!?! Logically she should not be receiving this error message at all. She clicked OK on that error window, and got another message: “ Word is unable to save the auto-recover file in the location you have specified. Make sure you have specified a valid location for auto-recover files in preferences, and that you have permission to write files to the location you specified. ” I also checked that location when I was there, and didn't find any problems with the auto-recover location.
Since I am no-where near her computer, I must try to debug this at a distance. Does anyone have any clue at all as to what might be going wrong? In my visit, the normal.dot was deleted and rebuilt, all permissions were rebuilt (and none that had problems were associated with Office at all!) and the drive itself was verified to be in great condition. Office is up to date, with the latest patches, and everything else appears to be functioning just fine.
TIA.Geshel -. My return e-mail address is an automatically monitored spam honeypot.
Do not send e-mail there unless you wish to be reported as a spammer. Please send all e-mail to my first name at my last name dot org, with a subject-line of “NEWSGROUP REPLY FOR NEO GESHEL” (all uppercase). John McGhie 8/5/2009, 3:32 น. Tell the user to first ensure that ALL the updates for Mac OS X and for Microsoft Office are applied to her computer. That's your starting point. Until she's fully up-to-date, all bets are off.
After applying all the updates, it sometimes helps to use the Mac OS X Disk Utility to 'Repair Disk Permissions'. Then reboot the computer!
The 'Disk Full' error is very non-specific. It means that Word was unable to write to or delete one of about 25 files it has open while working on the document. That, in turn, often indicates problems with the folder permissioning within the user login.
Hope this helps On 8/05/09 11:30 AM, in article [email protected], 'Neo Geshel' wrote: - Don't wait for your answer, click here: Please reply in the group. Please do NOT email me unless I ask you to. John McGhie, Microsoft MVP, Word and Word:Mac Sydney, Australia. Mailto: CyberTaz 8/5/2009, 3:30 น.
Two diagnostic steps to help narrow down the possibilities: 1- Have the user log out then log in while holding the Shift key, 2- Have the user log in normally & run Word in a new/different User Account Reply with the result of each. Also, were all the steps you've taken done while logged in as an Administrator? You're right about that first message - it's usually misleading but actually indicating that the OS is refusing to write the file regardless of how much space is available. It's a throwback message to the days of the Classic OS. Regards :) Bob Jones MVP Office:Mac On 5/7/09 9:30 PM, in article [email protected], 'Neo Neo Geshel 9/5/2009, 18:24 น. CyberTaz wrote: Two diagnostic steps to help narrow down the possibilities: 1- Have the user log out then log in while holding the Shift key2- Have the user log in normally & run Word in a new/different User Account Reply with the result of each.
Also, were all the steps you've taken done while logged in as an Administrator? You're right about that first message - it's usually misleading but actually indicating that the OS is refusing to write the file regardless of how much space is available. It's a throwback message to the days of the Classic OS. Regards :) Bob Jones MVP Office:Mac My client will be going on vacation soon, but I will try to get them to do these actions before they actually leave town. There also is no second account on the system (there is just the one user account). Thanks for your help, will post the results here. Cheers, Geshel -.
My return e-mail address is an automatically monitored spam honeypot. Do not send e-mail there unless you wish to be reported as a spammer. Please send all e-mail to my first name at my last name dot org, with a subject-line of “NEWSGROUP REPLY FOR NEO GESHEL” (all uppercase). Neo Geshel 9/5/2009, 18:26 น. John McGhie wrote: Tell the user to first ensure that ALL the updates for Mac OS X and for Microsoft Office are applied to her computer.
That's your starting point. Until she's fully up-to-date, all bets are off. After applying all the updates, it sometimes helps to use the Mac OS X Disk Utility to 'Repair Disk Permissions'.
Then reboot the computer! Done, done and done; and all mentioned in the previous post (had you chosen to read it). The 'Disk Full' error is very non-specific. It means that Word was unable to write to or delete one of about 25 files it has open while working on the document. That, in turn, often indicates problems with the folder permissioning within the user login. Permissioning did not indicate any problems, as a full Repair Permissions (once again, as mentioned in my previous post) brought up nothing from within the Office 2008 folder or anything related to it.
Geshel -. My return e-mail address is an automatically monitored spam honeypot. Do not send e-mail there unless you wish to be reported as a spammer. Please send all e-mail to my first name at my last name dot org, with a subject-line of “NEWSGROUP REPLY FOR NEO GESHEL” (all uppercase).
Clive Huggan 9/5/2009, 21:54 น. On 10/5/09 11:26 AM, in article [email protected], 'Neo Geshel' wrote: John McGhie wrote: Tell the user to first ensure that ALL the updates for Mac OS X and for Microsoft Office are applied to her computer. That's your starting point. Until she's fully up-to-date, all bets are off. After applying all the updates, it sometimes helps to use the Mac OS X Disk Utility to 'Repair Disk Permissions'.
Then reboot the computer! Done, done and done; and all mentioned in the previous post (had you chosen to read it). One of the great rewards of people such as John McGhie who voluntarily give their expertise to fellow Office-sufferers is to chuckle over snide comments like this!
The 'Disk Full' error is very non-specific. It means that Word was unable to write to or delete one of about 25 files it has open while working on the document. That, in turn, often indicates problems with the folder permissioning within the user login. Permissioning did not indicate any problems, as a full Repair Permissions (once again, as mentioned in my previous post) Ooh, and there you go again. I don't know why John bothers. Clive Huggan brought up nothing from within the Office 2008 folder or anything related to it.
Geshel Neo Geshel 10/5/2009, 9:51 น. My apologies if my post was offencive to you, but I am one of those people who actually RTFM.
Or, in other words, I actually take time to read what was originally posted, rather than 'shooting first and asking questions later'. Unfortunately, this also means I have limited patience for those who are diametrically opposite. Virtually every point he made I had already covered, handled and dismissed in the very post he was responding to. I may be responsible for the reply to his post, but I can't be held responsible for his failure to read the original post in the first place.Geshel -.
My return e-mail address is an automatically monitored spam honeypot. Do not send e-mail there unless you wish to be reported as a spammer. Please send all e-mail to my first name at my last name dot org, with a subject-line of “NEWSGROUP REPLY FOR NEO GESHEL” (all uppercase). John McGhie 11/5/2009, 2:02 น. No-one is holding you responsible for my behaviour. Only your own. I read your post, which raised a question in my mind about the sequence in which you performed various operations.
I contribute here as a hobby, because some folks are nice and take the trouble to say thanks for the effort, which makes me feel good. If you wish to be one of the other kinds of folks, well, I'll just leave your posts for someone else. If you want a 'professional' level of service, then you will find my business contact address in the.sig. Send me a firm order for $500.00 and that will buy you four hours of my time, and you can be as rude as you like.
Cheers On 11/05/09 2:51 AM, in article [email protected], 'Neo Geshel' wrote: - Don't wait for your answer, click here: Please reply in the group. Please do NOT email me unless I ask you to. John McGhie, Microsoft MVP, Word and Word:Mac Sydney, Australia. Mailto: [email protected] 11/5/2009, 9:30 น. I'm having similar problems when editing either doc. Files and then trying to save the file with the new edits.
I experience a sudden crash of MS Word. I'm also having problems opening old doc files. I have the latest updates to the OSX system and MS word. I have run disk utilities; ran repair disk permissions; and, I still have the same problems of trying to save the most recent edits for both doc and docx files. I have closed all programs and even after the disc repair, I have rebooted my computer I have logged out and then log-in while holding the shift key.
Nothing seems to work. Please help Oracle69 CyberTaz 11/5/2009, 12:20 น. Yours is actually a different situation even though the symptoms may sound similar. The cause is most likely one or both: Corrupt document, or A corrupt Normal.dotm (I'm assuming you're using Office 2008?) You'll find information of both issues in the Troubleshooting suggestions on this page related to the topic: 'Unexpected quit while in use'. I'd try testing Normal.dotm first.
HTH :) Bob Jones Office:Mac MVP wrote in message news:[email protected]. Neo Geshel 30/5/2009, 1:09 น. Sorry, but I'm just your average, everyday hardworking middle-class person. I don't work for the government, I'm not in healthcare or the legal system and I'm not associated with any of the big multinational companies.
Ergo, I cannot afford those rates. My apologies, but no silver spoon here. There are a few Apple Authorized Service Providers around here, though, that charge half as much for twice that amount of time. Only thing is my client lives in the boonies, and needs the computer every day. Can't just drag it into town for every small bug.
Cheers.Geshel (BTW, why are you top-posting? Are you stuck with some Windows program, like Outlook Express? I thought all normal Usenet programs bottom-posted, as per proper Usenet specs and 25+ years of established netiquette.) -. My return e-mail address is an automatically monitored spam honeypot. Do not send e-mail there unless you wish to be reported as a spammer. Please send all e-mail to my first name at my last name dot org, with a subject-line of “NEWSGROUP REPLY FOR NEO GESHEL” (all uppercase). John McGhie 30/5/2009, 3:29 น.
Hi Geshel: On 30/05/09 6:09 PM, in article [email protected], 'Neo Geshel' wrote: There are a few Apple Authorized Service Providers around here, thoughthat charge half as much for twice that amount of time. Yep:-) It's a marketplace as everywhere else, you get what you pay for:-) (BTW, why are you top-posting? Are you stuck with some Windows programlike Outlook Express? I thought all normal Usenet programs bottom-posted, as per proper Usenet specs and 25+ years of established netiquette.) Faster. Like most of us, I rarely have more than four hours of 'hobby time' in a day, usually only half that much. However, the groups I cover can carry as many as 300 new posts per day. If the newest information is at the top where I can see it in the first screenful without scrolling, it means I can provide a lot more coverage in the time I can afford for doing this.
Obviously, I would prefer that you top-posted too, because that makes my job faster and easier. But if you prefer not to, no problem. Just excuse me if I leave such posts until I have more time, when we get busy. Cheers - Don't wait for your answer, click here: Please reply in the group.
Please do NOT email me unless I ask you to. John McGhie, Microsoft MVP, Word and Word:Mac Sydney, Australia. Mailto: [email protected] 29/9/2014, 22:35 น.
Crashes and freezes in OS X are mercifully rare, but they do occur. Fortunately, most of them can be resolved readily; and even though a crash or freeze may have any of numerous causes or symptoms, the same procedure works for troubleshooting most of them. Crashing apps Your first step should be to determine the scope of a problem. Is just one application having difficulties, or is the whole system affected?
Send a report, or not: If an app quits unexpectedly, you know that it's at least part of the problem. App crashes are usually accompanied by an error message. If you see one of these, click Reopen to send Apple a report with details about your system configuration and what went wrong, and then relaunch the app.
Or click OK to send the report without relaunching the app. With OS X's default settings, a dialog box like this appears after most app crashes. Click Reopen to send a report to Apple and relaunch the app.
If you don’t want to send Apple information about crashes automatically, go to the Security & Privacy pane of System Preferences, click the lock icon, and enter your username and password to unlock it. Then click Privacy, select Diagnostics & Usage, and uncheck Send diagnostic & usage data to Apple. After you do that, the options in the crash dialog box change to Ignore, Report, and Reopen; only if you click Report is information sent to Apple.
If you change your preferences to prevent crash reports being sent to Apple automatically, a dialog box like this appears when an app crashes. Skip reopening windows: If the app crashes again after you relaunch it, you’ll see a message asking whether you want to reopen the windows that were open the last time. I suggest clicking Don’t Reopen, on the theory that something in one of the open windows may have caused the crash. Either way, as long as the app functions correctly from then on, you can go about your business. (If it continues to crash, follow the steps below, beginning with “Restart.”) When an application crashes a second time after you relaunch it, OS X asks if you want to reopen its windows.
![]()
Most likely you don't. Spinning beach balls and other bad signs Sometimes, however, an app freezes but doesn’t quit. If your symptom is an unresponsive Mac—perhaps featuring the dreaded spinning wait cursor, sometimes refered to as the 'spinning beach ball' or as I like to call it, the “spinning pizza of death” (SPOD)—you’ll need to narrow down the cause. Switch to another app: Try switching to another app—for example, by clicking its Dock icon or pressing Command-Tab. If other apps respond, and especially if the SPOD appears only when you hover the pointer over a window or menu belonging to the app that was in the foreground when your Mac stopped responding, try force-quitting that app. One way to do this is to press Command-Option-Esc, select the app in the list that appears, and then click Force Quit. (Sometimes you may need to repeat this once or twice to get the app to quit.) If this force-quitting succeeds, try relaunching the app.
More often than not, that will be enough to bring the app back to life. If relaunching (or force-quitting and then relaunching) an app doesn’t do the trick, if none of your apps respond, or if your mouse pointer is frozen, move on to the following steps—try each one, in order, until the problem goes away. Restart: If you can choose Restart from the Apple menu, do so. If not, press Command-Control-Eject (the Eject key looks like an upwards-pointing arrow with a line underneath it) to force an immediate restart.
If even that doesn’t work, press and hold the Power button until your Mac shuts down, then press the Power button again to turn your Mac back on. Check disk space: A startup disk that’s extremely low on disk space (10GB or less) can lead to slowdowns and worse. Delete some files (or move them to another disk) to make more space.
For help, see Try another document: If an app always misbehaves when a particular document is open, try closing it and opening a different document. A damaged or corrupted file could be the source of the problem. Update your software: Make sure OS X itself, and any apps you use regularly, are up to date, because a software update may have fixed a crash-producing bug.
Choose Software Update from the Apple menu to update Apple software and anything downloaded from the Mac App Store; for anything else, use the app’s built-in software update feature or download the latest version. Disconnect peripherals: If you attached any new devices recently—especially USB devices—try disconnecting them. Restart and see if the problem recurs. If not, the device may be faulty or, more likely, it may require updated software or firmware.
Contact the device’s manufacturer for assistance. Disable plug-ins: If the app that’s crashing includes any extensions, plug-ins, or other extras, try disabling or removing them to rule out the possibility that the add-on software is the culprit. Try a safe boot: To disable certain software that loads at startup and to run cleanup processes that may resolve random gremlins in your system, try a safe boot: Restart your Mac, and, immediately after you hear the startup sound, press and hold the Shift key until the gray Apple logo appears on the screen. If the problem goes away, restart again normally and try again. Repair your disk: Disk errors can lead to all sorts of problems, crashes included. Try using and using Disk Utility’s Repair Disk feature to look for and fix common disk errors.
Run Apple Hardware Test: Apple Hardware Test is a special utility you can run to test your Mac’s logic board, RAM, graphics board, and other components for errors that could lead to crashes and worse. Has complete instructions for using this tool. Add RAM: If your Mac has a small amount of RAM (say, 4GB or less) and has available slots to add more, try increasing your RAM. Extra RAM can speed up many operations on your Mac and can reduce the likelihood of crashes and hangs related to running out of memory.
If you try all those things and continue to have crashes or freezes, contact the app’s developer (if it’s a single app) or Apple (if the problem is system-wide) for further advice and assistance.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |