Sync Error 114 with no display name or object type

Question

Sync Error 114 with no display name or object type

Jim Paradis 101

We are getting a Sync error 114 where there is no display name or object type. All I have to go on is a GUID. The sync status is on-prem AD only. How do I go about finding the problem? I don't know the account for the GUID.

Thanks,
Jim

Other Error
.onmicrosoft.com
Description The object failed synchronization. For more information, please see the error details. If the problem continues and cannot be fixed, please contact Microsoft Support.

Error Details

Property

Value
Error Type

114
Last Attempted At

10/25/2021, 11:00:06 AM

Related Articles: 1. Azure AD Connect: Troubleshooting Synchronization Errors

Attribute

Attribute Value
User Principal Name

Object GUID

91c46d1b-2f2f-4487-abe0-689c01f07593
Synchronization Status

On premises AD only

Marilee Turscak-MSFT 37,206 Reputation points Microsoft Employee Moderator

2021-10-25T18:32:21.727+00:00

Multiple customers have been reporting this issue over the past few days. The regular solution to this error is to delete any cloud-only users that previously existed in Active Directory, but since you are not getting enough information to identify the users, that solution doesn't work.

I've reached out to the product team and reported the issue. It sounds like it could be a bug with the new Azure AD Connect.

You might be able to find it by checking for a MachineID error, but that is not a guarantee.

I'll let you know when I have a response from the product team.
Jim Paradis 101 Reputation points

2021-10-25T18:34:04.47+00:00

Ok, thanks for your help.
Marilee Turscak-MSFT 37,206 Reputation points Microsoft Employee Moderator

2021-10-27T00:36:25.37+00:00

If you open the Synchronization Service Manager on the connecter PC , find the error, and click on it, are you able to see the user name? If so, you can find the user in AAD and delete it.
Marilee Turscak-MSFT 37,206 Reputation points Microsoft Employee Moderator

2021-10-27T00:36:58.517+00:00

I'm still waiting on a response from the PG, but saw in another thread that users were able to resolve this by checking the Synchronization Service Manger error.

Accepted answer

2 additional answers

Your answer

Marilee Turscak-MSFT 37,206 Reputation points Microsoft Employee Moderator

2021-10-25T18:32:21.727+00:00

Multiple customers have been reporting this issue over the past few days. The regular solution to this error is to delete any cloud-only users that previously existed in Active Directory, but since you are not getting enough information to identify the users, that solution doesn't work.

I've reached out to the product team and reported the issue. It sounds like it could be a bug with the new Azure AD Connect.

You might be able to find it by checking for a MachineID error, but that is not a guarantee.

I'll let you know when I have a response from the product team.
Jim Paradis 101 Reputation points

2021-10-25T18:34:04.47+00:00

Ok, thanks for your help.
Marilee Turscak-MSFT 37,206 Reputation points Microsoft Employee Moderator

2021-10-27T00:36:25.37+00:00

If you open the Synchronization Service Manager on the connecter PC , find the error, and click on it, are you able to see the user name? If so, you can find the user in AAD and delete it.
Marilee Turscak-MSFT 37,206 Reputation points Microsoft Employee Moderator

2021-10-27T00:36:58.517+00:00

I'm still waiting on a response from the PG, but saw in another thread that users were able to resolve this by checking the Synchronization Service Manger error.

Answer 1

Jim Paradis 101

I found this post from a similar issue. It helped me fix the issue in the Sync Service Manager on prim.

NorbertdeGraaf-2314 avatar image
0 Votes" 0
NorbertdeGraaf-2314 answered • 7 days ago

MS got back to me, I opened the Synchronization Service Manager on the connecter PC and found the error and clicked on it – this showed the username and although that user was deleted from AD, it was still present on AAD, I hard deleted the user and the sync shows no errors, problem solved, thanks

https://learn.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-sync-service-manager-ui-connectors

Marilee Turscak-MSFT 37,206 Reputation points Microsoft Employee Moderator

2021-11-02T17:43:58.43+00:00

Thanks for confirming!
Jamal Mercier-Hall 0 Reputation points

2023-07-21T20:15:46.8133333+00:00

I can understand how this would resolve the issue, however we have a policy here to convert the AAD account to a shared mailbox... which means we cannot delete the "user".

Is there a proposed solution for a case such as mine?

Answer 2

Marilee Turscak-MSFT 37,206 Microsoft Employee Moderator

The product group has been informed of this and the documentation has been updated. The error states the objectID so the object can be found and the display name should be on the pending export tab. The error states that Delete is not valid, so it is a deletion access violation documented here:
https://learn.microsoft.com/en-us/azure/active-directory/hybrid/tshoot-connect-sync-errors#deletion-access-violation-and-password-access-violation-errors

Also, if you open the Synchronization Service Manager on the connecter PC, find the error, and click on it, you should be able to find the user that way.

Let me know if this helps!

Marilee Turscak-MSFT 37,206 Reputation points Microsoft Employee Moderator

2021-11-02T17:27:49.06+00:00

Following up to share the solution in this related thread:

You can set ImmutableId as $null such as: Set-MsolUser -UserPrincipalName testuser5@keyman .com -ImmutableId "$null"
IT Admin 11 Reputation points

2021-11-17T15:09:18.06+00:00

having same issue however the display name is not visible in the synch service manager

Answer 3

Vishal Bakshi 76

The user name/details does not show in synchronisation service manager? Any MS gurus here who can help ?

Share via

Sync Error 114 with no display name or object type

2 additional answers

Your answer