Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
XADM: The Second DL in a Batch Does Not Replicate from Exchange Server 5.5 to Exchange 2000
Article ID: 306999 - View products that this article applies to.
This article was previously published under Q306999
If a Microsoft Exchange Server version 5.5 distribution list (DL) has an alias name that contains a space as the first character, exceeds 20 characters in length, and the DL is the second entry in a batch Lightweight Directory Access Protocol (LDAP) transaction, the DL may not replicate by means of the Active Directory Connector (ADC). The following error message may be logged in the Application event log:
NOTE: The "cn=\12345678901234567777123" section varies depending on the environment. This section is the alias of the DL that the ADC is trying to import.
Event Type: Error
Event Source: MSADC
Event Category: LDAP Operations
Event ID: 8021
LDAP Add on directory SERVERNAME for entry 'cn=\ 12345678901234567777123,OU=YourOU,DC=YourDomainName,DC=com' was unsuccessful with error:[0x44] Already Exists [ 00000526: UpdErr: DSID-031A0AE5, problem 6005 (ENTRY_EXISTS), data 0 ]. (Connection Agreement 'Your connection agreement name' #1436)
For more information, click http://search.support.microsoft.com/search/?adv=1.
This problem can occur if the ADC does not correctly import two Exchange Server 5.5 DLs when the DL alias names are similar.
To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
301378The English version of this fix should have the following file attributes or later:
(http://support.microsoft.com/kb/301378/EN-US/ )XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
Collapse this tableExpand this table
NOTE: Because of file dependencies, this update requires Microsoft Exchange Server 2000 Service Pack 1.
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 2.