When you need help troubleshooting most calendar issues in Microsoft Outlook and Microsoft Exchange, you have to collect and provide lots of data for the Microsoft support professional. This is primarily because of the complexity of the calendar feature set in Microsoft Office Outlook and Microsoft Exchange Server and because of the varied scenarios and products that affect the calendar data. The troubleshooting data that is needed includes an Exchange Store log for a user. This article describes how to enable Exchange 2007 and Exchange 2010 Store tracing for troubleshooting issues that are related to an Outlook calendar.
For information about working with Microsoft support to troubleshoot the Outlook calendar in an Exchange environment, visit the following Microsoft website:
Important This article describes the calendar logging process to use when you work with the support team at Microsoft. It is not intended to provide complete information for you to perform store logging by yourself. There is a risk of performance problems on the Exchange server if logging is not enabled correctly. That is why you should work with the support team during this process.
Microsoft Exchange Server 2007 and Microsoft Exchange Server 2010 can trace calendar activities that occur in the store. This tracing is performed through the Exchange Troubleshooting Assistant (ExTRA). The tracing can be done per user or per server.
The following steps show how to enable this tracing feature when you work with a Microsoft support engineer on a support case for calendar issues.
Enable Exchange tracing for calendar issues
Identify the user whose mailbox will be traced by this process.
Note For best performance, you should always identify one user who is encountering the issue, and then trace only that user's mailbox by using per-user tracing.
On the Exchange server on which the user's mailbox resides, start ExTRA. To do this, click Start, click Run, type the following command in the Open box, and then click OK:
On the "Welcome to the Exchange Troubleshooting Assistant" page, click Select a task.
On the "Troubleshooting Task Selection Screen" page, click Trace Control.
Click OK when you receive the following warning:
This server does not have the module needed for interpreting traces. Continue only if this is being done under the direct supervision of a qualified Exchange support engineer.
On the "Configure Trace File" page, configure the following options:
Trace file location (the default location is C:\Documents and Settings\<username>)
Trace file name (the default name is ExchangeDebugTraces.etl)
Maximum trace file size (the recommended size is 100 MB)
Sequential logging (enabled)
Note In Exchange Server 2010, this option has been renamed to Create a new file when max file size is reached
Run traces for:0 seconds
Note Accept the default configuration setting if you want tracing to run until you manually stop tracing. Otherwise, select the check box, and then set the number of seconds for which you want to run the trace.
Click Set manual trace tags.
On the "Set Trace Tags Manually" page, follow these steps:
Configure the following settings:
Trace Types: PFD, Fatal, Error, Warning, Info, Debug, Performance, Function
Microsoft Exchange Server 2010 Enterprise, Microsoft Exchange Server 2010 Standard, Microsoft Exchange Server 2007 Enterprise Edition, Microsoft Exchange Server 2007 Standard Edition, Microsoft Office Outlook 2007, Microsoft Office Outlook 2003, Microsoft Outlook 2002 Standard Edition