Discussion Locked

Exchange logs

0 helpful
10 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Everyday in my exchange server eventviewer the following event is recorded.

The message tracking log file e:\exchsrvr\tracking.log\200203xx.log was deleted.

xx is replaced by the date.why this file is created and is it a problem indication.eventviewer logs this as warning.
Event Id : 5008
Source : MSExchangeSA
Type : Warning

10 replies

by deadly dave

This happens because you have message tracking enabled and the tracking logs are deleted automatically after however many days you have set fro them to be kept. It is not a problem. You will find "enable message tracking" in the
Information Store Site configuration amd MTA Site configuration containers under the main Configuration container

by jdubrow

The first answer is correct.. the reason for that log is to enable you the opportunity to track msgs as they go through your system.. Within the exchange administrator go to tools then track msg.. to begin looking for a message..

by dynamo2003

I will advice you to turn off message tracking. This happen to us sometimes ago when someone turned on message tracking to maximum on the MTA the log generated over a short period of time say a week was over 2.6GB therefore bringing the systems directory to a stand still.

Message tracking should only be used for diagnostic purposes. If you are ever in doubt please refer to Exchange Book Online or the TechNet. Exchange Book Online can be installed using the Exchange installation CD.

by bretth

The third answer is talking about a different feature. Message tracking is for tracking the flow of messages through your mail system and out to the next step out from your Exchange system, eg firewall. A new log is created every day at 00:00GMT, and it is written to in sequence. These logs may be anywhere from 5MB on a smallish system, up to well over 100MB on a busy system, and are plain text files.
Diagnostics logging writes an entry to the event log for each event/step performed. Diagnostics logging can be enabled on many levels of Exchange, and you can choose the level of logging at a very granular level. It should only be used for diagnostics purposes, as it does increase the load on the systsm, and can chew up some disk space. 2GB+in a week is quite a lot, though.

This discussion is closed to new replies.