Details | |
Product: | Exchange |
Event ID: | 65 |
Source: | MSExchangeCCMC |
Version: | 6.0 |
Component: | Connector for Lotus cc:Mail |
Symbolic Name: | MSG_DIRSYNC_EXCHANGE_NAME_EXISTS |
Message: | The Microsoft Exchange entry with CCMAIL e-mail address {name} at {address} could not be written to Lotus cc:Mail because it conflicts with the existing Microsoft Exchange entry named {name} at {address}. Choose a unique name and update the CCMAIL e-mail address. |
Explanation | |
The proxy address generation defined in recipient policies may be duplicating existing cc:Mail addresses. | |
User Action | |
Perform the user action specified in the message. |
Tag: Message transfer agent
Unable to allocate memory for entity . Reboot the computer. If that does not work, Contact Microsoft Technical Support. [ ] (14)
Details | |
Product: | Exchange |
Event ID: | 59 |
Source: | MSExchangeMTA |
Version: | 6.5.6940.0 |
Component: | Microsoft Exchange Message Transfer Agent |
Message: | Unable to allocate memory for entity <object name>. Reboot the computer. If that does not work, Contact Microsoft Technical Support. [<value> <value> <value> <value>] (14) |
Explanation | |
The message transfer agent (MTA) has failed to allocate and reserve memory from the operating system. |
|
User Action | |
Free up the memory in use by closing any nonessential applications. Increase your system’s physical or virtual memory. Verify that there is enough disk space for the paging file to grow. |
Related:
- Unable to initialize bytes of memory. Semaphore creation failed. Reboot the computer. It that does not work, contact Microsoft Technical Support. [% 2 ] (16)
- Unable to allocate memory. Domain defined attribute allocation failed. [ ] (12)
- Unable to allocate memory. Session object allocation failed. [ ] (12)
- Unable to initialize bytes of memory. Reboot the computer. If that does not work, call Microsoft Technical Support. [ ] (16)
- Event ID 4425 — Transaction Manager Functionality
Unable to allocate memory for entity {object name}. Reboot the computer. If that does not work, Contact Microsoft Technical Support. [{value}{value}{value}{value}] (14)
Details | |
Product: | Exchange |
Event ID: | 59 |
Source: | MSExchangeMTA |
Version: | 6.0 |
Component: | Message Transfer Agent |
Symbolic Name: | MTA00059 |
Message: | Unable to allocate memory for entity {object name}. Reboot the computer. If that does not work, Contact Microsoft Technical Support. [{value}{value}{value}{value}] (14) |
Explanation | |
The message transfer agent (MTA) has failed to allocate and reserve memory from the operating system. | |
User Action | |
Free up the memory in use by closing any nonessential applications. Increase your system’s physical or virtual memory. Verify that there is enough disk space for the paging file to grow. |
Related:
- An internal MTA error occurred. The object is not on session queue. Queue ID: {id}. Object ID: {id}. Entity name: {object name}. Possible database corruption. Run MTACHECK.EXE if problem persists. [{value}{value}{value}{value}] (14)
- A fatal MTA database server error was encountered. The object reservation count for object {object name} has been decremented below zero. [{value}{value}{value}{value}] (16)
- An MTA database server error was encountered while copying an image of an object. Called from {directory name}. Procedure {name}. Database error code: {error code}. Object at fault: {object name}. [{value}{value}{value}{value}] (14)
- An MTA database server error was encountered while copying an object. Called from {directory name}. Procedure {name}. Database error code: {error code}. Object at fault: {object name}. [{value}{value}{value}{value}] (14)
- An internal MTA error occurred: transfer out failure. Object ID: {id}. Entity name: {object name}. [{value}{value}{value}{value}] (14)
An error occurred while performing an ASN.1 decode. Syntax server error code: , Primitive type: , Error detected at offset . Contact Microsoft Technical Support. [ ] (14)
Details | |
Product: | Exchange |
Event ID: | 45 |
Source: | MSExchangeMTA |
Version: | 6.5.6940.0 |
Component: | Microsoft Exchange Message Transfer Agent |
Message: | An error occurred while performing an ASN.1 decode. Syntax server error code: <error code>, Primitive type: <name>, Error detected at offset <value>. Contact Microsoft Technical Support. [<value> <value> <value> <value>] (14) |
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 Exchange server installation compact disc. For more information, see Microsoft Knowledge Base articles 168906 and 163032. |
Related:
- A fatal internal MTA error has occurred. Initialization error: ASN.1 template files failed to load. ASN.1 template file may be corrupt. [ ] (16)
- An internal MTA error occurred. A NULL constant was called during an ASN.1 decode. Contact Microsoft Technical Support. [ ] (14)
- Unable to initialize due to a missing or damaged configuration file. The ASN.1 template file is either missing or corrupt. Reload a new copy from the install CD. [ ] (16)
- Unable to initialize due to a missing or damaged configuration file. Reload the ASN.1 template files from the installation CD. If that does not correct the problem, Contact Microsoft Technical Support. [ ] (16)
- An interoperability error occurred. Utility error. ASN.1 got beyond the end of the data. [ ] (14)
An error occurred while performing an ASN.1 decode. Syntax server error code: {error code}, Primitive type: {name}, Error detected at offset {value}. Contact Microsoft Technical Support. [{value}{value}{value}{value}] (14)
Details | |
Product: | Exchange |
Event ID: | 45 |
Source: | MSExchangeMTA |
Version: | 6.0 |
Component: | Message Transfer Agent |
Symbolic Name: | MTA00045 |
Message: | An error occurred while performing an ASN.1 decode. Syntax server error code: {error code}, Primitive type: {name}, Error detected at offset {value}. Contact Microsoft Technical Support. [{value}{value}{value}{value}] (14) |
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 theMicrosoft 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 may 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 Knowledge Base articles Q168906 and Q163032. |
Related:
- 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)
- An interoperability error occurred with entity {object name}. A reliable transport service element (RTSE) 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)
- An interoperability error occurred with {object name}. Utility error. Unable to decode ASN.1. Server error code {error code} was detected at offset {value}. Node label {name}. Control block index {index name}. [{value}{value}{value}{value}] (14)
- An internal MTA error has occurred. The ASN.1 data from {object name} can not be decoded. Syntax server error code {error code}. An error was detected at offset {value}. Node label {name}. Control block index {index name}. [{value}{value}{value}{value}] (14)
- An internal MTA error occurred. Contact Microsoft Technical Support. Error code={error code} [{value}{value}{value}{value}] (14)
An internal error occurred while transferring a message or report. [ ] (14)
Details | |
Product: | Exchange |
Event ID: | 25 |
Source: | MSExchangeMTA |
Version: | 6.5.6940.0 |
Component: | Microsoft Exchange Message Transfer Agent |
Message: | An internal error occurred while transferring a message or report. [<value><value> <value> <value> <value> <value> <value>] (14) |
Explanation | |
The association will be stopped and restarted if necessary. Associations are paths that are opened to other systems. Each association is contained within a connection and is used to transfer messages to a system. You may have multiple associations in each connection. |
|
User Action | |
|
Related:
- Unable to connect to the MTA. Consecutive ma-open calls are failing with error . This Error code corresponds to a Network Error.
- A fatal internal MTA error occurred. Queue creation failure for queue . Contact Microsoft Technical Support. [ ] (16)
- A message was sent to the gateway on session index . [ ] (8)
- A fatal internal MTA error occurred. Unable to initialize because queue could not be created. Contact Microsoft Technical Support. [ ] (16)
- A fatal system error occurred while initializing the MTA. Reboot the computer. If that does not work, Contact Microsoft Technical Support. [ ] (16)
An error occurred while processing an association. The association will be terminated and restarted if necessary. [ ] (14)
Details | |
Product: | Exchange |
Event ID: | 23 |
Source: | MSExchangeMTA |
Version: | 6.5.6940.0 |
Component: | Microsoft Exchange Message Transfer Agent |
Message: | An error occurred while processing an association. The association will be terminated and restarted if necessary. [<value> <value> <value> <value> <value> <value> <value>] (14) |
Explanation | |
There may be too many associations open. Associations are paths that are opened to other systems. Each association is contained within a connection and is used to transfer messages to a system. You may have multiple associations in each connection. |
|
User Action | |
Use Network Monitor to capture network traces, then view these traces from Network Monitor for any network issue. Review the Threshold setting for Association parameters. This controls the number of messages Exchange allows to wait before it opens another association. If the error persists, stop and restart the message transfer agent (MTA) service. |
Related:
- A resource limit has been reached when attempting to open an association. Number of associations configured: [ ] (14)
- Unable to initialize due to a bad configuration. Contact Microsoft Technical Support. [ ] (16)
- The MTA database recovery operation has completed successfully. Recovery details can be found in the file: . [ ] (14)
- An MTA database server error was encountered. The object could not be rolled out to disk due to a disk error. Database error code: . [ ] (14)
- A fatal database error occurred, the database recovery operation was not successful and manual correction will be required. Details can be found in the file: . Please contact Microsoft Technical Support. [ ] (16)
An MTA database server error was encountered. Stop the MTA and run the knowledge consistency checker. [ ] (14)
Details | |
Product: | Exchange |
Event ID: | 21 |
Source: | MSExchangeMTA |
Version: | 6.5.6940.0 |
Component: | Microsoft Exchange Message Transfer Agent |
Message: | An MTA database server error was encountered. Stop the MTA and run the knowledge consistency checker. [<value> <value> <value> <value> <value> <value> <value>] (14) |
Explanation | |
A message transfer agent (MTA) database server error was encountered. |
|
User Action | |
Stop the MTA and run the mtacheck utility. |
Related:
- An internal MTA error occurred: ran off end of object. Error code : . Attribute: . Offset: . Entity name: . [ ] (14)
- An internal MTA error occurred. An open function mismatch occurred with the directory. Entity name: . [ ] (14)
- An internal MTA error occurred. Object is not reserved. Session reserving object: . Entity name: . [ ] (14)
- An MTA database server error was encountered while getting an attribute key from the database server. Called from . Procedure . Database error code: . Attribute: . [ ] (14)
- An MTA database server error was encountered while getting a number of values for an object. Called from . Procedure: . Database error code: . Object at fault: . Attribute identifier: . Referenced object, (00000000 => N/A). Referenced object error . [ ] (14)