Teams keeping files locked after closing

[David Phillips]

I've been testing files in Teams.  It appears it's keeping files locked open after they're closed in Teams.  For example - edit a file in the Teams window, close it, then go try to delete the file 5 minutes later on the SP side, it says it's locked for editing.  Has anyone else experienced this?

[#2]

Are you also having an issue with users not being able to save a file in the "Files" tab and they have to save it with another name or save it locally to not lose their work? I noticed the problem in different tenants occasionally happening over the past couple of months but at my current project I am noticing it starting to happen too often. I am still researching it myself.

[#3]

Sortof.  What I found is if you open the file in Teams, then close it, but leave Teams open, when you try to open the file in Excel from the SP, you get the locked dialog, and you're prompted to read only or save as a different file name.  I also noticed that if you open it later in Teams, and try to edit with Excel. it says it's locked open.  Seems a bit random too.

[#4]

I found this article about changing a registry setting for the web client service but am unsure if it would have impact beyond Teams. Feel free to investigate this:  

https://techcommunity.microsoft.com/t5/SharePoint/File-locking-issue/td-p/71185

[#5]

What I think is happening is the way Teams caches files when you open it in Teams it's still keeping it open when you close it out. Also even when editing with excel online sometimes it won't gracefully exit and the lock will always stay on the file for 5-10 mintues so you cannot do things like delete/edit file name etc. but you can open it again in Teams or Office online/ Current Office clients for co-authoring.

[#6]

I hope that can be addressed.  While it might make sense to us as tech people, that will drive users nuts.

[#7]

Yeah, with their file UI updates coming to match SharePoint online, I really hope they look at just integrating directly into Teams opening in Office Online and just bypassing the whole separate Teams integration part. I think they do this because of the conversations on the right, but you can still have those when views website / office files using tabs, so should just be a similar experience. Having Teams edit, but then an option to edit in word online, etc is kind of redundant when they really kind of are the same thing.

[#8]

It could be a similar issue to Office365 documents in SharePoint getting locked. The issue there is that sometimes people will close files by clicking the red X in the top-right corner. The fix is always to open the file and close it again by clicking "File -> Close".

[#9]

Has anyone found or heard of ways around this? It make it difficult to use TEAMs effectively when creating new files in the TEAMs location you want them and then trying to edit them and having to wait. For example just trying to create a new Excel file then when you open it, it says it's locked and doesn't ever seem to notify you when it's freed up. I've reverted back to creating the file and saving it outside of TEAMs, editing it then just coping it up to TEAMs. Bit of a band-aid for now and would really like to know when this will be addressed.

Similar issue when creating WORD documents. I created some in TEAMs and realized I put them in the wrong folder. Since they were locked I couldn't move them or delete them. TEAMs says it does it but the file just stays there. When opening up the SP site is only when you actually get an error. 

[#10]

I can give you two suggestions but I do think what you are referring to likely to be a bug. We are opening a ticket with MSFT today, but others have already opened tickets about this and I am not sure where it went. Your idea of creating the docs outside of Teams, then uploading is the safest idea I am using at the moment. Here are my other ideas for you to try:

1. Clear the Office cache on your computer. The directory should be something like C:\Users\YOURNAME\AppData\Local\Microsoft\16.0\OfficeFileCache. Delete all of the files that begin with FSD & FSF.

2. Click your Windows key, type "Office Upload Center" then Settings --> Delete Cached Files

Another last resort would be to change registry setting for file locking (unfortunately I can't find the article for that at the moment). The only thing about this is that I am not sure if doing this actually disables your ability to check-in/check out documents or not. You would have to test that.

Matthew

[#11]

We do have the same Issue. Did anybody get Response to that from Microsoft due to a call?

[#12]

Hello guys,

I have an update. I opened a Microsoft call and we got an answer very fast. Microsoft is aware of this Problem. The short solution with one Client is to place him to the monthly update channel. This is not an option in our business environment, because the monthly update channel is just for consumer customers (as the informed me). I hope some of you will help this! Information!

What I want to know is if Microsoft is willing to fix this. Co-Authoring IMHO is a killerfeature and must also be available for business customers. Pleas give me information if and if yes, when it will be available for business customers.

Greetings Andre

[#13]

Hi! Thank you! Seems like a strange answer from MS though :\ Also Co-authoring is available for business costumers aswell..This problem is outside the scope of co-authoring 

[#14]

Hi,

secretly I know that co-authoring also works in the business environment. But if Microsoft Support tells me that I have to switch from semi annual over to monthly and that this more for consumer customers (I know it´s also for business) then I am wondering......

I just spoke to a colleague with a little bit more background information and he also confirmed me now that monthly is also for business customers. Therefore someone in our organisation has to decide if we switch to monthly or not ;).

But I am still wondering why Microsoft Support ist telling me such things.

[#15]

Well, everyone can make mistakes :) I doubt switching to monthly channel will help though..please let me know

Adam

[#16]

It already helped with one client. We already moved just one client to test the solution proposal. With the newest Office Update the problem has been blown away instantly.

[#17]

I´m very glad to hear!! Learning something is awsome :)

Adam

[#18]

Yes indeed, I am with you. Personally I am more a sharepoint / Onedrive / Teams guy than a client-OS guy and I learned a lot within this issue ;) .

[#19]

This is still a problem mid-September 2018.  Any updates on when a fix will be pushed to customers?

[#20]

@Andre Radtke would you mind sharing that MS case number?  I may open a case as well if we can't figure this one out on our own.