Duplicate users occasionally appear in the Global Address List in Exchange 2000 Server

Article translations Article translations
Article ID: 837165 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

On This Page

SYMPTOMS

After you configure the Microsoft Exchange 2000 Server Active Directory Connector (ADC) to replicate information from Microsoft Exchange Server 5.5 to the Active Directory directory service and to replicate information from Active Directory to the Exchange Server 5.5 directory, you experience both of the following symptoms:
  • Duplicate users appear in the Exchange Global Address List.
  • One or more events that are similar to the following appear in the application event log on the computer that is running the ADC service:

    Event 1

    Event ID: 8024
    Event Category: LDAP Operations
    Event Source: MSADC
    Event Type: Error
    Description: LDAP Search Initial Page on directory directoryName at base 'o=organization' with filter '(msExchADCGlobalNames=NT5:GUID*)' was unsuccessful. Directory returned the LDAP error:[0x51] Server Down.

    Event 2

    Event ID: 8024
    Event Category: LDAP Operations
    Event Source: MSADC
    Event Type: Error
    Description: LDAP Search Initial Page on directory directoryName at base 'o=organization' with filter '(distinguishedName=cn=Recipients,ou=organizationalUnit,o=organization)' was unsuccessful. Directory returned the LDAP error:[0x51] Server Down.

    Event 3

    Event ID: 8020
    Event Category: LDAP Operations
    Event Source: MSADC
    Event Type: Warning
    Description: LDAP Search of directory directoryName at base 'cn=Recipients,cn=Recipients,ou=organizationalUnit,o=organization' using filter '(objectclass=*)' was unsuccessful. Directory returned the LDAP error:[0x51] Server Down.

    Event 4

    Event ID: 8271
    Event Category: Replication
    Event Source: MSADC
    Event Type: Information
    Description: Successfully replicated the object 'OU=Recipients,OU=organizationalUnit,OU=recipients,DC=corp,DC=example,DC=com' to object 'cn=Recipients,cn=Recipients,ou=organizationalUnit,o=organization'.

    Event 5

    Event ID: 8270
    Event Category: LDAP Operations
    Event Source: MSADC
    Event Type: Error
    Description: LDAP returned the error [44] Already Exists when importing the transaction dn: cn=Username,cn=Recipients,cn=Recipients,ou=organizationalUnit,o=organization changetype: Add admin-display-name:Username distinguishedname:OU=Username,cn=Recipients,cn=Recipients,ou=organizationalUnit,o=organization createtimestamp:20030327164659.0Z objectguid:GUID replication-signature:GUID msexchadcglobalnames:forest:o=organizationGUID : EX5:cn=Username,cn=Recipients,ou=organizationalUnit,o=organization:container$to... : NT5:GUID : FOREST:GUID container-info:-2147483647 ReplicatedObjectVersion:0

    Event 6

    Event ID: 8271
    Event Category: Replication
    Event Source: MSADC
    Event Type: Information
    Description: Successfully replicated the object 'CN=user,OU=Username,OU=Recipients,OU=organizationalUnit,OU=Exchange Migration,DC=corp,DC=example,DC=com' to object 'cn=Username,cn=Recipients,cn=Recipients,ou=organizationalUnit,o=organization'. (Connection Agreement 'CAname' #1264)

CAUSE

This problem occurs if Lightweight Directory Access Protocol (LDAP) errors occur during replication between Active Directory and the Exchange Server 5.5 directory. The ADC creates duplicate objects in the Exchange Server 5.5 directory when all the following conditions are true:
  • LDAP connectivity is lost when the ADC searches for objects in the Exchange Server 5.5 directory.
  • LDAP connectivity is restored when the ADC tries to create new contacts because of the unsuccessful search for a matching object in the Exchange Server 5.5 directory.

    Note In this scenario, the unsuccessful search for a matching object in the Exchange Server 5.5 directory occurs because of the loss of LDAP connectivity.
The Exchange 2000 ADC incorrectly considers the unsuccessful search that occurs because of the loss of LDAP connectivity the same as a successful search where no matching object is found in the Exchange Server 5.5 directory.

RESOLUTION

Hotfix information

To resolve this problem, obtain the August 2004 Exchange 2000 Server Post-Service Pack 3 update rollup.

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
870540 Availability of the August 2004 Exchange 2000 Server Post-Service Pack 3 update rollup

Prerequisites

Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 3 (SP3). For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
301378 How to obtain the latest Exchange 2000 Server service pack

Restart requirement

You do not have to restart your computer after you apply this hotfix. However, the following service is automatically stopped and then restarted when you apply this hotfix:
  • Microsoft Active Directory Connector

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date         Time   Version            Size    File name
   --------------------------------------------------------------
   30-Mar-2004  23:26  6.0.6581.0        757,760  Adc.exe          

STATUS

Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server.

Properties

Article ID: 837165 - Last Review: October 26, 2013 - Revision: 2.2
APPLIES TO
  • Microsoft Exchange 2000 Server Standard Edition
Keywords: 
kbnosurvey kbarchive kbhotfixserver kbqfe kbqfe kbfix kbexchange2000presp4fix kbbug kbexchange2000presp4julybarfix KB837165

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com