Office Documents become READ ONLY after resume from sleep

[mrwoberts]

It seems the internet has plenty of results on this issue, mostly relating to older versions of office (pre 2016), but I'm struggling to find a working solution.

 

Office 2016 and Windows 10 1809

Server 2016

 

This doesn't appear to be affecting every user, possibly because the teachers are quite good at closing their documents, whereas the support staff have been experiencing this problem for a while (~3 months). They're now sick of 'Saving As' and I need to find a solution ASAP.

 

Basically, if they are editing a Word document then leave their PC (locked) for a period of time, when they return and unlock (possibly wake up - still testing that theory), the Word document has become READ ONLY.

 

One PC this morning gave the following error message...

 

The things I've tested are...

 

- Nobody else has opened this document

- Office has August 2019 updates installed (will potentially release latest updates through WSUS if need be)

- Prevented one computer from sleeping, but it still happened when the PC was unlocked

 

I'm at the school tomorrow and will have a more thorough look at it, but just wondered if anyone else has come across this.

 

Here's another Edugeek post with same error message..

http://www.edugeek.net/forums/windows-7/149522-read-only-office-documents-after-suspend.html

Edited September 19, 2019 by mrwoberts

[network41]

Is the network card going in to some sort of sleep mode and the connection being dropped to the server hosting the document. Long shot but worth checking.

[mrwoberts]

Is the network card going in to some sort of sleep mode and the connection being dropped to the server hosting the document. Long shot but worth checking.

 

Yes, I was thinking the same. That's definitely on my 'try this' list. Thank you.

[pete]

We had this for one person who has a habit of opening a word document via a mapped drive, wandering off for 30-90 minutes and the desktop goes to sleep.

 

Test if it happens using a UNC path to open the document (\\server\share\folder\whatever.docx) vs a mapped drive (H:\folder\whatever.docx).

 

Also check the difference between "immediately start typing / clicking save" vs "wait 30 seconds, then do it".

[mrwoberts]

Test if it happens using a UNC path to open the document (\\server\share\folder\whatever.docx) vs a mapped drive (H:\folder\whatever.docx).

Also check the difference between "immediately start typing / clicking save" vs "wait 30 seconds, then do it".

 

Thank you for those suggestions, I'll add them to the list. At least I know others have experienced.

[mrwoberts]

Here's an interesting thing...

 

I just reproduced this issue at a different school, simply by opening a document on the server through a UNC path, made a simply edit, then put the PC to sleep. The moment I unlock after waking up, it gives me with the error message.