Skip to end of metadata
Go to start of metadata


Problem:


'LDAP Error 49' was reported when I integrated the AD domain. What is the reason?



Solution:


Please take a look on the whole error message, e.g.:


"The exception is [LDAP: error code 49 - 80090308: LdapErr: DSID-0Cxxxxxx, comment: AcceptSecurityContext error, data <HEX>, XXXX]."

The cause you will find as a hexadecimal number <HEX> after data.


Error code <HEX>Short DescriptionDescription
525LDAP_NO_SUCH_OBJECTReturned when an invalid username is supplied
52eERROR_LOGON_FAILUREReturned when a valid username is supplied but an invalid password/credential is supplied.
52fERROR_ACCOUNT_RESTRICTIONReturned when account restrictions are preventing this user from signing in.
530ERROR_INVALID_LOGON_HOURSReturned when a valid username and password/credential are supplied during times when login is restricted.
531ERROR_INVALID_WORKSTATIONReturned when a valid username and password/credential are supplied, but the user is restriced from using the workstation where the login was attempted.
532ERROR_PASSWORD_EXPIREDReturned when a valid username is supplied, and the supplied password is valid but expired.
533ERROR_ACCOUNT_DISABLEDReturned when a valid username and password/credential are supplied but the account has been disabled.
568ERROR_TOO_MANY_CONTEXT_IDSReturned when during a logon attempt, the user's security context accumulated too many security Identifiers.
701ERROR_ACCOUNT_EXPIREDReturned when a valid username and password/credential are supplied but the account has expired.
773ERROR_PASSWORD_MUST_CHANGEReturned when a valid username and password/credential are supplied, but the user must change their password immediately (before logging in for the first time, or after the password was reset by an administrator).
775ERROR_ACCOUNT_LOCKED_OUTReturned when a valid username is supplied, but the account is locked out. Note that this error will be returned regardless of whether or not the password is invalid.