Forum Discussion
Cannot Release Lock on SharePoint Online File
- Jul 17, 2018
Locks is a complex topic and technically a client or network issue. SharePoint supports co-authoring locks unless you have Check In/Out enabled on the library. Client side locks will occur if Office cannot negotiate a co-author lock falling back to an exclusive lock. As others have pointed out, the upload center can contribute to locking and is one of the first things you should check. You can trace the calls via Fiddler on the client.
This is the technical explanation from PSS:
When a user attempts to open an Office file hosted on SharePoint in the Office client, there is an expected set of network calls we should be seeing unless there is a problem. Once a user clicks that Office file to open in client, code on the SharePoint page and (if using Internet Explorer) the Office 365 browser addon sends a command to initialize the client application (Word, Excel, PowerPoint). Once the Office client application starts launching, Office will start a HTTP conversation with SharePoint. If the Office call is already authenticated, the Office will be returned the file content. However, if not already authenticated, which is usually expected to be the case, Office will negotiate for Authentication with SharePoint. This process happens through two networking calls called OPTIONS calls. The first OPTIONS call is anonymous and expected to be rejected by SharePoint as to establish what types of authentication SharePoint will accept. The second options call will include the requested authentication information to SharePoint. If SharePoint accepts the second options, call, it will return a METHOD call, identifying what network verbs can be used to communicate with it (OPTIONS, GET, LOCK, PROPFIND, and POST are all examples of verbs for this process). Once the verbs are established the Office client will make a POST network call that requests the metadata for the file, adds the user’s session lock state (coauthor lock or exclusive lock) and to request to open the file from the CellStorage web service in SharePoint. If the Office client has never accessed the document before, the entire document will be downloaded from SharePoint and cached in the Office Document Cache. If the Office client has opened the file before, then it is already cached and only the changes will be downloaded. At this point, the Office file will open in the Office client. This entire process happens between a few milliseconds to a few seconds.
I've seen a few reports of something that sounds like this this in our tenant this week, mostly from Mac users. The error message appears in the MS Upload center when the person is trying to save a file they've been editeing. It says "The file ... is locked for shared use by <the same user> [membership]. The files are not large, e.g., a 45 KB Word doc. Haven't found a cure, yet.
Richard
- Zoltan BagyonApr 06, 2017Iron Contributor
This is a very frustrating known issue in SP Online, and I can't really understand why we don't get an admin-tool (via PS, for example) to manage it.
My greatest concern is, what I've experienced many times, that the 10 minute timeframe MS promise for auto-unlock is simply not true and it took much-much longer to get access back to the file. Also the workaround they suggest here haven't ever worked for me. So my user (and admin) experience is that whenever this issue occurs, I have no other tools to fix it than waiting, and I have to tell the same to my users.
- Alberto_da_SilvaSep 16, 2022Copper Contributor
Zoltan Bagyon Have you seen this behaviour with Document Sets as well?
- Sebastian79Jan 06, 2019Copper Contributor
Zoltan Bagyon wrote:This is a very frustrating known issue in SP Online, and I can't really understand why we don't get an admin-tool (via PS, for example) to manage it.
My greatest concern is, what I've experienced many times, that the 10 minute timeframe MS promise for auto-unlock is simply not true and it took much-much longer to get access back to the file. Also the workaround https://support.microsoft.com/en-us/help/899709/you-receive-a-filename-is-locked-for-editing-by-another-user-message-when-you-try-to-modify-a-document-in-sharepoint-even-though-you-are-the-user-who-previously-opened-the-document haven't ever worked for me. So my user (and admin) experience is that whenever this issue occurs, I have no other tools to fix it than waiting, and I have to tell the same to my users.
Same Problem here with Sharepoint online after making changes to excel in a flow. The Excel file is locked for hours. I read a lot of things, but all solutions I found are not for SP Online (office 365) but for SP on premise. For SP on premise are very easy solutions with powershell, but in SP Online we don't have something like "Get-Spweb".
- Somebody knows a solution to unlock files fast in SP Online?
- Ore any idea how to prevent Excel file locks after flow create/manipulate/copy excel files (also when the flow is crashing)?
- Any flow nodes to force an unlock available?
- Andrew SilcockJan 06, 2019Iron ContributorHi Sebastian,
We too experience this issue, as do most people I suspect.
I haven't had the issue for a while, but one suggested solution that I have read is:
Restore the locked out file to a previous version. That essentially kicks the user (who the file thinks is editing) out and allows you to then rename/ delete/ move etc the file again.
- Monette MarceloSep 06, 2018Copper Contributor
I am also experiencing this issue,, and the page you sent cannot be found. Please advise the suggested fix for this problem... thank you.
- Andrew SilcockSep 06, 2018Iron ContributorAlso having this issue here, on and off.
It was a suspected issue with Chrome a few months ago, so we updated Chrome and that seem to resolve the problem, but it is back again.
Very off-putting for new users of SharePoint.