XCON: Description of Diagnostics Categories for MTA

Article translations Article translations
Article ID: 163033 - View products that this article applies to.
This article was previously published under Q163033
This article has been archived. It is offered "as is" and will no longer be updated.
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
Expand all | Collapse all


This article contains descriptions of the logging categories of the Exchange Server Message transfer agent (MTA).

More information

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

X.400 Service
X.400 protocol events, such as submission and delivery reports.
Events related to the use of MTA resources.
Events related to attempted security violations.
Communication among MTA components, between MTAs and between the MTA and XAPI clients such as the store, MSMI, and DXA. This includes RPC use.
Field Engineering
Internal debugging trace.
MTA Administration
Administration program access to MTA queues and routing information.
The configuration of internal parameters and/or problems in one or more MTA configuration files.
Directory Access
Events related to the MTA's use of the directory.
Operating System
Events related to the MTA's use of Windows NT functions, such as thread creation and file operations.
Internal Processing
Events related to the internal operation of MTA application code. Error events in this category indicate serious problem in the MTA.
Tracks the binary content of protocol messages. Use this category and Interface to log stack traces and XAPI traces to MTADATA\AP*.LOG.

NOTE: No additional events are logged to the application or EV*.LOGs when logging is turned up on this category.
APDU (Application Protocol Data Unit)
Tracks full P1 content (MTA send/receive) and fully encoded P1 APDU (communication between remote MTAs) to diagnose interoperability or conformance problems. Use this category and X.400 Service to log binary data to MTADATA\BF*.LOG.

NOTE: No additional events are logged to the application or EV*.LOGs when logging is turned up on this category.
EV*.LOGs are Text Event Logs. You can enable these logs by updating the registry key TextEventLogging. To do so:
  1. Start the Registry Editor (Regedt32.exe).
  2. Locate the following subkey:
  3. Change the DWord value to 1.
  4. Quit the Registry Editor.
For additional information about diagnostics logging, click the article number below to view the article in the Microsoft Knowledge Base:
163032 XCON: Description of Diagnostics Logging for MTA
Windows Scripting Host must be installed. To do so, visit the following MSDN Web site:
NOTE: In the code that follows, "HKLM" means "HKEY_LOCAL_MACHINE".


Article ID: 163033 - Last Review: November 1, 2013 - Revision: 4.0
Applies to
  • Microsoft Exchange Server 5.5 Standard Edition
  • Microsoft Exchange 2000 Server Standard Edition
kbnosurvey kbarchive kbinfo KB163033

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com