Saving PDFs from win10/Office2016 adds null bytes after %%EOF

[hi-ko]

We see a very strange behavior when saving Word docs from Office 2016 as PDF to an Alfresco CIFS share using SMB_v2 share.
The file get's added thousands of NULL byte characters after the last %%EOF tag and makes the doc unsable for Acrobat.
We don't see this effect when saving to other CIFS servers. Could it be that there is an issue with the buffer handling?

I guess a tcpdump / wireshark is the only way to find out what's going on?
Thanks for every hint - I will evaluate further details ...

[FileSysOrg]

I’ll see if I can reproduce this locally, if not then I may need a network packet trace to see what is happening.

[FileSysOrg]

I've been trying to reproduce this issue using fileServersNG-v61 but it seems to work ok here. I checked the content store folder and the file is the correct size. The exported file is readable by Acrobat Reader.

I'm using a Win10 client with Office 2016, using the File->Export option to generate the PDF in a user folder on the Alfresco mapped drive. With a network packet trace I see the client create the file, set the file length, then do two writes to the file. The second write I can see has %%EOF at the end of the data. The file size in bytes on the client and in the content store is the same length.

Could you send me a network packet trace from your setup of a simple PDF export (via email rather than posting on here would be better).

[hi-ko]

Thanks for your evaluation an effort. I'm still trying to identify the conditions when this effect happens since this does not apply to all the clients having win10/Ofice216. I try to create a packet trace which contains this pattern.

[hi-ko]

Unfortunately the error is no longer reproducible on the affected client systems. We guess it is related to an O365 or Win10 update.
The question is how to support this beast longterm ...

thanks a lot for your efforts.

[FileSysOrg]

ok, no problem, if it does resurface then a packet trace may be the best way to track it down, or help me to reproduce it locally.

MS Office has always been a bit of problem app.