Blog Post

Core Infrastructure and Security Blog
6 MIN READ

Deleting a Connector Space: When, Why and How

ktackett's avatar
ktackett
Icon for Microsoft rankMicrosoft
Nov 01, 2019
First published on MSDN on Oct 15, 2014 *** PLEASE NOTE: This post is explicitly intended for use with on-prem (FIM/MIM) only and is NOT for use with AAD Connect. Following this process wit...
Updated Feb 20, 2020
Version 3.0
KrisTackett
Deleted's avatar
Deleted
Dec 03, 2022

we are getting some errors in our MIM after deleting the connector space 972529, but the objects do not join and MIM thinks all users are new users with a DN that's already in use.

How do we clean up these errors?

Users in Metaverse have two connectors one to the SQL server and the DN is a number, and one to the FIM where the DN is the username. Is this normal?

 

FIM Service Management agent

synchronization error

ambiguous-import-flow-from-multiple-connectors

 

SQL server
error

sync-rule-flow-provisioning-failed

Microsoft.MetadirectoryServices.ProvisioningBySyncRuleException: An object with DN "CN= ,OU= ,OU= ,OU= ,DC= ,DC= ,DC= " already exists in management agent "AD".

 

The users are imported from an XML file and already exists in AD and are not new users with the same DN.

 

The operation failed because UPN value provided for addition/modification is not unique forest-wide