Synchro Error - Group An Object with DN Already Exists in Management Agent

Hello, 

i have this error when i try a synchro in FIM MA , 

An object DN  with DN already exists in Management Agent AD. 

The object was imported by the AD connector but i don't find the DRE related to the object in the Metaverse. It's weird ??

Any idea ?? 

Thanks

June 12th, 2014 5:45am

Hello,

The group in AD CS is still connected to an object is the metaverse?

Generally, this error appears when you try to create an object in a CS but an other object exists with the same anchor (DN for AD). You need to join the group from AD to the Metaverse Object (If it's not present, disabled the provisioning by SR and run Full/Delta Synchro on FIM MA)

Regards,

Free Windows Admin Tool Kit Click here and download it now
June 12th, 2014 5:56am

Agreed with Sylvian. Create Join rule that would identify the same group on both sides (Metaverse and AD MA) and then run Delta Import -> Full Synchronization on AD MA agent. (Delta should also work, but as you have changed agent's configuration, you should do FS at least once :) )
June 12th, 2014 6:08am

Thanks , the join rule was OK, it is a data problem and incoherence. 

Thanks.

Free Windows Admin Tool Kit Click here and download it now
June 12th, 2014 9:18am

Hello,

The group in AD CS is still connected to an object in the metaverse?

Generally, this error appears when you try to create an object in a CS but an other object exists with the same anchor (DN for AD). You need to join the group from AD to the Metaverse Object (If it's not present, disabled the provisioning by SR and run Full/Delta Synchro on FIM MA)

Re

June 12th, 2014 12:47pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics