04-04-2017 10:01 AM
04-04-2017 10:01 AM
SharePoint thinks a user still has a lock on. I can't adminsitratively do anything with the file online. This has been going on for almost a day.
We've cleared cache, closed Excel on his computer, cleared out some local cashe directories, rebooted, etc.
Nothing is clearing up this lock.
All I want to do is delete the file at this point, and I can't even do that.
What are my options as a Global Admin?
10-29-2019 07:29 AM
I also had this issue. Here are the steps that worked:
03-17-2020 11:24 AM
@Brent Ellis I couldn't find any way to do it through SharePoint directly. However I did find a way to use PowerShell to release the lock. The command is ReleaseLock
I wrote about it here...
05-06-2020 06:17 AM
@Charles Boisseau Just experienced the same issue with a user. To remedy I cleared the cache in Microsoft Upload Centre, no luck. Then I cleared the cache in Microsoft Upload Centre 2013, no luck. Then I cleared the internet history and cache, no luck. Then I stopped the users One Drive Sync, Success!
The user had accidentally clicked on the "Sync" button at the top of the library which had created a folder in One Drive which had not yet synced with SharePoint. I removed the synced folder from one drive to prevent this recoccuring.
Not sure if any of the actions I took prior to stopping the One Drive sync had any effect, but the above resolved the issue.
05-14-2020 06:39 PM
2020 baby yeah!
I have tried every singe suggestion in this thread.
I go to Sharepoint and go to the excel file. All good Now it's time to open in excel. Nah mate! Locked by another user.
Then I ask myself... Why and now? This is Sharepoint and I can work away just find when on the document in Sharepoint. It's not locked and I can open in excel with any other user without an issue.
I can't check it out- I get an error and it only allows me to see a portion of the error
This is just stupid. Why isn't this fixed yet?
Why do we have to mess around with a bunch of workarounds that don't even work?
05-14-2020 07:12 PM
@MattStOnge The error you're seeing is expected. Anytime you open an Office file from SharePoint (any version, SharePoint 2010, 2013, 2016, 2019, Online, etc) using Office (2010, 2013, 2016, 2019, 365 Pro Plus, Office for Mac, etc), you are guaranteed to set a file lock. That's how the product works.
There are two types of locks that can be set, and Exclusive file lock, and a Co-authoring file lock. Which lock type is set is dependent on a few key factors. When opening Office files, SharePoint will always attempt to set a co-authoring lock first. If a co-authoring lock cannot be set, SharePoint falls back to an exclusive file lock.
Exclusive file locks act exactly as their name implies. User opens the file, because of certain factors (addressed below), an exclusive file lock is set by the user's session in SharePoint. As long as that lock is in place only the user who set the lock can edit the file. If the user saves the file when they're done and properly exits the file (doesn't put the PC in sleep mode with the file open, doesn't just close the laptop lid and walk away, doesn't leave the file open for hours on end, and instead either uses file > Close, or waits for the file to completely save, then closes out of the client), then Office can send the proper network traffic to indicate it's done with the file and SharePoint will release the lock. This is known as exiting gracefully from the file, and applies to both file lock types.
Co-Authoring file locks are applied when the file is in a state that allows co-authoring and if the user is in a client that supports co-authoring. Whenever a file is opened in Office Web Apps, Office Online Server, or Office for the web, where the file can be edited in the browser, a Co-authoring file lock will always be set.
Certain Office clients (installed on your Windows or Mac machines) do not fully support Co-Authoring. For example, Co-Authoring in Excel is only supported on Office 365 Pro Plus version 1808 and newer. All other Office desktop clients do not allow for Excel co-authoring, and will always try to set an exclusive file lock.
Outside of the Office clients, there are other factors specific to the file and where the files stored that determine what file lock type is set. For example, all of the following to cause only Exclusive file locks to be set:
@MattStOnge, for you, it sounds like other users have set a co-authoring lock on the file, but your machine can only set exclusive file locks. Since the file is Excel, check that your Office client actually supports Excel Co-authoring. If you're not on the Office 365 Pro Plus client on any of the current update channel builds (1902, 1908, 2002, 2003, 2004) then you're never expected to be able to edit the Excel file in the excel client app in near real time with your colleagues. I would compare what version of Office you're using with that of your colleagues. If it's the same version, then your machine has another factor at play preventing you from joining the Excel file's Co-authoring session.
This functionality is more than just SharePoint or Office, there is a lot more in play. What settings are set in the SharePoint Document library, on the file itself, in the Office client, on your windows/mac machine, what group policy settings are set (if your local user account and machine are domain managed), all of these matter and can affect what type of file lock your Office client can set, and by direct relation, what can be done with said file.
05-14-2020 08:17 PM
The problem is that all the workstations are set up exactly the same with the same image.
All users except her can edit in Excel without an issue. At any given time, nobody is editing that document but it says it is locked when you try to edit with Excel just for that one user. Nobody else is having the problem.
I even went and imaged a whole new laptop for her with her profile. Went to Sharepoint to that document, said to open in excel. It worked 3 times in a row and then didn't 3 times.
Then went back to her original laptop and when it's locked out I say "Yeah, open and then notifiy when available". About 30 seconds later, office goes "Yo, good news...your file is available to edit. Do you want to edit?"
I'm like "Yeah....Ok"
Then it goes "Sucker... The file you are looking for C:\Profilename\File location| no longer exists!"
09-11-2020 08:36 AM
I have the same problem. In my case, it happens whenever I try to open a sharepoint file in excel, and excel always replies with a message saying the "the file is corrupt and cannot be opened" (translated). But this is not necessarily the problem.
What I found: The mechanism seems to work by IP. So, if I work on my notebook using Wifi and then open the document in the browser excel, and then I dock to my workplace and have another network, I can't release the lock anymore that comes from the wifi. Even worse: if I opened it from my homeoffice place, I cannot release that lock anymore from my office workplace...
So, the workaround for me (case 1) is to temporarily undock my device, then close the online excel browser tab, and then dock my device again.