An internal MTA error occurred. The X.400 object manager (OM) function {name} is returning the error code {error code}. [{value}{value}{value}{value}] (12)

Details
Product: Exchange
Event ID: 6501
Source: MSExchangeMTA
Version: 6.0
Component: Message Transfer Agent
Symbolic Name: MTA06501
Message: An internal MTA error occurred. The X.400 object manager (OM) function {name} is returning the error code {error code}. [{value}{value}{value}{value}] (12)
   
Explanation
The message transfer agent (MTA) database may be corrupted.
   
User Action
Stop and restart the MTA service. If the error persists, run the Mtacheck.exe utility. Stop the MTA service, open a command prompt, and type Mtacheck/v /f c:\mta.txt. If Mtacheck removes objects from a database queue, it places each damaged object in a Db*.dat file in \Exchsrvr\Mtadata\Mtacheck.out. Check your drives and verify that core *.dat files are in the \Exchsrvr\Mtadata directories. The \Exchsrvr\Mtadata directory with *.dat files may be on more than one drive. Contact Microsoft Product Support Services for assistance.

Related:

Initialization failed. There is a bad global domain ID in the directory. ASN.1 Server error code . Offset . [ ] (16)

Details
Product: Exchange
Event ID: 3056
Source: MSExchangeMTA
Version: 6.5.6940.0
Component: Microsoft Exchange Message Transfer Agent
Message: Initialization failed. There is a bad global domain ID in the directory. ASN.1 Server error code <error code>. Offset <value>. [<value> <value> <value> <value>] (16)
   
Explanation

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. To create Bf*.log files, set the logging level of the APDU and X.400 categories to Maximum.

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

The bad data can be viewed in the APDU log in Mtadata\Bf0.log. Reload the ASN.1 template files from the Microsoft Exchange Server installation compact disc. For more information, see Microsoft Knowledge Base articles 168906 and 163032.

Related:

Unable to generate the e-mail address. Address type ‘%1’ is not valid.

Details
Product: Exchange
Event ID: 2025
Source: MSExchangeSA
Version: 8.0
Symbolic Name: evtProxyAddrTypeInvalid
Message: Unable to generate the e-mail address. Address type ‘%1’ is not valid.
   
Explanation

This Error event indicates that the System Attendant found the proxy address type was invalid and could not generate an e-mail address of this type. This error will occur one time for each object the System Attendant tries to process. This error typically occurs when an address type that is in the Address-Types container in the Microsoft Exchange container in the Active Directory directory service has been corrupted.

   
User Action

To resolve this error, follow one or more of these steps:

  • If the address type is for third-party software, contact the software vendor.

  • If the address type is for one of the standard address types, such as SMTP, X400, NOTES or GWISE, contact Microsoft Product Support Services. For information about how to contact support, visit Microsoft Help and Support.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related:

An internal MTA error occurred. The X.25 interface failed to initialize. Check to make sure the X.25 card is started. (14)

Details
Product: Exchange
Event ID: 9106
Source: MSExchangeMTA
Version: 6.5.6940.0
Component: Microsoft Exchange Message Transfer Agent
Message: An internal MTA error occurred. The X.25 interface failed to initialize. Check to make sure the X.25 card is started. (14)
   
Explanation

The message transfer agent (MTA) database may be corrupted.

   
User Action

Verify that the X.25 hardware configuration matches the value specified in the X.25 MTA transport stack object. See Knowledge Base article 149062 for X.25 information. Restart the MTA service.

Related:

An interoperability error occurred with entity . A presentation error occurred. ASN.1 decode failure. Server error code was detected at offset . Node label , Control block index . [ ]. (14)

Details
Product: Exchange
Event ID: 1192
Source: MSExchangeMTA
Version: 6.5.6940.0
Component: Microsoft Exchange Message Transfer Agent
Message: An interoperability error occurred with entity <object name>. A presentation error occurred. ASN.1 decode failure. Server error code <error code> was detected at offset <value>. Node label <name>, Control block index <index name>. [<value> <value> <value> <value>]. (14)
   
Explanation

This event typically occurs in Exchange 5.x Server environments when a message transfer agent (MTA) has been configured with a password on the General tab of the MTA property page. This is the password that foreign systems use when they connect to this (local) MTA.

   
User Action

To resolve this problem, configure the X.400 connectors in each site to pass the remote MTA password by entering the remote MTA password on the General tab of the property pages of each X.400 connector. If necessary, re-enter the values on both the MTA and X.400 connector, and then restart both the directory service and MTA service.

Related:

ROSE error, FSM state check failure. Current state , service type , service flavor , Control block index [ ] (14)

Details
Product: Exchange
Event ID: 1178
Source: MSExchangeMTA
Version: 6.5.6940.0
Component: Microsoft Exchange Message Transfer Agent
Message: ROSE error, FSM state check failure. Current state <name>, service type <name>, service flavor <name>, Control block index <index name> [<value> <value> <value> <value>] (14)
   
