XCON: Setting up Advanced Logging on the Exchange 5.0 and 5.5 MTAsID: Q168906
|
There are times when it may become necessary to enable advanced logging on
the Microsoft Exchange Message Transfer Agent (MTA) in order to diagnose a
problem. This is in addition to the logging provided in the Windows NT
application log.
To enable the advanced logging, start the Windows NT Registry Editor and go
to the following key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeMTA
\Parameters
Find Text Event Log and set it to 1 (the default is 0).
Unbounded Event Log
Unbounded APDU Log
Unbounded Interop Log
These write to the Ev0.log, Bf0.log, and Ap0.log files, respectively.
Unbounded Event Log:
This enables uninterupted logging to the Ev0.log file. This is basically a text version of the Windows NT application log and will log every event that is in the application log.Unbounded APDU Log:
This enables uninterupted logging to the Bf0.log file. This log is enabled by setting X.400 Service and APDU logging to maximum in the MTA Properties page, Diagnostics Logging tab. The APDU log is a binary trace of all the ASN.1 activity within the MTA. This data can be viewed with the ASN.1 viewer (Aspirin) located on the BackOffice Resource Kit 2 compact disk.Unbounded Interop Log:
This enables uninterupted logging to the Ap0.log file. This log is enabled by setting Interoperability logging to maximum in the MTA Properties page, Diagnostics Logging tab. The Interoperability log is a text 'sniff' of the incoming and outgoing transport activity for the subject MTA.
Additional query words: x400 spdu 1988 1984 blue red book itu ccitt
Keywords : XCON
Version : 5.0 5.5
Platform : winnt
Issue type :
Last Reviewed: April 30, 1999