XCON: Description of MTA Diagnostics Logging Options (153188)
The information in this article applies to:
- Microsoft Exchange Server 4.0
- Microsoft Exchange Server 5.0
- Microsoft Exchange Server 5.5
This article was previously published under Q153188 SUMMARY
Five different variations of logs may be created when troubleshooting the
Microsoft Exchange Message Transfer Agent (MTA) or X.400 Connector:
- 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.
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.
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:
- 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.
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. - 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.
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.
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. - 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.
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:
- 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.
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. - 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.
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.
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. - 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:
- 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.
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. - 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.
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.
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. - 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.
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. - 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.
| Modification Type: | Minor | Last Reviewed: | 4/28/2005 |
|---|
| Keywords: | kbusage KB153188 |
|---|
|