XADM: The Recipient Update Service Does Not Work in an Environment That Contains More Than 800 Domain Controllers (316350)
The information in this article applies to:
- Microsoft Exchange 2000 Server
This article was previously published under Q316350 IMPORTANT: This article contains information about modifying the registry. Before you
modify the registry, make sure to back it up and make sure that you understand how to restore
the registry if a problem occurs. For information about how to back up, restore, and edit the
registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
SYMPTOMS
In a Microsoft Windows 2000 forest that contains more than 800 domain controllers, the Exchange 2000 Recipient Update Service may not run properly, and may log an error message that is similar to the following:
Event Type: Error
Event Source: MSADC
Event Category: LDAP Operations
Event ID: 8270
Date: 12/3/2001
Time: 4:33:51 AM
User: N/A
Computer: PARSIFAL
Description:
LDAP returned the error [b] Administration Limit Exceeded when importing the transaction dn: CN=Recipient Update Service (DOMAIN),CN=Recipient Update Services,CN=Address Lists Container,CN=Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=com changetype: Modify msExchServer1HighestUSN:1696357 msExchServer1HighestUSNVector:SERVER1:1868357 : SERVER2:2097926 : SERVER3:1696357 : SERVER4:3289482 : SERVER5:3493342 : SERVER6:3523081 : ...
NOTE: The event description contains all of the domain controller names (more than 800 names).
CAUSE
This problem can occur because there is an architectural limit of approximately 800 values (that are not distinguished name-linked) in a multivalued attribute in the Windows 2000 Active Directory. When there are more than 800 domain controllers, the Recipient Update Service attempts to update the msExchServer1HighestUSNVector attribute with the name and update sequence number (USN) number of each domain controller, which does not work because of the architectural limitation.
RESOLUTIONTo 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:
301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
The English version of this fix should have the following file attributes or later:
Component: Directory
NOTE: Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 2.
STATUSMicrosoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 3.
Modification Type: | Minor | Last Reviewed: | 6/6/2003 |
---|
Keywords: | kbbug kberrmsg kbExchange2000preSP3fix kbExchange2000sp3fix kbfix KB316350 |
---|
|