Symantec Access Management

 View Only
  • 1.  Status: Error 49 . Invalid credentials

    Posted Jan 03, 2023 04:05 AM
    Hi All,

    Does anyone have experienced with repetitive error "[SmDsLdapConnMgr.cpp:916][ERROR][sm-Ldap-01370] SmDsLdapConnMgr Bind. Server : 389. Error 49-Invalid credentials" in smps logs?
    Whenever above error appears, it will automatically restart the policy server and creating a file name smps.crash.pstack_
    After the server restarted, the invalid error still appears, and the issue only resolve after updating the password of AD account to the same password.

    Does anyone know what causes the issue and how we can avoid this error again?

    Thank you,
    Atifah


  • 2.  RE: Status: Error 49 . Invalid credentials

    Posted Jan 04, 2023 10:13 PM
    Hi,

    Does anyone experience this issue?

    Regards,
    Atifah


  • 3.  RE: Status: Error 49 . Invalid credentials

    Broadcom Employee
    Posted Jan 05, 2023 07:19 PM
    Edited by Peter Burant Jan 05, 2023 07:19 PM

    Hi Atifah,

    The error 49 appearing in the smps.log is not in itself indicative of a problem as this will occur any time a user provides invalid credentials during a login attempt.  The other situation in which the error may get logged is when the policy server provides incorrect credentials when attempting to bind to one of its stores.   From the symptoms, I suspect the error 49 in question to be the latter and related to the policy server attempting to connect to one of its stores.  The policy server trace log would provide more detail about the request that resulted in the error.

    Regardless of the reason for the error 49, the policy server should not crash, thus I would recommend opening a support case to troubleshoot the crash.   Support will need you to gather a core dump and run the pkgapp script against it.

    If you're not running the latest release, you can also take a look at the release notes for the subsequent releases to see if this crash condition has perhaps been addressed.  The latest release is 12.8 SP7 (12.8.7).  Do note that if the policy server either cannot connect to the Key Store, or loses the connection to the Key Store, the policy server will shut down (the smexec process will restart it up to 5 times by default).   

    Regards,
    Pete