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.
Shubham Kalmegh commented
This happens in Online Word/PowerPoint. What worked for me? - Open file in desktop application and slight change and then save. Refresh the page, this will fix.
Peter Spiekstra commented
Mostly resolved after a few hours
@Some Thanks. I had the file open on my browser and I was trying to replace it with a copy I edited on my computer.
i tried checking it out, then checking it back in and that worked.
I had this error and realized that the file was open in many of the tab that I had on my browser.
From technet forums try this maybe? This issue seems caused by web client adding lock on the file.
You could try to add below registry to disable the lock function of web client service:
<additional information and recommendations>
Registry to disable lock function when web client service is started:
1. Start web client service on user side
2. Find registry: HKLM\SYSTEM\CurrentControlSet\Services\WebClient\Parameters on their machines.
3. Find value: SupportLocking(if no, please add), set its value to 0, want to just disable lock feature.
@Rashid Mehmood, opening the document and closing it worked for us too.
Swapnil Nikam commented
I am still experiencing this issue, I tried all other solution i.e. clear cache, try oter browser, wait for 10 min, wait for 30 min, wait for 1 hour, no luck
I found another workaround:
Simply use another browser! You should now be able to checkout the file you have problems with and check it back in.
After that use your original browser.
Greetings from Germany
Gustaf Sahlström commented
I have seen similar. Found a workaround though: by syncing to my laptop through the Onedrive client, I could use Explorer/Finder to move the file. This move then synced up as expected.
The fact that the local client did not get an error is interesting, but I'm happy that I found a way around this annoying error.
Navneet Kaur commented
The solution- "The file is locked for shared use by" error is displayed, as properties of a file can not be changed if a file is open in edit mode by any user
Scott Knitter commented
Not sure how people are going into Word Online and saving the file with the same name, as you have to change the name for the Save button to work.
Tom Braman commented
Please vote for this suggestion at https://sharepoint.uservoice.com/forums/329214-sites-and-collaboration/suggestions/35931814-file-lock-override (same issue, but with more votes than this one)
Rashid Mehmood commented
@Ryan Helmer - thanks very much - opening in word online and saving as same name worked for me.
J Bedford commented
This is very annoying for our users.
It would be great to have:
- The ability to see who has locks on a file, and send them a message directly from that view in order to ask whether it is legitimate.
(A) Users should have a view that shows all of their own locks, perhaps per Document Library or by Recency.
(B) Admins should be able to search by Document Library or by User, etc. Or,
(C) If empowering Users thru a view feels like "too much" for most users, then empower Admins / Owners to be able to prompt Users to take action.
- The ability to force release a "phantom" / "illegitimate" lock. This should be possible for any User to do for any of their own locks, and for any Admin to do for any locks.
- If a legitimate lock is forced released (i.e., there have been changes made by the User whose lock it is since the last auto-save, or there has been activity by that User in the document "recently"), then whoever is trying to force release the lock should be presented with options:
(A) Save the document as a new version and release the lock and kick the User out of the document,
(B) Notify the User / send a message to the User, or
(C) Do nothing.
- Instructions on how to "properly" close a file in each application type (i.e., Word Online vs Word 365 vs Word 2016) such that locks will be properly released. It is evident that closing a tab in Word Online, even if no changes have been made for minutes or longer, does not properly release locks.
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.