What does "locked for Shared Use" mean, exactly?

But please do repro this issue on your end and respond.  This is a very common issue with my users too.  There is not predictability.

I think  it's hard for level 1 support here to repro an intermittent bug like this. From the many reports about it, it's clear it's not related to check out. Most likely it's another symptom of Msft's lack of expertise in the cloud storage space -  I don't think they've figured out co-authoring and a whole host of other authentication issues properly yet. So this needs to be escalated to a higher level that can dig into the why  of why it might happen. Since that won't happen here, I suggest everyone who experiences the bug submits a service request so more competent engineers are made aware of the problem.

WebBrewers3

Your appeal for additional reports to promote this issue up the support chain makes sense

Can we not just apply our names to this call?

I found this thread simply putting a loose description in a search engine

The comments from previous users seem reasonable ie 'have encountered this issue & the clear cache option doesn't work'

This is indicative of an underlying issue that hasn't been tackled, 'it just went away' isn't a fix

I am in the same situation, trying to manipulate a given file using my own logic app tells me I have locked the file

Yet I can open & edit it without issue

Below is a paraphrase of the error msg

{

"status": 423,

"message": "The file http://SharepointPath/MASTER.xlsx is locked for shared use by MyUserName [membership].\r\nclientRequestId: 2f97739a-3b33-420a-b91****",

"source": "https:// SharepointPath/_api/web/GetFileByServerRelativePath(decodedUrl=@p)/$value?@p='%2fsites% SharepointPath%2fMASTER.xlsx'",

"errors": [

"-2147018894",

"Microsoft.SharePoint.SPFileLockException"

]

}

Is Microsoft going to chime in again or are they considering this thread closed?

This issue is a big problem for my users as well and would love to see MS look into this.  I'm creating a support ticket with Microsoft Support and will post any response from them here.

@Tisky - Original post issue has not 'gone', it times 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'm opening a support ticket with Microsoft and will post their response here.

@Tisky - Original post issue has not 'gone', it times 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'm opening a support ticket with Microsoft and will post their response here.

I am adding my voice as an admin on behalf of my users. This issue happens when they tend to work quickly with Word documents on SharePoint. I am also planning to open a support ticket, but would love to hear more about what's happened with yours @Pistolbrazil.