Office Cache Causing Sharepoint Issue With Multiple RD Servers

Evan_001 1 Reputation point
2021-06-17T20:30:35.9+00:00

Good morning,

We use multiple Remote Desktop servers along with Teams, Sharepoint, and Office products. What we have noticed is that when a user is logged into ServerA and opens an Office file (word, excel, etc) from the Sharepoint site, the cache is populated with temporary files as normal. This user profile that includes that cache will follow the user if they were to log off of ServerA and log into ServerB. Now when they attempt to open the document from the SP site, they are given an error that says "Sorry, we couldn't open 'http://sharepoint/website/path/filename.docx'." We have been clearing the Office cache for users when they encounter this issue, but is there any way to actually solve this issue without having to "work around" by wiping the cache on log off/log in?

Thank you,

Microsoft 365 and Office SharePoint Server For business
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Elsie Lu_MSFT 9,801 Reputation points
    2021-06-18T07:20:31.58+00:00

    Hi @Evan_001 , welcome to Q&A forum!

    Per my research, currently clearing the cache is the only work around. And you could also open a support ticket for more help if urgent.

    Similar posts for your reference:
    Sorry we couldn't open document Word, Excel
    Error opening office documents from SharePoint 2013
    Error: Sorry, we couldn't open 'filepath/filename' received


    If the answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


  2. Eirik Vesterhus 1 Reputation point
    2021-08-19T09:11:36.127+00:00

    Would be nice with an explanation from Microsoft here. This is new behaviour. It seems $env:LOCALAPPDATA\Microsoft\Office\16.0\OfficeFileCache do not support roaming anymore or there are issues with creating the .C4-file.

    Take a look here. This is from procmon at time of the error:

    124580-image.png

    Excel tries to create the cache file and apparently it is a success.
    The actual folder and file never gets touched, though.

    124566-image.png

    Notice the timestamp in both screenshots.

    This should do the trick of you want to clear the cache at logon with a powershell script.

    $folders = get-childitem $env:LOCALAPPDATA\Microsoft\Office\16.0\ | where Name -like OfficeFileCache*
    foreach($folder in $folders){
    Remove-Item -Path $folder.FullName -Recurse -Force
    }


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.