-
Title
DSP: DOM2AD: No available DCs for domain, cannot process LDAP request for object -
Description
DSP: DOM2AD: No available DCs for domain, cannot process LDAP request for object -
Resolution
Issue
When performing a directory synchronization from Domino to Active Directory, you encountered an error with certain objects that failed to sync. The error is as follows:
No available DCs for domain, cannot process LDAP request for objectSolutionThe DN of an object contains the domain name, and DirSync will use this domain name to locate a DC for processing the object. In this case, there is no DN and therefore no domain so DirSync doesn’t know what DC to use (and without the DN it can’t create the object anyway). Here is the log error message typically associated with this issue. There should be a DN after the text highlighted in red.
Error during CreateObject Object DN:
Object attributes: objectClass = user unicodePwd = **** userAccountControl = 514 pwdLastSet = 0 showInAddressBook = CN=All Users,CN=All Address Lists,CN=Address Lists Container,CN=AcmeOrg,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=acmeinc,DC=com showInAddressBook = CN=Default Global Address List,CN=All Global Address Lists,CN=Address Lists Container,CN=AcmeOrg,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=acmeinc,DC=com proxyAddresses = SMTP:john.smith@contoso.com proxyAddresses = X500:/o=AcmeOrg/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=18F97ADA4849C79B00369A8085257140 targetAddress = SMTP:john.smith@domino.contoso.com mail = john.smith@contoso.com company = Acme legacyExchangeDN = /o=AcmeOrg/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=18F97ADA4849C79B00369A8085257140 givenName = FCS displayName = Forwarder5, FCS sn = Forwarder5 physicalDeliveryOfficeName = NY userPrincipalName = john.smith@contoso.com msExchPoliciesIncluded = {26491CFC-9E50-4857-861B-0CB8DF22B5D7} adminDescription = Created By DirSync
If there is no TargetDN in the BT_Person table in SQL, and no DN in the BT_PersonView, then the DN will be constructed using one of the following values from the BT_PersonView:CommonName
DisplayName
PrimaryAlias
FullName
PrimaryFullName
If any of these are null or empty in SQL, then no DN will be created and the CreateObject will fail, as above.