Co-Authoring breaks for Word Docs uploaded to SharePoint 2016, but works if created in site

%3CLINGO-SUB%20id%3D%22lingo-sub-766004%22%20slang%3D%22en-US%22%3ECo-Authoring%20breaks%20for%20Word%20Docs%20uploaded%20to%20SharePoint%202016%2C%20but%20works%20if%20created%20in%20site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-766004%22%20slang%3D%22en-US%22%3E%3CP%3ESummary%3A%20Word%20docs%20uploaded%20to%20our%20internally%20hosted%20SharePoint%202016%20site%20can%20never%20be%20co-authored%2C%20but%20if%20I%20create%2Fstart%20the%20Word%20doc%20directly%20in%20SharePoint%2C%20then%20it%20can%20be%20co-authored.%20Why%20is%20that%2C%20and%20how%20do%20I%20fix%20it%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EToday%20if%20I%20create%20a%20Word%20doc%20on%20my%20Windows%2010%20desktop%20with%20Word%20(Office%20Desktop%20Professional%20Plus%202016)%20and%20then%20upload%20it%20to%20a%20SharePoint%202016%20site%2C%20if%20I%20have%20the%20doc%20open%2C%20other%20users%20get%20an%20error%20message%20saying%20%22UPLOAD%20FAILED%20This%20file%20is%20locked%20for%20editing%20by%20%5BNAME%5D.%22%20%3CSAVE%20button%3D%22%22%3E%20(Side%20note%3A%20other%20person%20was%20using%20latest%20Mac%20version%20of%20Office)%3C%2FSAVE%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20I%20got%20to%20the%20same%20library%2C%20and%20click%20%22New%20%26gt%3B%26gt%3B%20Word%20Document%22%20and%20copy%20the%20same%20content%20into%20the%20document%2C%20save%20it%20and%20share%20it%2C%20others%20can%20now%20begin%20co-authoring.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20reproduced%20the%20issue%20with%20multiple%20users%2C%20multiple%20SharePoint%20sites%20(all%20same%20SharePoint%20server).%20Why%20does%20the%20creation%20location%20of%20the%20document%20make%20a%20difference%20for%20co-authoring%3F%20Is%20there%20a%20fix%20for%20this%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-766004%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E2016%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EPermissions%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-767847%22%20slang%3D%22en-US%22%3ERe%3A%20Co-Authoring%20breaks%20for%20Word%20Docs%20uploaded%20to%20SharePoint%202016%2C%20but%20works%20if%20created%20in%20site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-767847%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F379569%22%20target%3D%22_blank%22%3E%40stephenakearns%3C%2FA%3EMy%20guess%20is%20that%20it%20probably%20has%20to%20do%20with%20the%20version%20of%20Office%20that%20you%20are%20using%20on%20your%20desktop.%20A%20lot%20of%20our%20users%20are%20still%20on%20Win%207%2FOffice%202013%20and%20the%20only%20way%20they%20can%20co-author%20is%20to%20open%20the%20document%20in%20the%20browser.%20I%20believe%20Office%202016%20allows%20co-authoring%20in%20the%20desktop%20app.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20that's%20the%20case%2C%20then%20just%20have%20users%20open%20the%20doc%20in%20the%20browser%20to%20allow%20co-authoring%2C%20open%20in%20the%20desktop%20app%20to%20prevent%20it.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Visitor

Summary: Word docs uploaded to our internally hosted SharePoint 2016 site can never be co-authored, but if I create/start the Word doc directly in SharePoint, then it can be co-authored. Why is that, and how do I fix it? 

 

Today if I create a Word doc on my Windows 10 desktop with Word (Office Desktop Professional Plus 2016) and then upload it to a SharePoint 2016 site, if I have the doc open, other users get an error message saying "UPLOAD FAILED This file is locked for editing by [NAME]." <SAVE BUTTON> (Side note: other person was using latest Mac version of Office)

 

If I got to the same library, and click "New >> Word Document" and copy the same content into the document, save it and share it, others can now begin co-authoring. 

 

I've reproduced the issue with multiple users, multiple SharePoint sites (all same SharePoint server). Why does the creation location of the document make a difference for co-authoring? Is there a fix for this? 

1 Reply
Highlighted

@stephenakearnsMy guess is that it probably has to do with the version of Office that you are using on your desktop. A lot of our users are still on Win 7/Office 2013 and the only way they can co-author is to open the document in the browser. I believe Office 2016 allows co-authoring in the desktop app.

 

If that's the case, then just have users open the doc in the browser to allow co-authoring, open in the desktop app to prevent it.