Hello Mohan, the thread didn’t help
I have confirmed the issue with a new install of os x 10.9.5 , a new install of MS office 2016 volume licensed version
on both afp and smb mounted home directories, where making a user account local to the machine does not produce the log (non networked home Dirs are not a option), so at the moment I am thinking it is debug process detecting the users office directory
UBF8T346G9.Office its on a network file store and trying to send log info back, but we are behind a firewall and authenticated web proxy so it can not send direct and creates the MicrosoftShipAssertLog
and a MicrosoftShipAssertLog.send.txt files.
I have tried going into the programs selecting the error reporting tool and turning that off, same result
I have tried going into the programs selecting the error reporting tool and turning that off AND removing the MicrosoftShipAssert.app
from the shared resources directory, that causes excel to fail and exit after 1 minute crashing Excel.
trying to symlink UBF8T346G9.Office to a local disk , crashes office 2016 mac apps immediately;
In summary nothing reinstalls, turning off error reporting removing MicrosoftShipAssert.app gives me either a set office apps
that do not generate Log
;files that grow to gigabytes in size or cause the apps to crash and be unusable.
Also with the rate of updates for Office Mac 2016 are coming I replicate the tests every time
Thanks Roger