This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(35.2, 31%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETS%3C/text%3E%3C/svg%3E)
I have a Microsoft Server 2019 Standard with MS Office installed. I also have a Linux server that shares each user's ~/windows/ directory through Samba with their Windows account when they're logged in (as a network drive). However, when they attempt to save an .xslx file located in the said directory, the following error appears:
Microsoft Excel cannot access the file 'D:\\<username>\AppData\Local\Microsoft\Windows\INetCache\Content.MSO\53B87310'.
There are several possible reasons:
- 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.
None of the above is true - the file exists, doesn't seem to be used (since it's a temporary file created by Excel) and there is no Workbook name collision.
Saving the file locally (to Desktop, for example) works without any issues. Saving a file as Administrator to the network drive works without any issues too, which hints at problems with privileges.
Any help would be much appreciated!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I'd check the user has read, write, modify, delete permissions on the location. Check both the share and underlying NTFS effective permissions.
--please don't forget to upvote and Accept as answer if the reply is helpful--
It shows me the following:
This should mean that everyone has full access, right?
I'd check both the share and underlying NTFS permissions and for the problem user.
--please don't forget to upvote and Accept as answer if the reply is helpful--
The user in question is this one:
NIKAM\tom is, however, the name of the Linux server + user. The Windows server is called KLIKAM (again with user tom). Should there then also be a KLIKAM\tom user with appropriate permissions?
That could be it, these sort of things can be tricky in a workgroup setting.
--please don't forget to upvote and Accept as answer if the reply is helpful--
Just checking if there's any progress or updates?
--please don't forget to upvote and Accept as answer if the reply is helpful--