Topic Last Modified: 2009-03-10
The Microsoft® Exchange Server Analyzer Tool queries the MessageID property for each instance of the Exchange_MessageTrackingEntry Microsoft Windows® Management Instrumentation (WMI) class.
If the Exchange Server Analyzer does not receive a result from the query, the Exchange Server Analyzer displays an error.
The most likely cause of this error is that message tracking is disabled.
Message tracking logs information about the sender, the mail message, and the message recipients. Specifically, you can review statistics such as the time the message was sent or received, the message size and priority, and the list of message recipients. You can also log the subject line of e-mail messages. You can use message tracking to search for messages, such as system messages, public folder messages, and e-mail messages.
You must enable message tracking on each server for which you want to track messages. When it is enabled, all messages that are routed through a server are added to the message tracking logs.
The Exchange Server Analyzer requires that message tracking be enabled for it to start its scans.
|The following permissions are required to perform this procedure: member of the local administrators group and member of a group that has had the Exchange Administrators role applied at the administrative group level|
In Exchange System Manager, expand Servers, right-click the server on which you want to enable message tracking, and then click Properties.
On the General tab, select the Enable message tracking check box.
To record the subject of any message sent to, from, or through the server, select the Enable subject logging and display check box.
Note: If you enable subject logging, you may cause some decrease in performance.
Under Log file maintenance, you can prevent the removal of log files or modify the length of time that the log files are kept. The default period that tracking logs are kept is seven days.
Note: On servers that process large quantities of mail, the tracking logs grow quickly. Make sure that you have sufficient disk space for the log files and for other services or applications that use this disk.
Click OK or Apply. You do not have to restart services for this change to take effect.
On a server that is running the Mailbox role, Hub Transport role, or Edge Transport role, start the Exchange Management Shell.
To examine the message tracking options that are available, run the following cmdlet:
get-TransportServer <ServerName> | format-list "MessageTracking*"
By default, message tracking is enabled in Exchange 2007. If message tracking is disabled, the following results appear:
MessageTrackingLogEnabled : False
To enable message tracking, run the following cmdlet:
set-TransportServer <ServerName> -MessageTrackingLogEnabled $true
To modify the message tracking log file location, run the following cmdlet:
set-TransportServer <ServerName> -MessageTrackingLogPath "<drive>:\<path>"
Note: The log file location must be a path that is located on the local computer.
Exit the Exchange Management Shell.
For more information about how to use the Management Console to configure message tracking in Exchange 2007, see "How to Configure Message Tracking" (http://go.microsoft.com/fwlink/?linkid=100591).
For more information about how to use the Set-TransportServer cmdlet, see "Set-TransportServer" (http:// go.microsoft.com/fwlink/?linkid =140266).
For more information about how to use the Message Tracking Center, see Microsoft Knowledge Base article 262162, "Using the Message Tracking Center to Track a Message in Exchange Server" (http://go.microsoft.com/fwlink/?LinkId=3052&kbid=262162).
For more information about how to troubleshoot Exchange Server transport issues, see Microsoft Knowledge Base article 821910, "How to troubleshoot for Exchange Server 2003 transport issues" (http://go.microsoft.com/fwlink/?LinkId=3052&kbid=821910).