New Documents locked by web edit when using Chrome

%3CLINGO-SUB%20id%3D%22lingo-sub-206820%22%20slang%3D%22en-US%22%3ENew%20Documents%20locked%20by%20web%20edit%20when%20using%20Chrome%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-206820%22%20slang%3D%22en-US%22%3E%3CP%3EHi%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe've%20recently%20noticed%20an%20issue%20with%20documents%20being%20left%20locked%20after%20opening%20in%20the%20web%20edit%20of%20Sharepoint%20Online.%20It%20only%20seems%20to%20happen%20in%20%3CSTRONG%3EChrome%3C%2FSTRONG%3E%20and%20i'm%20fairly%20sure%20it's%20a%20recent%20issue%20(perhaps%20since%20the%20newer%2C%20richer%20web-edit%20became%20available).%20I%20was%20wondering%20if%20others%20can%20re-produce%20this%20in%20their%20tenants%3F%20I%20realise%20there%20are%20all%20sorts%20of%20tips%20of%20unlocking%20documents%20and%20waiting%20for%20locks%20to%20expire%20but%20this%20seems%20to%20be%20a%20consistent%20lock%20placed%20on%20every%20new%20document%2C%20and%20a%20very%20simple%20scenario.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt's%20very%20easy%20for%20us%20to%20re-produce%20and%20it%20happens%20in%20multiple%20tenants.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E1.%20If%20you%20go%20to%20New%20%26gt%3B%20Document.%26nbsp%3BIt%20automatically%20opens%20in%20Word%20web%20edit.%3C%2FP%3E%3CP%3E2.%20Enter%20some%20content%3C%2FP%3E%3CP%3E3.%20Click%20on%20the%20document%20library%20link%20at%20the%20top%20bar%20to%20exit%20the%20web%20edit%3C%2FP%3E%3CP%3E4.%20Open%20the%20properties%20pane%20for%20the%20document%20and%20try%20to%20change%20any%20of%20the%20properties.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20receive%20this%3A%3C%2FP%3E%3CP%3E%3CSPAN%3EThe%20file%20is%20locked%20for%20shared%20use%20by%26nbsp%3Bxxxxx%40xxx.onmicrosoft.com%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EAs%20you%20can%20see%20this%20is%20a%20simple%20scenario%2C%20involving%20a%20brand%20new%20document%2C%20single%20user%20and%20web%20edit%20only.%20Before%20I%20go%20through%20the%20long%20process%20of%20logging%20a%20support%20case%20was%20interested%20to%20see%20if%20it's%20just%20me.%26nbsp%3BThe%20web%20edit%20version%20we're%20seeing%20is%26nbsp%3B16.0.10319.33700.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThanks%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EAndy%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-206820%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EFiles%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EUsage%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-207357%22%20slang%3D%22en-US%22%3ERe%3A%20New%20Documents%20locked%20by%20web%20edit%20when%20using%20Chrome%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-207357%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20main%20issue%20i'm%20facing%20is%20via%20office%20online%20edit%20only%2C%20and%20editing%20of%20properties%20via%20property%20panel%20after%20creating%20a%20document.%20It%20only%20seems%20to%20be%20blocking%20the%20properties%20panel.%20The%20user%20can%20open%20the%20document%20again%20in%20web%20edit%20or%20desktop%20client%20and%20continue%20editing.%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20seen%20other%20locking%20issues%20before%20via%20desktop%20client%20but%20the%20reason%20this%20one%20is%20so%20frustrating%20is%20the%20fact%20it's%20such%20a%20basic%20repeatable%20scenario%20that%20simply%20blocks%20the%20user%20proceeding%20when%20creating%20a%20document%20every%20single%20time.%20All%20the%20user%20is%20doing%20is%20creating%20a%20brand%20new%20document%20and%20then%20trying%20to%20fill%20in%20it's%20properties%20and%20it's%20preventing%20them%20doing%20this.%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20issue%20becomes%20compounded%20further%20if%20you%20have%20any%20required%20fields%20in%20the%20document%20library.%20In%20this%20scenario%20it%20does%20this%20(again%20Chrome%20only%20it%20seems)%3A%3CBR%20%2F%3E%3CBR%20%2F%3E1.%20User%20creates%20new%20document%20via%20New%20%26gt%3B%20Document%3CBR%20%2F%3E2.%20User%20is%20automatically%20presented%20with%20web%20edit%20where%20they%20enter%20some%20content%3CBR%20%2F%3E3.%20User%20exits%20web%20edit%20and%20is%20back%20at%20the%20document%20library%20where%20the%20document%20has%20required%20fields%20and%20is%20therefore%20checked%20out%20until%20they%20fill%20them%20in%2C%3CBR%20%2F%3E4.%20User%20tries%20to%20fill%20in%20required%20fields%20via%20properties%20panel%20but%20is%20blocked%20in%20doing%20so%20as%20it%20says%20document%20is%20locked%20by%20themselves.%3CBR%20%2F%3E%3CBR%20%2F%3ESo%20they%20end%20up%20completely%20stuck%20and%20unable%20to%20check%20in%20as%20there%20are%20required%20fields%2C%20but%20unable%20to%20fill%20them%20in%20as%20it%20says%20they%20have%20it%20locked.%3CBR%20%2F%3E%3CBR%20%2F%3EAgain%20I%20know%20people%20have%20had%20locking%20issues%20but%20as%20the%20ones%20i've%20described%20are%20such%20simple%2C%20repeatable%20scenarios%20can%20anyone%20confirm%20that%20going%20though%20the%20same%20steps%20in%20Chrome%20that%20they're%20experiencing%20the%20same%20thing%3F%20With%20the%20particular%20scenario%20described%20above%20I'm%20surprised%20it's%20not%20causing%20more%20widespread%20complaints%20as%20it's%20blocking%20a%20number%20of%20our%20users%20even%20getting%20their%20initial%20document%20created.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-207335%22%20slang%3D%22en-US%22%3ERE%3A%20New%20Documents%20locked%20by%20web%20edit%20when%20using%20Chrome%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-207335%22%20slang%3D%22en-US%22%3EHave%20seen%20this%20happening%20lately%20aswell.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-207329%22%20slang%3D%22en-US%22%3ERe%3A%20New%20Documents%20locked%20by%20web%20edit%20when%20using%20Chrome%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-207329%22%20slang%3D%22en-US%22%3E%3CP%3EFor%20me%20its%20v67%20Chrome%2C%20Office%20365%20online%20and%20sometimes%20Excel%201806%20Build%2010228.20062%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-206965%22%20slang%3D%22en-US%22%3ERe%3A%20New%20Documents%20locked%20by%20web%20edit%20when%20using%20Chrome%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-206965%22%20slang%3D%22en-US%22%3E%3CP%3EFollowing.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIs%20this%20only%20happening%20in%20OOS%20(Office%20Online%20Server)%20or%20are%20you%20experiencing%20this%20on%20the%20client%20as%20well%3F%26nbsp%3B%20If%20so%20what%20version%20(s)%20of%20the%20client.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIs%20it%20just%20locking%20the%20properties%20pane%2C%20or%20is%20it%20also%20locking%20a%20specific%20paragraph%20you%20were%20editing%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-206838%22%20slang%3D%22en-US%22%3ERe%3A%20New%20Documents%20locked%20by%20web%20edit%20when%20using%20Chrome%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-206838%22%20slang%3D%22en-US%22%3EI%20mean%20locked%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-206837%22%20slang%3D%22en-US%22%3ERe%3A%20New%20Documents%20locked%20by%20web%20edit%20when%20using%20Chrome%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-206837%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20having%20this%20issue%20too%20...%20particularly%20annoying%20in%20that%20is%20causes%20Flow%26nbsp%3Bworkflow%20to%20fail%20because%20the%20document%20is%20open.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-206828%22%20slang%3D%22en-US%22%3ERe%3A%20New%20Documents%20locked%20by%20web%20edit%20when%20using%20Chrome%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-206828%22%20slang%3D%22en-US%22%3EHappens%20in%20Teams%20too%20but%20worse%20due%20to%20cache%2C%20but%20it's%20been%20happening%2C%20if%20you%20want%20to%20take%20a%20stab%20at%20support%20let%20us%20know%20the%20outcome%20but%20your%20not%20the%20only%20one%20experiencing%20it%20%3A).%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1901277%22%20slang%3D%22en-US%22%3ERe%3A%20New%20Documents%20locked%20by%20web%20edit%20when%20using%20Chrome%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1901277%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20experience%20the%20same%20problem.%20I%20see%20this%20is%20an%20old%20post%20and%20I%20looking%20for%20the%20solution%20...%20anyone%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Hi

 

We've recently noticed an issue with documents being left locked after opening in the web edit of Sharepoint Online. It only seems to happen in Chrome and i'm fairly sure it's a recent issue (perhaps since the newer, richer web-edit became available). I was wondering if others can re-produce this in their tenants? I realise there are all sorts of tips of unlocking documents and waiting for locks to expire but this seems to be a consistent lock placed on every new document, and a very simple scenario.

 

It's very easy for us to re-produce and it happens in multiple tenants. 

 

1. If you go to New > Document. It automatically opens in Word web edit.

2. Enter some content

3. Click on the document library link at the top bar to exit the web edit

4. Open the properties pane for the document and try to change any of the properties.

 

You receive this:

The file is locked for shared use by xxxxx@xxx.onmicrosoft.com

 

As you can see this is a simple scenario, involving a brand new document, single user and web edit only. Before I go through the long process of logging a support case was interested to see if it's just me. The web edit version we're seeing is 16.0.10319.33700.

 

Thanks

Andy

8 Replies
Happens in Teams too but worse due to cache, but it's been happening, if you want to take a stab at support let us know the outcome but your not the only one experiencing it :).

We are having this issue too ... particularly annoying in that is causes Flow workflow to fail because the document is open. 

I mean locked

Following.

 

Is this only happening in OOS (Office Online Server) or are you experiencing this on the client as well?  If so what version (s) of the client.

 

