Fix is locked for shared use
For whatever reasons, when working with files, I get the "is locked for shared use by" message when trying to move a file. And I am the one locking the file... How can I lock the file myself ? I run no flows, I have only shared the file to the user. Those kind of issues are very annoying and very specific to SharePoint mysteries. End users don't understand those messages. After a while the lock seems released.
I think Issues of this Type increased as Microsoft changed the default action when opening Files from Read-Only to Read-Write in the Office Online Apps. Additionally, i have worked with Microsoft on this issue and they were telling me, that we should not simply close the Tab where the Document is opend, but shall click on one of the Breadcrumb Links as stated in the Support Article https://support.office.com/en-us/article/using-office-online-in-onedrive-dc62cfd4-120f-4dc8-b3a6-7aec6c26b55d
We have seen locks beeing released in between of 5 Minutes and several Hours unable to help our Users.
Users of our Office 365 tenant are noticing an uptick in the amount of SharePoint files that experience: The file 'SharePoint site URL/file' is locked for shared use by 'same user'. We need to have an understanding of why/how long the file is locked. There seems to be no correlation between any common issues. The files seem to time out after a certain amount of time, this is one of the underlying problems...the time it takes for the file become 'unlocked'. It seems to take anywhere between 1 and 10 hours, I personally experienced this by patiently waiting over an hour last week to see how long it would take. Clearing cache and credentials manager does not fix this issue, neither does rebooting, nor signing out of Office 365, or even signing in using InCognito/InPrivate mode. I have seen some online posts talking about a 10 minute lock, but that was from development documents found on Github.
I would at the least get some more info about the 'lock' timing and what affects the timing.
Ryan Helmer commented
Agreed, just dealt with this yesterday. There is no obvious end user solution to this, and the wait period is arbitrary. The only way we were able to unlock the file was to open it in the Online version of the app, do a Save As with the same filename, then close the file. Not sure if that's what did it, or if the lock timed out coincidentally.