The shares are Guest enabled, no password needed. I'm now trying to identify how much of a risk it is to OSX users in disabling 'Allow Background Saves' and is it better to force them to save locally, then drag to the server.įreeNAS 11.1 with a pretty standard config. Disabling SMBv2 seems to resolve the issue, but is not So pending your setup, likely you do NOT have CA RHA on your servers, but you may have backup software, settings in MS FSRM file screens, etc that could potentially have the same effect. Other programs do not seem to have this issue OR utilize a different 'temp' naming schema. With SMBv1 being such a security issue now, we had to figure out SMBv2 and discovered its not the protocol, but the apps using the protocol. I've been using CA RHA to replicate data for some time and previously we had SMBv2 intentionally disabled as we though this was the culprit, but after doing packet captures, it seems Office apps treat saving to remote source differently if connected via _xxxx file attempting to be created,īut unlike Windows version of Office, Mac versions time out is much faster and so the save is canceled almost immediately. DS_Store files because of the garbage they generate (it starts to add up after terabytes of data) and I have a feeling the same thing is going on here, in the 'temp folder' there is a. tmp files as I don't want to 'sync/replicate' them I had them explicitly excluded. Our sync software was causing long delays as it was interfering with these. tmp file in the same directory when saving. We had a similar problem with Windows Office saves as Office apps, ONLY WHEN USING SMBv2, create a I have a feeling it has to do with our Sync software (CA RHA). Our issue was worse as users could not save directly to the server at all. Where would we poor supporters be if we had not the backup of knowledgeable peopleįor us it was the setting: Word | Preferences | Save | Allow Background Saves This said, I of course appreciate your help very much. ' I am not sure why your Word for Mac 2016 create the temporary file in a new folder.' - The answer lies in the code! There mustīe the ifs and elses that test the conditions and decide to put the folder where we find them.

I also wonder how other software could interfere? Preventing Office from deleting the folder? Or causing Office to create the folder in the wrong place or with he wrong permissions? Clearly as employees of the company that created the program, you shouldīe able to shed some more light on the issue and give some hints on what kind of 'background process' one has to think of. We too have the problem but very sporadic and we don't know how to repropduce the error. But the OP has never come back to report if he found the culprit. I don't understand why this has been marked as an answer.

Oneshot mac torrent