SharePoint Online - spreadsheet checked out to user shows as read only for that specified user

%3CLINGO-SUB%20id%3D%22lingo-sub-325813%22%20slang%3D%22en-US%22%3ESharePoint%20Online%20-%20spreadsheet%20checked%20out%20to%20user%20shows%20as%20read%20only%20for%20that%20specified%20user%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-325813%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EHi%20folks%20-%20We're%20experiencing%20an%20issue%20where%20an%20Excel%20spreadsheet%20checked%20out%20to%20a%20team%20member%20still%20remains%20in%20read%20only%20view%20and%20they%20are%20unable%20to%20edit%20it.%20If%20they%20try%20to%20edit%20it%2C%20they%20get%20a%20message%20telling%20them%3A%20%3CEM%3ECant%20Edit%20Workbook%20-%20%5Bteam%20member%20name%5D%20has%20the%20workbook%20locked.%20Ask%20them%20to%20close%20the%20file%20or%20check%20it%20in.%3C%2FEM%3E%20However...%20the%20team%20member%20name%20that%20shows%20in%20the%20error%20is%20the%20same%20team%20member%20who%20is%20trying%20to%20edit.%20So%2C%20the%20error%20is%20essentially%20telling%20them%20they%20can't%20edit%20something%20because%20they're%20the%20one%20who%20has%20it%20checked%20out.%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%3EThis%20is%20sporadic%2C%20thru%20testing%20we've%20determined%20this%20error%20occurs%2090%25%20of%20the%20time%20with%20Chrome%20and%20IE%2C%20I%20only%20received%20the%20error%20once%20when%20using%20MS%20Edge.%20This%20is%20happening%20for%20me%20(SP%20admin)%20as%20well%20as%20other%20team%20members.%20I%20have%20a%20list%20below%20of%20the%20various%20troubleshooting%20I've%20tried.%26nbsp%3B%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CDIV%3EIs%20this%20a%20bug%20related%20to%20spreadsheets%3F%3C%2FDIV%3E%3CDIV%3E...or%20do%20spreadsheets%20have%20to%20be%20checked%20out%20thru%20a%20different%20kind%20of%20process%20(seems%20unlikely%2C%20but%20I%20might%20as%20well%20ask)%3F%3C%2FDIV%3E%3CDIV%3E...any%20other%20ideas%20of%20why%20this%20is%20happening%3F%26nbsp%3B%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3EHere's%20what%20I've%20tried%20to%20diagnose%20the%20issue.%20I%20have%20not%20identified%20the%20root%20cause%20or%20fix.%3C%2FDIV%3E%3CDIV%3E%3CUL%3E%3CLI%3EI%20tested%20Word%20documents%20vs.%20spreadsheets.%20This%20only%20happens%20with%20spreadsheets.%20Word%20documents%20have%20never%20given%20us%20this%20error%20scenario.%3C%2FLI%3E%3CLI%3ETested%20on%20multiple%20sites%20within%20our%20Hub%20collection%26nbsp%3B%26nbsp%3B-%20same%20issue%20on%20all%20sites%3C%2FLI%3E%3CLI%3ETested%20on%20multiple%20libraries%20within%20a%20single%20site%20(on%20two%20separate%20sites%20w%2Fin%20the%20Hub)%20-%20same%20issue%3C%2FLI%3E%3CLI%3EI%20deleted%20and%20reloaded%20the%20spreadsheet%20and%20tested%20again%20on%20multiple%20libraries%20and%20multiple%20sites%20%26nbsp%3B-%20same%20issue%3C%2FLI%3E%3CLI%3EI%20created%20a%20net-new%20spreadsheet%2C%20uploaded%20that%20and%20tested%20to%20eliminate%20the%20possibility%20of%20corruption%20on%20the%20initial%20spreadsheet.%20I%20then%20retested%20using%20the%20net-new%20spreadsheet%20on%20multiple%20libraries%20and%20multiple%20sites.%20I%20went%20thru%20this%20process%20to%20create%20net-new%20and%20retest%20on%20multiple%20libraries%20and%20multiple%20sites%203%20times%20(creating%203%20net-new%20spreadsheets).%20All%20of%20the%20spreadsheets%20between%20all%20of%20the%20libraries%20and%20sites%20exhibit%20the%20same%20behavior.%26nbsp%3B%3C%2FLI%3E%3CUL%3E%3CLI%3EI%20also%20went%20thru%20this%20process%20with%20Word%20docs%20to%20confirm%20the%20error%20is%20specific%20to%20spreadsheets.%20Word%20docs%20worked%20fine%20every%20time.%3C%2FLI%3E%3C%2FUL%3E%3CLI%3EI%20rebuilt%20the%20library%20multiple%20times%20and%20then%20ran%20thru%20the%20tests%20again%20-%20same%20issue%20each%20time%3C%2FLI%3E%3CLI%3EI%20tested%20on%20multiple%20browsers%3CUL%3E%3CLI%3EChrome%20and%20IE%20both%20consistently%20have%20the%20issue%3C%2FLI%3E%3CLI%3EMS%20Edge%20-%20was%20only%20able%20to%20reproduce%20this%20error%20once%20when%20using%20this%20browser%3C%2FLI%3E%3CLI%3EI%20tested%20by%20checking%20out%20and%20then%20attempting%20to%20edit%20while%20in%20the%20same%20browser.%20eliminates%20the%20possibility%20that%20error%20is%20caused%20by%20checking%20out%20in%20one%20browser%20and%20attempting%20to%20edit%20using%20a%20different%20browser.%26nbsp%3B%3C%2FLI%3E%3C%2FUL%3E%3C%2FLI%3E%3CLI%3EI%20tested%20by%20opening%20the%20spreadsheet%20in%20the%20Excel%20web%20interface%20as%20well%20as%20opening%20directly%20in%20Excel%20to%20edit%20-%20same%20error%20regardless%20of%20what%20interface%20I%20used%20to%20attempt%20the%20edits%3C%2FLI%3E%3C%2FUL%3E%3CDIV%3EThank%20you%20for%20any%20suggestions!%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-325813%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-401493%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Online%20-%20spreadsheet%20checked%20out%20to%20user%20shows%20as%20read%20only%20for%20that%20specified%20user%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-401493%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F272245%22%20target%3D%22_blank%22%3E%40Kateraid%3C%2FA%3E%26nbsp%3Bdid%20this%20issue%20get%20fixed%20in%20your%20environment.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-329509%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Online%20-%20spreadsheet%20checked%20out%20to%20user%20shows%20as%20read%20only%20for%20that%20specified%20user%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-329509%22%20slang%3D%22en-US%22%3E%3CP%3EFor%20anyone%20keeping%20tabs%20on%20this%20issue%2C%20I%20now%20have%20a%20ticket%20open%20with%20Microsoft%20and%20they're%20doing%20research%20to%20identify%20a%20solution.%20I'll%20update%20this%20post%20when%20we%20come%20to%20a%20conclusion%20on%20this.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-326614%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Online%20-%20spreadsheet%20checked%20out%20to%20user%20shows%20as%20read%20only%20for%20that%20specified%20user%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-326614%22%20slang%3D%22en-US%22%3E%3CP%3EIt's%20Excel%20365%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-326403%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Online%20-%20spreadsheet%20checked%20out%20to%20user%20shows%20as%20read%20only%20for%20that%20specified%20user%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-326403%22%20slang%3D%22en-US%22%3EHi!%20Might%20be%20stupid%20but%20which%20excel%20Version%3F%20Is%20it%20excel%20365%20or%20previous%20version%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-548310%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Online%20-%20spreadsheet%20checked%20out%20to%20user%20shows%20as%20read%20only%20for%20that%20specified%20user%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-548310%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F240185%22%20target%3D%22_blank%22%3E%40Mahendra%20Ranaweera%3C%2FA%3E%26nbsp%3Bno%2C%20not%20yet.%20I've%20been%20working%20with%20Microsoft.%20They've%20been%20trying%20to%20pull%20logs%20of%20the%20issue%20occurring%2C%20but%20the%20log%20tool%20they're%20using%20keeps%20shutting%20down%20before%20we%20can%20complete%20the%20exercise%20on%20Chrome.%20Their%20log%20tool%20works%20on%20the%20other%20browsers%2C%20but%20the%20other%20browsers%20are%20sporadic%20with%20the%20issue%20and%20we%20didn't%20happen%20to%20experience%20the%20issue%20on%20the%20other%20browsers%20while%20they%20were%20running%20their%20log%20tool%2C%20therefore%20they've%20advised%20since%20we%20can't%20recreate%20the%20issue%20in%20the%20other%20browsers%20while%20their%20log%20tool%20is%20running%20they've%20concluded%20this%20is%20not%20an%20issue%20on%20non-Chrome%20browsers.%20I%20have%20screen%20captures%20of%20the%20issue%20occurring%2C%20and%20the%20MS%20team%20members%20have%20witnessed%20it%20happen%20while%20on%20screen%20share%20sessions%20with%20me%2C%20but%20because%20they%20can't%20capture%20a%20successful%20log%20they%20tell%20me%20their%20tech%20support%20team%20can't%20do%20any%20research%20on%20the%20issue.%20At%20this%20time%20they've%20told%20me%20to%20avoid%20Chrome%2C%20which%20is%20problematic%20for%20my%20company%20for%20a%20variety%20of%20other%20reasons.%20To%20say%20I'm%20disappointed%20is%20putting%20it%20lightly.%20After%20a%20few%20of%20my%20company's%20big%20projects%20wrap%20up%20%26amp%3B%20I%20have%20more%20availability%20from%20other%20team%20members%2C%20I'm%20planning%20to%20leverage%20another%20team%20member%20to%20see%20if%20they%20have%20better%20luck%20running%20the%20Microsoft%20log%20tool%20while%20recreating%20the%20issue%20in%20chrome%20so%20we%20can%20capture%20a%20successful%20log.%20I%20spent%20several%20hours%20over%20multiple%20ph%20calls%20with%20the%20MS%20tech%20support%20group%20and%20every%20time%20we%20tried%20this%20on%20my%20computer%20their%20log%20tool%20crashed.%20I'll%20update%20this%20post%20again%20when%20we%20get%20to%20that%20point.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Contributor

Hi folks - We're experiencing an issue where an Excel spreadsheet checked out to a team member still remains in read only view and they are unable to edit it. If they try to edit it, they get a message telling them: Cant Edit Workbook - [team member name] has the workbook locked. Ask them to close the file or check it in. However... the team member name that shows in the error is the same team member who is trying to edit. So, the error is essentially telling them they can't edit something because they're the one who has it checked out. This is sporadic, thru testing we've determined this error occurs 90% of the time with Chrome and IE, I only received the error once when using MS Edge. This is happening for me (SP admin) as well as other team members. I have a list below of the various troubleshooting I've tried.  

 

Is this a bug related to spreadsheets?
...or do spreadsheets have to be checked out thru a different kind of process (seems unlikely, but I might as well ask)?
...any other ideas of why this is happening? 
 
Here's what I've tried to diagnose the issue. I have not identified the root cause or fix.
  • I tested Word documents vs. spreadsheets. This only happens with spreadsheets. Word documents have never given us this error scenario.
  • Tested on multiple sites within our Hub collection  - same issue on all sites
  • Tested on multiple libraries within a single site (on two separate sites w/in the Hub) - same issue
  • I deleted and reloaded the spreadsheet and tested again on multiple libraries and multiple sites  - same issue
  • I created a net-new spreadsheet, uploaded that and tested to eliminate the possibility of corruption on the initial spreadsheet. I then retested using the net-new spreadsheet on multiple libraries and multiple sites. I went thru this process to create net-new and retest on multiple libraries and multiple sites 3 times (creating 3 net-new spreadsheets). All of the spreadsheets between all of the libraries and sites exhibit the same behavior. 
    • I also went thru this process with Word docs to confirm the error is specific to spreadsheets. Word docs worked fine every time.
  • I rebuilt the library multiple times and then ran thru the tests again - same issue each time
  • I tested on multiple browsers
    • Chrome and IE both consistently have the issue
    • MS Edge - was only able to reproduce this error once when using this browser
    • I tested by checking out and then attempting to edit while in the same browser. eliminates the possibility that error is caused by checking out in one browser and attempting to edit using a different browser. 
  • I tested by opening the spreadsheet in the Excel web interface as well as opening directly in Excel to edit - same error regardless of what interface I used to attempt the edits
Thank you for any suggestions!
 
5 Replies
Highlighted
Hi! Might be stupid but which excel Version? Is it excel 365 or previous version?
Highlighted
Highlighted

For anyone keeping tabs on this issue, I now have a ticket open with Microsoft and they're doing research to identify a solution. I'll update this post when we come to a conclusion on this.

Highlighted

@Kateraid did this issue get fixed in your environment.  

Highlighted

@Mahendra Ranaweera no, not yet. I've been working with Microsoft. They've been trying to pull logs of the issue occurring, but the log tool they're using keeps shutting down before we can complete the exercise on Chrome. Their log tool works on the other browsers, but the other browsers are sporadic with the issue and we didn't happen to experience the issue on the other browsers while they were running their log tool, therefore they've advised since we can't recreate the issue in the other browsers while their log tool is running they've concluded this is not an issue on non-Chrome browsers. I have screen captures of the issue occurring, and the MS team members have witnessed it happen while on screen share sessions with me, but because they can't capture a successful log they tell me their tech support team can't do any research on the issue. At this time they've told me to avoid Chrome, which is problematic for my company for a variety of other reasons. To say I'm disappointed is putting it lightly. After a few of my company's big projects wrap up & I have more availability from other team members, I'm planning to leverage another team member to see if they have better luck running the Microsoft log tool while recreating the issue in chrome so we can capture a successful log. I spent several hours over multiple ph calls with the MS tech support group and every time we tried this on my computer their log tool crashed. I'll update this post again when we get to that point.