No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>


To have a better experience, please upgrade your IE browser.


the solution that DSM fail to synchronize AD account

Publication Date:  2012-11-07 Views:  436 Downloads:  0
Issue Description
DSM fail to synchronize AD account, and check detailed error information, prompting "UPN is empty, sAMAccountName=xxxx, is not consistent, do not allowed to synchronize".
Alarm Information
Handling Process
Find the AD account, and manually modify the upn attribute value and sAMAccountName attribute value as the same, then synchronize again.
Root Cause
The reason might the synchronous third-party LDAP organization user attribute value UPN and sAMAccountName is inconsistent. The two attribute value of third-party LDAP (MS AD or Novell eDirectory) user object is: UPN and sAMAccountName. Now use AD user attribute to introduce.
UPN and sAMAccountName are the same by default. Because the user establishment is not standard, when the UPN and sAMAccountName value is not the same, the user will not be synchronized by DSM, and will prompt the detailed synchronous error information.