File locking bug in SharePoint - frequently get file locks.
File locking has been an issue in SharePoint for as long as I can remember, now carried forward into TEAMs.
This is an obstacle to our adoption of TEAMs - people get frustrated by it (including our TEAMs support team!).
Frequently unable to save my files because TEAMs/SharePoint believes another user (Me!) has it locked. Only answer (as ShaePoint won't let you rename or delete the original whilst locked) is to save a copy, close the file, wait 30 min or so and then hope TEAMs/SharePoint has sorted itself and delete the old file.
Seems to me that it happens if handshake between SharePoint and client is lost momentarily.
Jessica Darago commented
I have a pseudo-fix for this! If you are working in the native Word app (as opposed to working in Teams or WordOnline), you have to formally close the file using Ctrl+W (Windows) or Cmd+W (Mac) or the File dropdown. Simply closing Word does not work.
I have not tested this with Excel or PowerPoint, but I would bet it's the same.
This may not solve all instances, but so far it has worked for me.
Mohammed Rauf commented
We use Sharepoint onpremise and we have simillar issue with Teams. For us the message is different . It says "Sorry, we couldn't open <sharepoint path to file>.
Workaround is to quit teams. On quitting teams the file opens without any issues. The workaround works everytime. Talking to Microsoft support has not helped.
Microsoft needs to fix this at the earliest.
Murtuza Husain commented
Its May 2020 and still at enterprise level this isnt solved. It has already become a major hindrance in adoption!
OMG, same issue here.
Michael K commented
I am still facing this issue. Can someone please post a fix for this problem for the average person. Thanks TechNet forums but I don't speak tech.
From technet forums - 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.
This is so bad ... why why why Microsoft
Lee Landers commented
I am having the same issue. I'm trying to delete an old document and the file is locked. I have not yet been able to figure out how to delete or rename it and it is causing confusion within our team. This is a huge hindrance to collaboration.
Paul M commented
Got locked file issue throughout our SharePoint tenant as Teams uses sharepoint for file storage so its effected too. To re-produce 1) Create new file from browser, back out and try setting metadata properties and you are greeted with locked file.
Same problem, we have to wait 5 to 10 minutes to release the file and be able to rename it, or rename the file directly from Sharepoint/OneDrive.
Please improve the replications ...
we have the same problem. it's driving our users mad!
Manju Pingle commented
i created a file with a password in a MS Team of which i am the owner but it still only opens READ ONLY even after i put the password
We also have the same problem. Please vote so that Microsoft fix the issue
Rob Kellock commented
Does my nut in continuously. It shouldn't ever happen, but if it does the least you should expect is for Site Admins to be able resolve the issue - and they can't either. Lots of advice on how to available, but it rarely resolves the issue.
I cannot believe Microsoft has not fixed this. It's almost a Deal Breaker for using this functionality in Teams. Thanks Microsloth
I get this constantly trying to edit things, rename files, edit posts, etc "Failed" sorry this file was locked , etc etc, truly frustrating.
Two years later the problem is still there! Really annoying.
This problem is still not solved. Very frustrating for our customers.
Microsoft, prioritize this bug. It's a legacy bug that does not match with the user expierence of Teams. I understand it is a difficult bug to squash, but it is very annoying. Especially because the instructions to solve it, are unclear.
I found this mostly when using chrome and creating a file via SharePoint "New" or when saving a new file from a desktop app to Sp when required properties are missing. that is using edge or uploading the file might be a (clumsy) workaround.