MS word 2016 TMP filles in folders being created on network shares

Stubakka
Contributor II

Hello All, I recently have come across an issue where a user is working in Word 2016 and creates a document on their iMac. All goes well, they upload it to a network Share (that many users use daily) and recently , if she reopens that file, or any word file from any share, its leaving behind a folder with the Files name, then random numbers and letters behind it. inside this folder is a TMP file with the name of the folder that when attempting to erase it. It won't allow it. The network share is being connected to via SMB, but using CIFS also resulted in the same issue. Has anyone else dealt with this?

6eb5768b3cbe46e1bf36ccb0a8559c73
5547320fbd5b40158b70d02d530d7a6c

3 REPLIES 3

Mhomar
Contributor

I too have this going on via SMB, I have not been able to identify a solution for it either. It was suggested on the MacAdmins Office Slack channel that closing the file after saving would fix it. However, my experience with that fix has been very hit or miss. We could use some help mitigating this Feature ;-)

Stubakka
Contributor II

Good to know Im not alone.

talkingmoose
Honored Contributor II

I suggest returning to the #microsoft-office channel in Slack and reporting these issues to Erik Schwiebert (@shwieb there). He's been investigating issues like this.

According to him, the Office applications make a request to the operating system and the OS itself is interacting with your file shares. Office has no control over what's happening here. And while you may be using the SMB protocol for connectivity, more than likely you're not connecting to a Windows server—you're connecting to a network storage appliance. Manufacturers of these appliances will tweak the networking stacks of whatever flavor of OS they're using. Some do this well. Some don't. It's the server that determines what will happen, what it will display and how it will behave.

So, from your network storage team, collect information about the storage device, its manufacturer and its OS and version. Report that to schwieb. He's been tweaking Office for the various behaviors folks are seeing to help mitigate these issues.