[Last Call] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 538
  • Last Modified:

Microsoft office crashes when a laptop is not connected to the network

Hi Guys,

We've got an usual problem. When a laptop is connected to the company network it works fine. If you log off the network, and let all the files synchronise (we use redirection folders) and shut it down; then restart without the network cable, then Microsoft Office crashes when a file is opened.

Any ideas??
5 Solutions
Do you have any templates or shared files that are loaded over the network?
There is a trick you can trry to see where it is hanging up, once we find out where we can fix it:
Try to run FileMon: http://technet.microsoft.com/en-us/sysinternals/bb896642.aspx right before you open Word or a doc file. Then check to see the captured information.
There is a good chance it is stuck looking for files across the share and hangs when it can not find them.
Let us know what you find!
Yeah, it might also be crashing because of a printer driver trying to access your printer and not finding it. I'm not sure how to fix the problem but try setting up your printer settings again.
"Microsoft Office crashes when a file is opened."

Microsoft Office, stupidly, remembers ALL the file shares on all files you opened in the application.  If you get your network users to NEVER EDIT a file from a remote network resource, like another computer, this will not happen.  They should use windows explorer to COPY the file to their local hard drive, edit it, and then copy it back -- this is good practice, in case a file is corrupted, you have local backups.

You will have to do this for at least 15 files before the file cache is purged from every system.  If you need to know the details, MS office apps record the path of every file opened in the registry.  If a file that was opened on a remote computer is not available, the stupid office application siezes instead of just ignoring the error.  

I told MS of this problem over 20 years ago -- they still have not fixed the bug.  Either believe them and have the problem, or do only LOCAL file editing, and in 1-2 days, the problem will disappear.
steven_maherAuthor Commented:
Thanks for the help. The problem was solved by removing the file history in Office applications by going to Tools > General > and unchecking the file history.

Featured Post

Restore individual SQL databases with ease

Veeam Explorer for Microsoft SQL Server delivers an easy-to-use, wizard-driven interface for restoring your databases from a backup. No expert SQL background required. Web interface provides a complete view of all available SQL databases to simplify the recovery of lost database

Tackle projects and never again get stuck behind a technical roadblock.
Join Now