![]() ![]() What critical piece of information am I missing? Yup, the filename and/or filepath. OK, I see a file IO error, an error code, and a message about failing to create a temporary directory. The first set of Unexpected messages I received looked like the following: 11:30:00.452›OUTLOOK (0x17e)›0xe92c000› Outlook›MbuFont›icy4b› Unexpected› Failed to write postScript name to file What I eventually realized is that you need to look for messages that contain the word “Unexpected” - Microsoft would it kill you to adhere to syslog RFC standards is use something like “error”? - note using grep on the file did not work for me so I used vim and its search capabilities to look for Unexpected messages. Tailing this log while reproducing the issue will result in a lot of output. Then you reproduce the issue and check the logs - the big question is where are the logs? Unfortunately, Outlook does not tell you this either, but you can find it in: ~/Library/Containers//Data/Library/Logs. Then you need to close Outlook and open it again - wish it would state that. To do this, you go to Tools > Sync Errors > Gear Icon > Turn on logging for troubleshooting. ![]() Next up, I enabled troubleshooting logging. After completing this, I reinstalled Office, but the problem persisted.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
February 2023
Categories |