Forum Discussion
Synchronization errors in your directory
None of the solutions mentioned in the article were able to resolve the issue unfortunately. My issue is the proxyAddresses. Its currently in use by two user accounts. The only place i can see the old user account is in Synchronization Service Manager.
If you're absolutely certain the object no longer exists in Azure AD - including the recycle bin (aka the object is still in its soft-deleted state) then there's only two possibilities as to why it's showing in miisclient.exe:
- Exists as a new projected addition to Azure AD;
- The connector space is no longer in sync with Azure AD.
If you select the Azure AD connector under the Connectors tab, it states near the top if the operation type is "Add", and the attributes themselves will be a dead giveaway since all their change types will also be "Add".
I'm not expecting it will be an add meaning I won't go into this scenario further, but let us know if it is.
If it's the second issue - which is also quite unusual, you will need to run a "Full Import" operation on the Azure AD connector to remove any orphaned connector space objects.
Cheers,
Lain
- Hi there Lain,
Thank you for the response. In my case, the connector was showing as Pending Export, and all of the change types were set to Add.
What we end up doing is running a full import on the Azure AD connector then we ran a full Sync. We then refreshed the front end and we are no longer getting the duplicate attribute synch error.
Thank you again for your assistance!Good to hear it's resolved.
The full sync is what removes the object from the connector space, where the sync, kind of "acknowledges" that it's gone.
If you get orphans like that, a full sync should always be your first action item (since a delta will not reset the connector space).
If that doesn't work, there is a commandlet within the ADSync PowerShell module that will allow you to delete a single item, but it should not be the first thing you try since if the connector space is more broadly unhealthy, it does nothing to resolve that underlying issue.
Cheers,
Lain
