Word 2016 co-authoring fails when file is stored on SharePoint 2013

Symptoms
When you use Microsoft Word 2016 Co-authoring feature in an on-premises instance of Microsoft SharePoint 2013, you receive one of the following error messages:

  • FILE IN USE This file is locked for editing by another user.

  • UPLOAD FAILED This file is locked for editing by <user>.


  • Upload Failed: Locked by another user
    Your changes were saved but could not be uploaded because this file is locked for editing by <user>. You will be notified when this file becomes available. Click resolve for options.



    Note This message is displayed in the Backstage area.
Resolution
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

To prevent Word 2016 from locking files that are stored on SharePoint 2013, add the EnableRealtimeChannel registry key.

Note This key disables the real-time Co-authoring feature in Word 2016. This feature is available only for processing documents that are stored in SharePoint Online and OneDrive. Real-time Co-authoring is not available in SharePoint 2013 or SharePoint 2010.

Add the following registry key, and then restart Word:

Subkey:

HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\FileIO

Key:

"EnableRealtimeChannel"=dword:00000000
More information
Files that are stored in SharePoint 2013 and that were opened by Word 2016 before the registry fix in the "Resolution" section is applied may continue to be locked by other users even after the key is applied. This is because of document information that has been stored locally.

If files continue to be locked after you apply the registry fix, you may have to rename or delete the OfficeFilecache folder to reset the sync state of these documents on your computer.

Important This procedure will cause you to lose all local changes. Therefore, we recommend that you save a local copy of all pending files before you perform these steps.

  1. Check for pending files. To do this, click the Office Upload Center icon in the notification area of the Task Bar, as shown in the following screen shot.


  2. Wipe the entire Office file cache. To do this, follow these steps:

    1. Close all Office programs.
    2. In the notification area, right-click the OneDrive icon, and then click Exit.
    3. Press Ctrl+Alt+Del to start Task Manager.
    4. On the Processes tab, select all running processes that have any of the following image names, and then click End Process:

      • MsoSync
      • CsiSyncClient
      • MsoUC
      • Groove
      • Lync
      • OneDrive
    5. In Windows Explorer, locate the following folder:

      %SystemDrive%\Users\%UserName%\AppData\Local\Microsoft\Office\16.0\OfficeFileCache
    6. Rename the OfficeCacheFolder folder. For example, rename it as OfficeCacheFolder_old.

      Note By renaming the folder, you preserve document data. However, you can also delete the folder to recover disk space if the folder is extremely large. Both methods reset the document sync state.
    7. Restart OneDrive and other Office programs.
Status
This problem is scheduled to be fixed in build 4229.1032 and later versions of Office 365. This problem is also scheduled to be fixed in the October update for Office 2016.

Microsoft is researching this problem in Microsoft Word 2016 and will post more information in this article when the information becomes available.
Properties

Article ID: 3100925 - Last Review: 10/09/2015 23:19:00 - Revision: 1.0

Word 2016

  • kbgraphxlink KB3100925
Feedback