Is it just locking the properties pane, or is it also locking a specific paragraph you were editing?

For me its v67 Chrome, Office 365 online and sometimes Excel 1806 Build 10228.20062

 

Have seen this happening lately aswell.

The main issue i'm facing is via office online edit only, and editing of properties via property panel after creating a document. It only seems to be blocking the properties panel. The user can open the document again in web edit or desktop client and continue editing.

We've seen other locking issues before via desktop client but the reason this one is so frustrating is the fact it's such a basic repeatable scenario that simply blocks the user proceeding when creating a document every single time. All the user is doing is creating a brand new document and then trying to fill in it's properties and it's preventing them doing this.

The issue becomes compounded further if you have any required fields in the document library. In this scenario it does this (again Chrome only it seems):

1. User creates new document via New > Document
2. User is automatically presented with web edit where they enter some content
3. User exits web edit and is back at the document library where the document has required fields and is therefore checked out until they fill them in,
4. User tries to fill in required fields via properties panel but is blocked in doing so as it says document is locked by themselves.

So they end up completely stuck and unable to check in as there are required fields, but unable to fill them in as it says they have it locked.

Again I know people have had locking issues but as the ones i've described are such simple, repeatable scenarios can anyone confirm that going though the same steps in Chrome that they're experiencing the same thing? With the particular scenario described above I'm surprised it's not causing more widespread complaints as it's blocking a number of our users even getting their initial document created.

We experience the same problem. I see this is an old post and I looking for the solution ... anyone?