To protect your data, the calendar log file is a binary file that cannot be read without a conversion process. However, this is partially true… To explain what I mean, let us have a look at the next section. Notice that I mention free/busy in the list above. Communications with Exchange, POP3, SMTP, and IMAP servers.A unique log file is generated for each Send/Receive action that you perform on these accounts. Transactions for the Messaging Application Programming Interface (MAPI), which is used with Microsoft Exchange, POP3, Internet Message Access Protocol (IMAP), Simple Mail Transfer Protocol (SMTP), and Lightweight Directory Access Protocol (LDAP).The main purpose of the calendar logging feature is to quickly identify situations where, for example, meetings are inexplicably deleted from a calendar folder. Calendar transactions that are generated by Outlook features, by user actions, by the object model, or by the MAPI Calendar Table, including:Ĭalendar item actions (creation, modification, or deletion).The logging option logs information about the following features: If you don’t turn off logging, the log files continue to increase in size. Note: turn off logging after you complete your troubleshooting. Select or clear the Enable logging (troubleshooting) check box.
On the Other tab, select Advanced Options.Under Other, select or clear the Enable troubleshooting logging (requires restarting Outlook) check box.In Outlook, go to the File tab > Options > Advanced.As such, I decided to turn on logging in Outlook to try to find out what was happening. While deploying an Exchange hybrid solution for a client the other day, I experienced some problem with free/busy information between the on-premises Exchange and Exchange Online.
0 kommentar(er)
