When BMC Remedy<\/strong> or AREasy<\/strong> accesses the LDAP (in this case Microsoft Active Directory), either to start the server or during configuration tasks, The error shown below is similar each time there is an LDAP authentication issue.<\/p>\n “The exception is [ LDAP: error code 49 – 80090308: LdapErr: DSID-0Cxxxxxx, comment: AcceptSecurityContext error, data xxx, vece ].”<\/p>\n However, there are several values that can indicate what LDAP function is causing the issue. Here are some general references for Microsoft Active Directory:<\/p>\n The AD-specific error code is the one after “data” and before “vece” or “v893” in the actual error string returned to the binding process<\/p>\n Problem When BMC Remedy or AREasy accesses the LDAP (in this case Microsoft Active Directory), either to start the server or during configuration tasks, LDAP: error code 49 can be encountered. Symptom The error shown below is similar each time […]<\/p>\nLDAP: error code 49<\/code> can be encountered. Symptom<\/p>\n\n\n
\n 525<\/th>\n user not found<\/td>\n<\/tr>\n \n 52e<\/th>\n invalid credentials<\/td>\n<\/tr>\n \n 530<\/th>\n not permitted to logon at this time<\/td>\n<\/tr>\n \n 531<\/th>\n not permitted to logon at this workstation<\/td>\n<\/tr>\n \n 532<\/th>\n password expired<\/td>\n<\/tr>\n \n 533<\/th>\n account disabled<\/td>\n<\/tr>\n \n 701<\/th>\n account expired<\/td>\n<\/tr>\n \n 773<\/th>\n user must reset password<\/td>\n<\/tr>\n \n 775<\/th>\n user account locked<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"excerpt":{"rendered":"