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.

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.

Related:

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 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 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:

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:

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
  1. Use network Monitor to capture Network Traces, and then view these traces from Network Monitor for network issues.
  2. If the error persists, stop and restart the message transfer agent service.
  3. If the error still persists, restart Microsoft Exchange Server.

Related:

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: