"Sorry, we couldn't open... "error opening excel file in Desktop app from Teams

%3CLINGO-SUB%20id%3D%22lingo-sub-3099013%22%20slang%3D%22en-US%22%3E%22Sorry%2C%20we%20couldn't%20open...%20%22error%20opening%20excel%20file%20in%20Desktop%20app%20from%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3099013%22%20slang%3D%22en-US%22%3E%3CP%3EHoping%20someone%20can%20help%20me%20resolve%20this%20one%20quickly!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20trying%20to%20open%20a%20file%20from%20Teams%20on%20the%20Desktop%20Excel%20App.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20can%20edit%20it%20no%20problem%20in%20Teams%20and%20in%20a%20browser%20%3CSTRONG%3EBUT%3C%2FSTRONG%3E%20I%20need%20to%20open%20in%20the%20App%20as%20it%20contains%20protected%20formulas.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20I%20try%20to%20open%20in%20the%20App%20I%20get%20the%20%3CSTRONG%3E%22Sorry%2C%20we%20couldn't%20open...%22%3C%2FSTRONG%3E%20error%20followed%20by%20the%20%22%3CSTRONG%3E*The%20file%20name%20or%20path%20does%20not%20exist.%20*The%20file%20is%20being%20used%20by%20another%20program.%20*the%20workbook%20you%20are%20trying%20to%20save%20has%20the%20same%20name%20as%20the%20currently%20open%20workbook.%22%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThere%20are%20multiple%20users%20who%20can%20view%20and%20edit%20the%20files%20from%20the%20Teams%20group%20-%20I've%20seen%20that%20this%20could%20be%20happening%20because%20another%20user%20is%20viewing%20it%20which%20is%20why%20I%20can't%20open%20or%20edit%20on%20the%20App%20but%20still%20able%20to%20edit%20online.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHow%20do%20I%2C%26nbsp%3B%20a)%20tell%20who%20has%20it%20open%2C%20and%2C%26nbsp%3B%20b)%20stop%20this%20from%20happening%20in%20the%20future%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EExcel%20is%20on%20the%20most%20recent%20update.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-3099013%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExcel%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3265774%22%20slang%3D%22en-US%22%3ERe%3A%20%22Sorry%2C%20we%20couldn't%20open...%20%22error%20opening%20excel%20file%20in%20Desktop%20app%20from%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3265774%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20the%20issue%20and%20I've%20tried%20several%20possible%20things%20-%20still%20unresolved.%3C%2FP%3E%3CP%3EI%20believe%20this%20is%20tied%20to%20%22file%20in%20use%20-%20another%20user%20editting%22%20but%20have%20not%20confirmed%20yet.%20There%20was%20a%20similar%20problem%20back%20in%202016%20timeframe%20that%20was%20resolved%20with%20a%20patch%20-%20this%20might%20be%20something%20that%20has%20been%20reintroduced.%20Like%20you%20this%20has%20only%20appeared%20recently%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Hoping someone can help me resolve this one quickly!

 

I'm trying to open a file from Teams on the Desktop Excel App.

 

I can edit it no problem in Teams and in a browser BUT I need to open in the App as it contains protected formulas.

 

When I try to open in the App I get the "Sorry, we couldn't open..." error followed by the "*The file name or path does not exist. *The file is being used by another program. *the workbook you are trying to save has the same name as the currently open workbook."

 

There are multiple users who can view and edit the files from the Teams group - I've seen that this could be happening because another user is viewing it which is why I can't open or edit on the App but still able to edit online.

 

How do I,  a) tell who has it open, and,  b) stop this from happening in the future?

 

Excel is on the most recent update.

2 Replies

I have the issue and I've tried several possible things - still unresolved.

I believe this is tied to "file in use - another user editting" but have not confirmed yet. There was a similar problem back in 2016 timeframe that was resolved with a patch - this might be something that has been reintroduced. Like you this has only appeared recently

I found a resolution to my issue:
found the issue - tied to PCMover "cloning"
Have to clear OfficeFileCache - in my users case the version was 16.0 and not 15.0

Close all Office applications.
Navigate to: %systemDrive%\Users\%userprofile%\AppData\Local\Microsoft\Office\15.0\OfficeFileCache\
Clear all the files in this directory [It’s okay, if you cannot delete one or two files]