Article ID: 147454
Article Last Modified on 10/28/2006
APPLIES TO
- Microsoft Exchange Server 4.0 Standard Edition
- Microsoft Exchange Server 5.0 Standard Edition
This article was previously published under Q147454
SYMPTOMS
The Microsoft Mail Connector PC MTA for the Microsoft Mail Connector interchange does not log message sizes in the message-tracking log files.
STATUS
Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 4.0. This problem has been corrected in the latest U.S. Service Pack for Microsoft Exchange Server version 4.0. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):
S E R V P A C K
Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 5.0. This problem has been corrected in the latest U.S. Service Pack for Microsoft Exchange Server version 5.0. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):
S E R V P A C K
MORE INFORMATION
When message tracking is enabled, tracking log files are written to the following location:
Exchsrvr\Tracking.log
The tracking logs are tab-delimited text files that are best displayed in Microsoft Excel. The file name of each tracking log corresponds to the date of messages tracked for that particular log file. For example, if a message is sent through the MSMI on May 14, 1997 and message tracking is enabled, a tracing log file is created with the following file name:
19970514.log
The component that logs a particular entry in the message-tracking log is located in the fourth column, or column "D" in Microsoft Excel. For the PC MTA, the component name will be the name defined for the PC MTA by the administrator when the Microsoft Mail Connector was configured.
The message size should be logged in the ninth column or column "I" in Excel. In versions 4.0, SP1, SP2, SP3, SP4 and version 5.0, the message size logged for any message going through the PC MTA will be 0 bytes.
Keywords: kbbug kbfix kbusage KB147454
