MS Office 2007 crashes when Save As

PorterComp

Member
Reaction score
9
Location
Mississippi
Here's one for you guys/gals.

Client upgraded from office 2003 to office 2007. Not sure exactly when this started, but they stated that when they do a "save as" Word shuts down and then they reopen it and it "recovers" the document. One of the three computers that were upgraded have this problem. The one that does not is the one computer that "stores/shares" all the files. Could this be related or just coincedence?

any suggestions on where to go with this one?
 
Sounds like it's a file permission issue on the 'server' computer. Make sure the other users have the necessary read/write/change access to the folders.
 
I think used my words wrong. They didn't "upgrade". They did uninstall 2003 and then install 2007, not an actual upgrade.

I checked the permissions on the folder on the 'server' computer and they are correct in that all users in the organization can access them.

They told me today that many of the docs that they are trying to save as were created in 2003 or earlier, opened in 2007 and then try to 'save as'. It's at this point that Word shuts down and then when they reopen it, word recovers the document, then they are able to save the doc and it doesn't happen again on that document.

Any clues?
 
I still have no solution for this...any other ideas? a batch converter is a work-around, dont want that...Office wasn't updated on all machines, one of the machines causing the problem is new with freshly installed office 2007...permissions on the "server" machine are set for 'everyone' full.

More info. The 'creator' of these files placed a 'read only' on the files that the others are attempting to do a 'save as' on. When a user attempts to File>save as is when Word closes and then reopens with the recovered document. Then all is good with that file. I've looked all over the Net and all over MS Technet and can't find anything on this.

I'm at a loss here? Any help would be appreciated.

Thanks
 
No wanting to state the obvious but have you tried running the repair option via Add Remove Programs?

Try creating a txt file on the share using the PC with the problem to see if this is a permissions issue, or you could check the effective permissions on the shared folder to see if the PC\user has persmissions to add and edit files.
 
I had a similar problem a few years back after I moved a legal database onto a new server. The system would generate mail-merge letters and documents via word which were then stored and index by the database. After the system was moved to the new server everything worked fine including creating new mail-merge documents, but any existing documents would take an age to open and would often result in Microsoft Word crashing on the client PCs. I identified the problem using a Hex editor to view to file contents of a newly created file and one imported from the old system. Each Word document stores the original file path name in its metadata and could see that the file header on the old documents was much larger than that on the new and to add to the mess these contained the full mapped drive path rather than a more efficient UNC naming convention. I manually removed the extra metadata from one of the old documents that had previously given problems and lo-and-behold it opened perfectly & quickly.

Having successfully resolved the problem on a single document I then had to rectify the issue with the tens of thousands of other files! For this I used a metadata removal tool. It took several hours to strip all the metadata from the old files, but thereafter everything worked perfectly.

Doc Scrubber from Javacool.
 
Back
Top