Connector Space Object; Error Code 8344

Sal Vizcarra 21 Reputation points
2022-07-13T15:28:09.963+00:00

We keep running into this error after migrating to a new AD Connect Server. We have verified the service account has inheritance enabled!

Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
18,624 questions
{count} votes

Accepted answer
  1. Danny Zollner 9,391 Reputation points Microsoft Employee
    2022-07-13T15:48:27.643+00:00

    The error code 8344 indicates a permission issue when performing a write operation on an object. You mentioned that the service account being used has inheritance disabled - that may not be relevant, however, as the object that you need to check is the one that the error is being generated on. If inheritance is enabled on the object, it may be disabled on an OU that the object is contained in.

    First, check the pending export of the object in AAD Connect to see what change is being attempted. After that, you can open the advanced security settings on the object in Active Directory Users and Computers to see what permissions are applied to it. If you see the on-premises Active Directory service account listed, ensure that the specific permission needed (i.e.: write proxyAddresses) exists. If it doesn't, it could be that the permissions just don't exist - you can check the object generating the error or the OU that it is contained in to see if the necessary permissions exist. Inheritance has to be turned on not only on the object being modified, but also on any OUs it is contained in if the permission is not applied to that OU or object directly. As an example, sometimes permissions are applied to the root of the domain (e.g.: DC=Contoso,DC=com) and inherit down. If there are nested OUs between the root and the object generating the error, a single OU in the path between that object and the point where the permission is applied (root of domain in this example) not having inheritance disabled would cause the permissions to not inherit past that point.

    If all else fails - I'd suggest opening a support case, this is a fairly common problem and a support engineer for Azure AD Connect should be able to assist you.

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful