SharePoint locking issue

[isdataninja]

We have multiple users experiencing intermittent SharePoint locking issue. (on-prem)

Users working away with their documents then gets locked out saying the document is locked out by themselves. 

Already created a case with micrsoft and they have been unable to help. This is now holding up our SharePoint Online/O365 deployment. 

Tried these reg fixes but issue persists. 

• Disable "Long Term Caching" reg fix
• http://www.networksteve.com/exchange/topic.php/Office_2010_Microsoft_Office_Upload_Center_configure_...
• Subkey:HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\FileIO
• Key:"DisableLongTermCaching"=dword:00000001

• EnableRealtimeChannel reg fix
• https://support.microsoft.com/en-us/kb/3100925
• Subkey:HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\FileIO
• Key:"EnableRealtimeChannel"=dword:00000000

 Anybody else experiencing this? 

[#2]

I have seen this sometimes, but the problem is normally solved in some minutes

[#3]

I've seen this when workflows/event receivers are kicking in and updating the document properties.

[#4]

---

@Juan Carlos González Martín wrote:
I have seen this sometimes, but the problem is normally solved in some minutes

---

i believe lockout time is 10min? if the user waits long enough, the file will be unlocked.. but the issue still exists. 

[#5]

---

@Pieter Veenstra wrote:

I've seen this when workflows/event receivers are kicking in and updating the document properties.

---

yep, seen it on modifying document properties as well. 

[#6]

anybody? 

[#7]

Which version of Office do you use? and can you replicate the same issue with othe versions of office?

[#8]

office 365. users only started reporting after they were migrated over. it's even got to the point where users would have to revert back to 2010. 

---

@Deleted wrote:

Which version of Office do you use? and can you replicate the same issue with othe versions of office?

[#9]

Any update on this - were you able to resolve the issue?

[#10]

Hello. Yes we did. It ended up being our Riverbed wan accelerator. Had to configure it to bypass SharePoint traffic.