Microsoft KB Archive/305148

= XADM: ForestPrep Causes Constraint Violations When You Replicate Exchange Server 5.5 Directory Objects =

Article ID: 305148

Article Last Modified on 2/20/2007

-

APPLIES TO


 * Microsoft Exchange 2000 Server Standard Edition

-



This article was previously published under Q305148



SYMPTOMS
Setup completes correctly, however, the Active Directory Connector.log file and the event log may contain some &quot;Constraint Violation&quot; errors that appear similar to the following:

[15:10:58] (3221233742) LDAP returned the error [13] Constraint Violation when importing the transaction dn: CN=Connector for Lotus Notes (Server1),cn=Connections,CN=Site,CN=Routing Groups,CN=Company,CN=Administrative Groups,CN=Company,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=root,DC=company,DC=com

changetype: Add

admindisplayname:Connector for Lotus Notes (Server1)

legacyexchangedn:/o=Company/ou=EXCH1/cn=Configuration/cn=Connections/cn=SERVER1-LME-NOTES

homemdb:CN=Mailbox Store (Server1),CN=First Storage Group,CN=InformationStore,CN=EX...

homemta:CN=Microsoft MTA,CN=Server1,CN=Servers,CN=Company,CN=Administrative Groups,C...

deliverymechanism:2

routinglist:NOTES:*;1

canpreservedns:TRUE

computername:Server1 -



CAUSE
When the temporary Configuration Agreement is set up during ForestPrep, the Active Directory Connector (ADC) attempts to replicate objects from the Microsoft Exchange Server 5.5 directory. If an object fails to replicate, the ADC will try again later. If this second replication attempt fails, the temporary Connection Agreement does not attempt further replications with this object.

In the case of the Constraint Violation error, the Active Directory Connector.log file and network traces taken during ForestPrep show the second attempt failing with the following error message:

LDAP returned the error [0] Success when importing the transaction.

You can see from the traces that the ADC is failing to set an attribute on an object. The ADC is trying to set the value of that attribute to an object that does not yet exist in Active Directory, which consequently generates a Constraint Violation.



RESOLUTION
When Exchange 2000 Setup is continued, it establishes a permanent Configuration Agreement. After this occurs, the objects that are encountering the Constraint Violation will eventually replicate. This replication will occur properly, because the ADC eventually replicates the target object, and the object that is failing will be able to find the target of its attribute on the next replication cycle.



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

Additional query words: exch2kp2w

Keywords: kbbug kberrmsg kbpending KB305148

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.