Forum Discussion
Solved
File locking issue
We are running an on-prem Sharepoint 2013 standard edition and we recently upgraded our users to O365 Office 2016. Soon after the Office 2016 upgrade, many users are reporting that they are having problem with saving files back to Sharepoint after editing them. When a user tries to save a document after editing, an "Upload Failed" error message gets triggered - "This file is checked out by another user" - the error message also shows a user ID that essentially is the user that is trying to save the file back to Sharepoint. It seems that somewhere in between, the session was lost and Sharepoint cannot recognize that the user who is trying to save the file is the same user that started editing (or checked out) the file. The frequency of this issue is intermittent but seems to happen more with power users that have many MS Office document opened at the same time. We have been in contact with Microsoft team for months, but so far no resolution.
Has anyone experienced this issue and care to share the resolution?
Please find below the problem, cause and resolution provided by Microsoft..
Note : - we do not use check in - check out in our environment...
Hope this helps
Stewart
PROBLEM
================================
there are some users report of upload failed issue, sometimes, it can be completed by retry, some time, it will always failed.
Also many different symptoms when saving on both office and SP side which point to lock issue.
CAUSE & RESOLUTION
=================================
CAUSE: web client service add lock on the file
RESOLUTION: since no need for checkout/checkin, add below registry to disable the lock function of web client service but keep all other functions like explorer view support
HKLM\SYSTEM\CurrentControlSet\Services\WebClient\Parameters\SupportLocking=0
ADDITIONAL INFORMATION AND RECOMMENDATIONS
================================================
Registry to disable lock function when web client service is started:
- Start webclient service on user side
- Find registry: HKLM\SYSTEM\CurrentControlSet\Services\WebClient\Parameters on their machines.
- Find value: SupportLocking(if no, please add), set its value to 0, want to just disable lock feature.
If you use a tool to migrate content to Office 365 like Sharegate, it will transfer the document library settings that you had in your on-premises site, one of the key settings is require check in/out as this disables multi-user editing and OneDrive sync shows all the files as locked. If you turn this off, it will make editing in OneDrive sync work but won't check back in existing files, you will need to get users to check these in or take ownership of the files and check them all in.
If you have a required column that is not set by the user when they add the file, it will mark it as requiring attention and I have noticed that this can also put the file in a checked out state.
- If you open a document that was missing data, it will be read only even if it was check out to you. If you set the value in the SharePoint list to remove the "Required info" it still remain checked out and the user needs to check it in to edit it.
The server properties also moved from the header in Word to the File menu under properties so not obvious to users.
I would recommend setting a default on required meta data if you can and educate users on setting properties in Office Documents.
See if they are facing issue with Excel files. We had same issue before and when we investigated.
Our users were opening excel file in Office Client (thick client) and expecting coauthoring which is not supported in excel.
Where are word supports in both webapps and thick client.
- Thanks Anji, we will look into it.
I have the same issue amd again with SharePoint 2013 and after upgrade of my Office 365 to 2016 version.
I'm losing data so please advise a solution asap.
Chris
