Word 16.31 turning server files invisible

Hi Jeff,

Thanks for the reply. I checked the new video, it does shows a file for a second then it will disappear quickly. But this kind of file seems like a temporary file when Office tries to save as a copy, and when the save action completes, it then automatically removed so it looks like disappears. But it seems it doesn’t affect anything. In the video, I see you have saved Document/Document2/Document3.

Additionally, after unticking the “always save backup” option, something really has been changed. Before ticking that, you will see a real copy of file version saved locally. After disabling this option, it only shows a temporary file for a second.

However, this problem is not the very same issue in this thread. This original thread is that the real saved file can’t be visible on server. Considering they are in different scenarios, if you still have concern about the temporary file, I can split the question for you and we will continue involve more resource to check that behavior for you separately. We appreciate any reported problems from all of you.

Regards,

Rena

Thanks. Unfortunately, as it's inconsistent there is no way to record a file in the act of disappearing without running screen recorders full-time on all computer and wait. Best I can do is, when a file goes invisible, get you the file and/or whatever logs  you need if they'll help.

Thanks,

Jeff

I appear to have found a solution to the hidden file issue, however in addition to the files being hidden, I am also observing that saving the file immediately after being created fails.   Here are the steps to reproduce:

Running OS X 10.14.6

Word 16.32 (19120802)

1. Create a new file in word
2. Save file on network share
3. File will save, and disappear.
4. Make changes to the file, try and close word.
5. Word prompts to save, hit save.
6. Word appears to close, but then reopens.
7. Turns out it is impossible to save the changes to this file - the only way to exit is to tell Word to discard the changes - subsequently opening the file confirms only the initial save worked
8. Opening the file again, saving works normally.

Clearing the hidden flag does not fix the save issue... I noticed the com.apple.quarantine flag is set on the file, sure enough examining the logs I see that sandboxd has denied write access to create temporary files.

The behaviour occurs using both AFP and SMB protocols.

The sandboxd error that occurs when I initially create a file:

Violation:       deny(1) file-read-xattr /Volumes/Public/

The sandboxd errors that occur when trying to save that same file immediately afterwards:

Violation:       deny(1) file-write-create /Volumes/Public/Test.docx.sb-118eafb8-ncgFo2 

Violation:       deny(1) file-write-create /Volumes/Public/.~WRD0001 

When I first started testing, there was an additional sandboxd violation in the ~/Library/Group Containers/UB*.Office folder... running the following command in this folder appears to have fixed the hidden file issue:

xattr -r -d com.apple.quarantine ~/Library/Group\ Containers/UB*.Office

Hi jscooper22,

Thanks for the updates. Sorry about the late reply.

We have already involved the related resources for further investigation on this issue.

I understand that it's hard to record on an inconsistent issue, however, it will be a great help on the investigation if anyone who have the same issue could provide us with a video recording on this issue.

Your assistance is highly appreciated.

@Luc, Thanks for sharing us the detailed steps to reproduce this issue, we will forward this information to our related resources.

Regards,

Alex Chen