Quantcast
Channel: Forum Microsoft Identity Manager
Viewing all articles
Browse latest Browse all 6944

Azure AD Connect - sync-generic-failure - A different entry with target identifier already exists

$
0
0

Dear,

In an Exchange Hybrid scenario, I have connected Azure AD Connect with two different Active Directories, one is the Account forest and the other is the Resource forest.

The user object which causes the error in Azure AD Connect has three connectors:
- Account forest
- Resource forest
- Azure AD

The sync error occurs on the connector from the Account forest during synchronization process.

In the following post I read that an solution approach would be to move the affected user object into an OU which is out of scope, run a delta sync, move the user object back to the original OU which is in scope, run again the delta sync: (https://social.technet.microsoft.com/Forums/en-US/9f528006-d5aa-4ca1-b873-ca802d85ad07/syncgenericfailure-error-in-adconnect?forum=ilm2) 

Unfortunately, I can't use that solution approach. I need a solution that does not require deletion of the user object.

Does anyone have an idea or similar experience?

I appreciate any help or information.

This is the stack trace from the sync error:

<extension-error-info><extension-name>SyncRulesEngine</extension-name><extension-callsite>not available</extension-callsite><extension-context>not available</extension-context><call-stack>A different entry with target identifier already exists
   at Microsoft.MetadirectoryServices.SyncRulesEngine.Server.ObjectLinkGraph.AddLink(IObjectLinkModification link, IEntryModification sourceEntry, IEntryModification targetEntry)
   at SyncManagedUtil.PopulateGraphLinks(IObjectLinkGraph graph, CMvObject* mvObject, IEntryModification csEntry, IEntryModification mvEntry)
   at ObjectNamespace.LoadLinkedTargetObjects(IObjectLinkGraph graph, IEntryModification targetMvObject)
   at Microsoft.MetadirectoryServices.SyncRulesEngine.JoinModule.LinkSourceToTarget(IEntryModification sourceObject, IEntryModification targetObject, SynchronizationRule syncRule, SyncRulePipelineArguments pipelineArguments, Boolean joiningToExistingTarget)
   at Microsoft.MetadirectoryServices.SyncRulesEngine.JoinModule.ExecuteJoinProcessingForSyncRule(IEntryModification sourceObject, SynchronizationRule syncRule, SyncRulePipelineArguments pipelineArguments, AttributeFlowModule attributeFlowModule, Guid excludedMVObjectIdWhenSearchingGraphForJoin)
   at Microsoft.MetadirectoryServices.SyncRulesEngine.JoinModule.Execute(PipelineArguments argsToProcess)
   at Microsoft.MetadirectoryServices.SyncRulesEngine.Server.SyncEngine.RunSyncPipeline(SyncRulePipelineArguments pipelineData, List`1 pipelineChain)
   at Microsoft.MetadirectoryServices.SyncRulesEngine.Server.SyncEngine.Synchronize(SynchronizationOperation operation, IObjectLinkGraph inputGraph, Boolean preview)
   at ManagedSyncRulesEngine.Synchronize(ManagedSyncRulesEngine* , CCsObject* sourceCsObject, CMvObject* mvObject, SynchronizationOperation operation, Char** error)


Viewing all articles
Browse latest Browse all 6944

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>