XCON: Application Protocol Data Unit (APDU) Logs (BF0.LOG)

Last reviewed: February 3, 1998
Article ID: Q163324
The information in this article applies to:
  • Microsoft Exchange Server, version 4.0
  • Microsoft Exchange Server, version 5.0

SUMMARY

Application Protocol Data Unit (APDU) text logs are binary representations of communication among Microsoft Exchange Message Transfer Agents (MTAs) in different Sites and between MTA and client applications within a Site. The log includes the fully-encoded ASN.1 envelope. This is useful for verifying when messages from remote MTAs are bad or invalidly formatted.

MORE INFORMATION

Increasing Diagnostic Logging levels to Medium or higher for both the MTA's APDU and X.400 Service categories will generate BF*.LOG files in the exchsrvr\MTADATA directory. The current log is always named BF0.LOG. Prior logs are named BF#.LOG with the # increasing with the age of the log. When a log reaches 5 megabytes in size it is renamed and a new log is begun.

NOTE: There is no difference between Medium and Maximum for the APDU category. However, in addition to its influence on APDU logs, the diagnostics logging level of the X.400 Service category determines which X.400 events are written to event logs.

APDU logs can be instrumental in diagnosing problems with the MTA. However, they are valuable only to those familiar with ASCII translations of X.400 protocol. These logs can grow quite large very quickly and cause performance on the Server to suffer.

An ASN.1 Parser can be used to decode the data in a BF0.LOG.

If the logging levels of both X.400 Service and APDU are set to Minimum, the first four events in the table below will be written to the Event Logs. If the logging levels of both categories are set to Medium or greater, all six events will be logged and the APDU text logs will be generated as well.

Event #  Description                                Logging Level
200      Bad APDU transferred in from another MTA   Minimum
220      Bad APDU submitted to this MTA             Minimum
269      APDU delivery failed temporarily           Minimum
270      APDU delivery failed permanently           Minimum
271      APDU sent                                  Medium
271      APDU received                              Medium


Additional query words: kbfaq whitepaper logging section
Keywords : XCON kbusage
Version : 4.0 5.0
Platform : winnt
Issue type : kbtshoot


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: February 3, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.