Microsoft KB Archive/305207

= XADM: ADC Tries to Set a Connector's &quot;homemdb&quot; Attribute to the Incorrect Object =

Article ID: 305207

Article Last Modified on 2/20/2007

-

APPLIES TO


 * Microsoft Exchange 2000 Server Standard Edition

-



This article was previously published under Q305207



SYMPTOMS
When you run Exchange 2000 Setup, Setup finishes; however, the Active Directory Connector.log file and the event log may contain some &quot;Constraint Violation&quot; error messages that are 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 -

When this occurs, the homemdb attribute may be incorrect. For example, the Active Directory Connector (ADC) may try to set the connector's attribute to the following:

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

Later, in the Active Directory Connector log, the target attribute eventually replicates as follows:

[15:11:09] (1073750095) Successfully replicated the object 'cn=Microsoft Private MDB,cn=Server1,cn=Servers,cn=Configuration,ou=SERVER,o=SITE' to object 'CN=Private Information Store (Server1),CN=First Storage...



CAUSE
This issue can occur if a connector object is being replicated and the target that the homemdb attribute is set to does not exist. Exchange 2000 attempts to build a homemdb attribute, but because that object does not exist yet, Exchange 2000 might form the name of the attribute incorrectly, and then the attribute cannot be created.



RESOLUTION
To resolve this issue, continue Setup to create the permanent configuration Connection Agreement; this enables replication to continue.



MORE INFORMATION
For additional information about this problem and its resolution, click the article number below to view the article in the Microsoft Knowledge Base:

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

If X.400 connectors exist in the environment, the X.400 connectors successfully replicate because they do not require that a homemdb attribute be set.

Additional query words: connectors homemdb ADC

Keywords: kbprb KB305207

-

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

© Microsoft Corporation. All rights reserved.