XCON: Description of MTA Diagnostics Logging Options

• Microsoft Exchange Server, version 4.0

SUMMARY

Five different variations of logs may be created when troubleshooting the Microsoft Exchange Message Transfer Agent (MTA) or X.400 Connector:

1. Event Viewer Application Log (*.EVT): Logging begins when Diagnostics Logging options have been enabled on the MTA; all logging can only be seen in the Windows NT Event Viewer.

2. EV0.LOG: Logging to this file, located in Exchsrvr\mtadata, begins when the TextEventLog value in the Windows NT Registry:

         KEY_LOCAL_MACHINE\SYSTEM\CURRENTCONTROLSET\SERVICES
                          \MSEXCHANGEMTA\Parameters,
   
      has been changed from 0, the default, to 1. The MTA service must be
      stopped and restarted for this Registry entry to take effect. This
      logging will include the information that is seen in Event Viewer;
      however, it will be in TXT file format, rather than EVT, so that it can
      be viewed in any environment.
   
   

3. Tracking.log: The Tracking.log subdirectory under \Exchsrvr contains logs for each day that Message Tracking has been enabled. The log files are named according to the day they were created (a log file created on 7/1/96 will be named 19960701.log). These logs are created when Message Tracking has been enabled on either the Information Store Site Configuration object or the MTA Site Configuration object in the Microsoft Exchange Administrator program. These objects are in the Configuration container. The Tracking.log file may be viewed by 2 methods:

         1. The Message Tracking Center (click Track Message on the Tools menu
            of the Microsoft Exchange Administrator program) is used to
            selectively query the tracking log files and is effective when an
            administrator desires to track a particular message to find out
            if/how it was delivered.
   
         2. The Tracking.log file is in tab-delimited TXT format and can be
            viewed with any text editor, or it can more effectively be used
            by opening it in Excel. The Tracking.log will give an
            administrator such information as Message ID, Event Type,
            Date/Time stamp, Length of Message, Recipients, and Status of
            all messages received/sent on the corresponding day. Please
            refer to pages 589-591 in the Administrator's Guide for
            specific details on the various event codes and fields in
            this log file.
   
   

4. Ap0.log: The Ap0.log is generated when the Diagnostics Logging options have been set up correctly. Specifically, the Interface and Interoperability categories must be set to Maximum on the MTA service. This file will contain information about how the MTA's are making connections and sending data, as defined in RFC1006.

5. Bf0.log: The Bf0.log is generated when the X400 Service and APDU categories have been set to a minimum of Medium. This log file contains a binary dump of messages that have been sent/received by the MTA.

MORE INFORMATION

This section includes a sample of each of the files described above. This message was sent to a recipient called "alpine1" in Site Alpine and was copied to a recipient on the local server called "tamraj1" in Site TamraJ.

1. Event Viewer (generated by MSExchangeMTA,X.400 Service):

Object 06000056 received from entity /O=MICROSOFT/OU=TAMRAJ/CN=CONFIGURATION/CN=SERVERS/CN=TAMRAJ 2/CN=MICROSOFT PRIVATE MDB. The entity is a Message, object is a Normal priority Message, the MTS identifier is C=US;A= ;P=MICROSOFT;L=TAMRAJ2-960701173047Z-2, and content length is 1155. The number of objects sent so far = 1. External trace information (first 100 bytes) = 3080638061801302555300006280130120000013094D4943524F534F4654 0000318080113936303730313133333135352D3034303082010083020600 00000000. (10)

Message C=US;A= ;P=MICROSOFT;L=TAMRAJ2-960701173047Z-2 was successfully appended to the /o=MICROSOFT/ou=TAMRAJ/cn=Configuration/cn=Connections/cn=In ternet Mail Connector (TAMRAJ2) transfer-in queue. [XAPI TRANSFER 37 73] (10)

Object 06000057 was sent to entity /O=MICROSOFT/OU=TAMRAJ/CN=CONFIGURATION/CN=CONNECTIONS/CN=IN TERNET MAIL CONNECTOR (TAMRAJ2). The entity is a XAPI-

Gateway        , object is a Normal priority Message, the

Entity /o=MICROSOFT/ou=TAMRAJ/cn=Configuration/cn=Connections/cn=In ternet Mail Connector (TAMRAJ2) has removed object C=US;A= ;P=MICROSOFT;L=TAMRAJ2-960701173047Z-2 from the transfer-in queue/mailbox. Internal object ID: 06000057. [XAPI GATEWAY 36 134] (10)

1. Ev0.log:

          Message appended to transfer-in queue OK
            Entity name

            MTS Identifier C=US;A= ;P=MICROSOFT;L=TAMRAJ2-

(MTA XFER-IN(17) Proc 205) 07-01-96 01:32:09pm

          Object 06000057 sent to entity

            Entity is a XAPI-Gateway
            Object is a Normal priority Message
            MTS Identifier C=US;A= ;P=MICROSOFT;L=TAMRAJ2-

            Content length 1155
            External Trace Information (first 100 bytes) =

            No. of objects sent so far = 1
            PDU dump reference 2