Errors occurred while windows was synchronizing data

Please provide as much detail as possible. Contact our Support Team. Request Case Start Chat. Translation Feedback How can we make this translation better? Get notified about latest updates to this technical article? Yes No. Do you want to Unsubscribe? When doing so, the following errors can be returned:. When an attribute exceeds the allowed size limit, length limit or count limit set by Azure Active Directory schema, the synchronization operation results in a LargeObject or ExceededAllowedLength sync error.

Typically this error occurs for the following attributes. Azure AD does not impose limits per attribute, except for a hard-coded limit of 15 certificates in UserCertificate attribute and up to attributes for Directory extensions with a maximum of characters for each directory extension.

However, there is a size limit for the whole object so when Azure AD Connect tries to synchronize an object that exceeds this object size limit, an export error is thrown. All attributes contribute to the object's final size and some attributes have different weight multipliers due to additional processing overhead e. Additionally, different cloud services, service plans, and licenses may be assigned to the account which consumes even more attributes that also contribute to the overall size of the object.

Therefore, it's not possible to determine exactly how many entries can an attribute hold in Azure AD for example, how many SMTP addresses can fit in ProxyAddresses , because that depends on the size and multiplying factors of all the attributes populated in the object.

Below are some examples which demonstrate the different weighs of attributes like UserCertificate and ProxyAddresses:. These numbers can vary slightly. As a rule of thumb, it is safer to assume that the limit of smtp addresses in ProxyAddresses is approximately addresses to leave the room for the future growth of the object and its populated attributes. Review the user properties and remove attribute values that may no longer be required like revoked or expired certificates, outdated or unnecessary addresses SMTP, X.

An Existing Admin Role Conflict will occur on a user object during synchronization when that user object has:. Azure AD Connect is not allowed to soft match a user object from on-premises AD with a user object in Azure AD that has an administrative role assigned to it.

You can assign the administrative role to the existing user object again after the soft match between the on-premises user object and the Azure AD user object has completed. Some sources say that messing with Port is not secure. I have no clue. Was this reply helpful? Yes No. Sorry this didn't help. Thanks for your feedback. My time synchronization utility is turned on.

Community Forums. Ask a question. Personalize your experience! Personalized Community is here! Quickly customize your community to find the content you seek. Personalize Community Now.

Shahbaaz Ansari asked a question on 29 Jun AM. Hello, I am trying to create contact from outlook and set parent for the same but i am getting error "An Unknown error occurred while synchronizing data to Outlook" while saving the record.

Thanks, Shahbaaz. Replies 7 All Responses.