Article ID: 837968
Article Last Modified on 10/25/2007
APPLIES TO
- Microsoft Exchange Server 2003 Enterprise Edition
- Microsoft Exchange Server 2003 Standard Edition
SYMPTOMS
Duplicate users may appear in the Exchange global address list after you configure the Microsoft Exchange Server 2003 Active Directory Connector (ADC). This problem occurs after you configure the ADC to do the following:
- To replicate information from Microsoft Exchange Server 5.5 to the Active Directory directory service
- To replicate information from the Active Directory directory service to the Exchange Server 5.5 directory
Additionally, one or more events that are similar to the following are logged in the Application event log on the computer that is running the ADC service.
Note Some of the following events use the same event ID number, but the description in the event is different.
Event 8020
Event ID: 8020
Event Type: Warning
Event Category: LDAP Operations
Event Source: MSADC
Description: LDAP Search of directory Directory name at base 'cn=Recipients,cn=Recipients,ou=Organizational unit,o=Organization' using filter '(objectclass=*)' was unsuccessful. Directory returned the LDAP error:[0x51] Server Down.
Event 8024
Event ID: 8024
Event Type: Error
Event Category: LDAP Operations
Event Source: MSADC
Description: LDAP Search Initial Page on directory Directory name at base 'o=Organization' with filter '(msExchADCGlobalNames=NT5:GUID*)' was unsuccessful. Directory returned the LDAP error:[0x51] Server Down.
Event 8024
Event ID: 8024
Event Type: Error
Event Category: LDAP Operations
Event Source: MSADC
Description: LDAP Search Initial Page on directory Directory name at base 'o=Organization' with filter '(distinguishedName=cn=Recipients,ou=Organizational unit,o=Organization)' was unsuccessful. Directory returned the LDAP error:[0x51] Server Down.
Event 8270
Event ID: 8270
Event Type: Error
Event Category: LDAP Operations
Event Source: MSADC
Description: LDAP returned the error [44] Already Exists when importing the transaction dn: cn=User name,cn=Recipients,cn=Recipients,ou=Organizational unit,o=Organization changetype: Add admin-display-name:User name distinguishedname:OU=User name,cn=Recipients,cn=Recipients,ou=Organizational unit,o=Organization createtimestamp:20030327164659.0Z objectguid:GUID replication-signature:GUID msexchadcglobalnames:forest:o=Organization GUID : EX5:cn=User name,cn=Recipients,ou=Organizational unit,o=Organization:container$to... : NT5:GUID : FOREST:GUID container-info:-2147483647 ReplicatedObjectVersion:0
Event 8271
Event ID: 8271
Event Type: Information
Event Category: Replication
Event Source: MSADC
Description: Successfully replicated the object 'OU=Recipients,OU= Organizational unit,OU=Recipients,DC= corp,DC=contoso ,DC=com' to object 'cn=Recipients,cn=Recipients,ou=Organizational unit,o=Organization'.
Event 8271
Event ID: 8271
Event Type: Information
Event Category: Replication
Event Source: MSADC
Description: Successfully replicated the object 'CN=User,OU=User name,OU=Recipients,OU=Organizational unit,OU=Recipients,DC=corp,DC=contoso,DC=com' to object 'cn=User name,cn=Recipients,cn=Recipients,ou=Organizational unit,o=Organization'. (Connection Agreement 'Connection agreement name' #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 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 The unsuccessful search for a matching object in the Exchange Server 5.5 directory occurs because of the loss of LDAP connectivity.
The Exchange 2003 ADC interprets the following kinds of search results as equivalent:
- Unsuccessful searches that occur because of a loss of LDAP connectivity
- Successful searches that do not find a matching object in the Exchange Server 5.5 directory
RESOLUTION
Hotfix information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Exchange Server 2003 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
Prerequisites
Because of file dependencies, this hotfix requires Microsoft Exchange Server 2003 Service Pack 1. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
836993 How to obtain the latest service packs for Exchange Server 2003
Restart requirement
You do not have to restart your computer after you apply this hotfix. However, the Active Directory Connector service is automatically stopped and then restarted when you apply this hotfix.
File information
The English version of this hotfix has the file attributes (or later file attributes) 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 -------------------------------------------------------------- 29-Jun-2004 00:58 6.5.7232.6 697,344 Adc.exe
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
837165 Duplicate users occasionally appear in the global address list in Exchange 2000 Server
Additional query words: ldap adc XADM
Keywords: kbhotfixserver kbqfe kbhotfixserver kbqfe kbqfe kbexchdirectory kbfix kbbug KB837968
