XCON: Description of Diagnostics Logging for MTA

 Last reviewed: October 29, 1997
Article ID: Q163032
The information in this article applies to:

- Microsoft Exchange Server versions 4.0 and 5.0

IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.

SUMMARY

This article provides descriptions of the logging categories on the message transfer agent (MTA) of Exchange Server.

MORE INFORMATION

X.400 Service

X.400 protocol events, such as submission and delivery reports.

Resource

Events related to the use of MTA resources.

Security

Events related to attempted security violations.

Interface

Communication among MTA components and between MTAs. Includes RPC use.

Field Engineering

Internal debugging trace.

MTA Administration

Administration program access to MTA queues and routing information.

Configuration

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 problems in the MTA.

Interoperability

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, using the following procedure.

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it.

  1. Start the Registry Editor (Regedt32.exe).

  2. Go to the following subkey: 

          HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeMTA
      \Parameters\TextEventLogging

  3. Change the DWord value to 1.

  4. Quit the Registry Editor. 
Keywords          : XCON kbusage
Version           : WinNT:4.0,5.0
Platform          : WINDOWS
Issue type        : kbinfo
Solution Type     : kbworkaround

================================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: October 29, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.