A fatal internal MTA error occurred. Unable to load ASN.1 template. Template: name. [valuevaluevaluevalue] (16)

Details
Product: Exchange
Event ID: 3052
Source: MSExchangeMTA
Version: 6.5.0000.0
Message: A fatal internal MTA error occurred. Unable to load ASN.1 template. Template: name. [valuevaluevaluevalue] (16)
   
Explanation
After a failure and a subsequent failed restart attempt, the Microsoft Exchange Server message transfer agent (MTA) logs the event listed above. Some or all of the .tpl files may be corrupted.

ASN.1 is an ISO/ITU data encoding standard that refers to Specification of Basic Encoding Rules for Abstract Syntax Notation One. The fully encoded ASN.1 envelope is in the Microsoft Exchange Server APDU (Application Protocol Data Unit) logs, which are binary representations of communication among message transfer agents (MTAs) in different sites and between MTA and client applications within a site.

APDU logs are enabled when the logging levels of the X.400 service and APDU categories are both set to Medium or greater after you select MSExchangeMTA on the Diagnostics Logging tab of the Server Properties dialog box.

These text logs are stored in the \Mtadata directory. The current log is always named Bf0.log. Prior logs are named Bfx.log, where x increases as the age of the log increases.

   
User Action
Reload the ASN.1 template files from the Microsoft Exchange Server installation compact disc.

To help Microsoft Product Support Services track down the problem, create log files. See Knowledge Base article Q163032 for more information.

To create Ap*.log files, on the Diagnostics Logging tab of the Server Properties dialog box, select MSExchangeMTA, and then set the logging level of the Interoperability and Interface categories to Maximum.

To create Bf*.log files, set the logging level of the APDU and X.400 categories to Maximum.

Save all MTA log files (mtadata\*.log), Event Viewer output, and database files. Contact Microsoft Product Support Services.

You can enable text event log files (Ev*.log) by modifying the Registry. Contact Microsoft Product Support Services for assistance.

Related:

Leave a Reply