none
AD Sync Error (does not have a parent object in management agent or already exists in management agent)

    Question

  • Hi All,

    I got stuck in situation and will be really thankful, If anyone could get me out of this. I am facing issues while syncing records to Active Directory. 

    I have a FIMMA and an outbound ADMA. When I run Full sync for FIMMA, without running full import of Outbound ADMA, I get this error for ADMA sync rule:

    Microsoft.MetadirectoryServices.ProvisioningBySyncRuleException: Object "CN=ahmad.sohail,OU=Xnrel,OU=Active Xnrel Employees,OU=Entire xnrel,DC=xnrel,DC=com" does not have a parent object in management agent "Xnrel Outbound ADMA".

    But if I first run Full Import of Outbound ADMA then run full sync of FIMMA, then outbound ADMA sync rule get applied on new records but for existing records, it gave me this error below: 

    Microsoft.MetadirectoryServices.ProvisioningBySyncRuleException: An object with DN "CN=ahmad.sohail,OU=Xnrel,OU=Active Xnrel Employees,OU=Entire xnrel,DC=xnrel,DC=com" already exists in management agent "Xnrel Outbound ADMA"

    So kindly help/guide me for this scenario. 

    Thanks


    F.

    Sunday, May 13, 2018 3:30 PM

All replies

  • Hi Fahaad,

    Microsoft.MetadirectoryServices.ProvisioningBySyncRuleException: Object "CN=ahmad.sohail,OU=Xnrel,OU=Active Xnrel Employees,OU=Entire xnrel,DC=xnrel,DC=com" does not have a parent object in management agent "Xnrel Outbound ADMA".

    Please make sure that all path exists in AD. The error means that some of AD containers doesn`t exist.

    Microsoft.MetadirectoryServices.ProvisioningBySyncRuleException: An object with DN "CN=ahmad.sohail,OU=Xnrel,OU=Active Xnrel Employees,OU=Entire xnrel,DC=xnrel,DC=com" already exists in management agent "Xnrel Outbound ADMA"

    You should configure your ADMA on Configure Join and Projection Rules. Specify Join rule using some attribute. For example, in your case it can be CN or accountName.


    Emil Valiev

    Tuesday, May 15, 2018 1:20 PM