Once the block has been raised locally, Word will not reset it: you have to fool Word with a second copy of the file.
Saving documents will work fine for a while, then Word suddenly, indeterminately craps out.Īpparently, when Word conflicts with those mirroring, or other networking, apps or drivers, it decides the target file has somehow been locked permanently by some unknown force-even though IT is the one who locked it for writing in the first place! This is particularly common with files opened in directories that are connected with "cloud"ĭrives, like those folders used by Google Drive (or whatever the h Google is calling things now) for local, mirrored copies. The problem appears to be that Word/Office is getting confused on drives (or even down to individual folders) that are set up as writable from a network connection. Really not sure what is going on. May investigate furtherīut for time being I have a workaround. Thanks to bwayne36 for pointing the way to a simple workaround.Īlthough this problem was posted 5+ years ago, Microsoft has still not fixed it: the problem still exists in the very latest version of Office 360. I am running Microsoft Security Essentials and I did not make any changes to it to stop the message from appearing. However, the annoying message no longer appears when I save updates.ĭid not need recovery software, changes to Normal.dot, fussing with Add-ins. The document went from under 1 M to almost 2.5 M (to be expected with. doc (Word 97-2003) as detailed by bwayne36. Did not have the problem before but not sure that is relevant. Recently upgraded from Office 2010 to Office 2013. Re-appeared when document re-opened and resaved. Then did not appear for subsequent saves (as long as document remained open.) Message appeared from time to time whenever I resaved the document.
#File permission error word 2016 full
You may also check Save Folder and Word Default Save Folder permission, make sure user account has Full Control and Modify permission. Once the issue reappears again, we can determine which add-in causes this problem and then disable it.