Explanation

ROSE refers to the remote operation service element. 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 Application Protocol Data Unit (APDU) 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

Stop and restart the message transfer agent (MTA) service. If the error persists, run the Mtacheck.exe utility. Stop the MTA service, open a command prompt, and type Mtacheck /v /f c:\mta.txt. To obtain more information, on the Diagnostics Logging of the Server Properties dialog box, select MSExchangeMTA, and then set the logging level of the Interoperability and X.400 categories to Medium or greater.

If Mtacheck removes objects from a database queue, it places each damaged object in a Db*.dat file in \Exchsrvr\Mtadata\Mtacheck.out. Check your drives and verify that core *.dat files are in the \Exchsrvr\Mtadata directories. The \Exchsrvr\Mtadata directory with *.dat files may be on more than one drive. For assistance, contact Microsoft Product Support Services.

Related:

ROSE error, no ROSE APDU found in ASN.1. Control block index [ ] (14)

Details
Product: Exchange
Event ID: 1177
Source: MSExchangeMTA
Version: 6.5.6940.0
Component: Microsoft Exchange Message Transfer Agent
Message: ROSE error, no ROSE APDU found in ASN.1. Control block index <index name> [<value> <value> <value> <value>] (14)
   
Explanation

ROSE refers to the remote operation service element. 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 Application Protocol Data Unit (APDU) 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

To obtain more information, in the Server Properties dialog box, on the Diagnostics Logging tab, select MSExchangeMTA, and then set the logging level of the Interoperability and X.400 categories to Medium or greater. Then, check the APDU log files.

Related:

ROSE error, service type out of range. Control block index [ ] (14)

Details
Product: Exchange
Event ID: 1174
Source: MSExchangeMTA
Version: 6.5.6940.0
Component: Microsoft Exchange Message Transfer Agent
Message: ROSE error, service type out of range. Control block index <index name> [<value> <value> <value> <value>] (14)
   
Explanation

ROSE refers to the remote operation service element. 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 Application Protocol Data Unit (APDU) 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

For more information, on the Diagnostics Logging tab in the Server Properties dialog box, select MSExchangeMTA, and then set the logging level of the Interoperability and X.400 categories to Medium or greater.

Stop and restart the message transfer agent (MTA) service. If the error persists, run the Mtacheck.exe utility. Stop the MTA service, open a command prompt, and type Mtacheck /v /f c:\mta.txt.

If Mtacheck removes objects from a database queue, it places each damaged object in a Db*.dat file in \Exchsrvr\Mtadata\Mtacheck.out. Check your drives and verify that core *.dat files are in the \Exchsrvr\Mtadata directories. The \Exchsrvr\Mtadata directory with *.dat files may be on more than one drive. Contact Microsoft Product Support Services for assistance.

Related:

ROSE error, ASN.1 decode failed, Syntax server error code Error detected at offset Node label Control block index [ ] (14)

Details
Product: Exchange
Event ID: 1173
Source: MSExchangeMTA
Version: 6.5.6940.0
Component: Microsoft Exchange Message Transfer Agent
Message: ROSE error, ASN.1 decode failed, Syntax server error code <error code> Error detected at offset <value> Node label <name> Control block index <index name> [<value> <value> <value> <value>] (14)
   
Explanation

ROSE refers to the remote operation service element. 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 Application Protocol Data Unit (APDU) 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. To create Bf*.log files, set the logging level of the APDU and X.400 categories to Maximum. 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

The bad data can be viewed in the APDU log in Mtadata\Bf0.log. Reload the ASN.1 template files from the Exchange server installation compact disc. For more information, see Microsoft Knowledge Base articles 168906 and 163032.

Related:

ROSE error, invalid source LPI on received message. Invalid LPI is — Control block index [ ] (14)

Details
Product: Exchange
Event ID: 1172
Source: MSExchangeMTA
Version: 6.5.6940.0
Component: Microsoft Exchange Message Transfer Agent
Message: ROSE error, invalid source LPI on received message. Invalid LPI is <value><value><value> Control block index <index name> [<value> <value> <value> <value>] (14)
   
Explanation

ROSE refers to the remote operation service element. 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 Application Protocol Data Unit (APDU) 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

To obtain more information, on the Diagnostics Logging tab of the Server Properties dialog box, select MSExchangeMTA, and then set the logging level of the Interoperability and X.400 categories to Medium or greater. Stop and restart the message transfer agent (MTA) service. If the error persists, run the Mtacheck.exe utility. Stop the MTA service, open a command prompt, and type Mtacheck /v /f c:\mta.txt.

If Mtacheck removes objects from a database queue, it places each damaged object in a Db*.dat file in \Exchsrvr\Mtadata\Mtacheck.out. Check your drives and verify that core *.dat files are in the \Exchsrvr\Mtadata directories. The \Exchsrvr\Mtadata directory with *.dat files may be on more than one drive. For assistance, contact Microsoft Product Support Services.

Related: