Symantec Access Management

  • Private Community
 View Only

  • 1.  [SmDsLdapConnMgr.cpp:720][WARNING][sm-Ldap-02900] Function prldap_set_session_option is not supported. Server :

    Posted Feb 13, 2018 11:26 AM

    We are seeing below Warning on smps.log , Could you please help to understand what this warning indicates and how to fix.

     

    Policy Server Versions

     

    CA SSO 12.52 SP01 CR08 & CA SSO 12.52 SP01 CR02

     

    [SmDsLdapConnMgr.cpp:720][WARNING][sm-Ldap-02900] Function prldap_set_session_option is not supported. Server : <AD DOMAIN>:636.
    [SmDsLdapConnMgr.cpp:720][WARNING][sm-Ldap-02900] Function prldap_set_session_option is not supported. Server : <AD DOMAIN>:636.
    [SmDsLdapConnMgr.cpp:720][WARNING][sm-Ldap-02900] Function prldap_set_session_option is not supported. Server : <AD DOMAIN>:636.
    [SmDsLdapConnMgr.cpp:720][WARNING][sm-Ldap-02900] Function prldap_set_session_option is not supported. Server : <AD DOMAIN>:636.
    [SmDsLdapConnMgr.cpp:720][WARNING][sm-Ldap-02900] Function prldap_set_session_option is not supported. Server : <AD DOMAIN>:636.
    [SmDsLdapConnMgr.cpp:720][WARNING][sm-Ldap-02900] Function prldap_set_session_option is not supported. Server : <AD DOMAIN>:636.
    [SmDsLdapConnMgr.cpp:720][WARNING][sm-Ldap-02900] Function prldap_set_session_option is not supported. Server : <AD DOMAIN>:636.
    [SmDsLdapConnMgr.cpp:720][WARNING][sm-Ldap-02900] Function prldap_set_session_option is not supported. Server : <AD DOMAIN>:636.
    [SmDsLdapConnMgr.cpp:720][WARNING][sm-Ldap-02900] Function prldap_set_session_option is not supported. Server : <AD DOMAIN>:636.
    [SmDsLdapConnMgr.cpp:720][WARNING][sm-Ldap-02900] Function prldap_set_session_option is not supported. Server : <AD DOMAIN>:636.
    [SmDsLdapConnMgr.cpp:720][WARNING][sm-Ldap-02900] Function prldap_set_session_option is not supported. Server : <AD DOMAIN>:636.
    [SmDsLdapConnMgr.cpp:720][WARNING][sm-Ldap-02900] Function prldap_set_session_option is not supported. Server : <AD DOMAIN>:636.
    [SmDsLdapConnMgr.cpp:720][WARNING][sm-Ldap-02900] Function prldap_set_session_option is not supported. Server : <AD DOMAIN>:636.
    [SmDsLdapConnMgr.cpp:720][WARNING][sm-Ldap-02900] Function prldap_set_session_option is not supported. Server : <AD DOMAIN>:636.
    [SmDsLdapConnMgr.cpp:720][WARNING][sm-Ldap-02900] Function prldap_set_session_option is not supported. Server : <AD DOMAIN>:636.
    [SmDsLdapConnMgr.cpp:720][WARNING][sm-Ldap-02900] Function prldap_set_session_option is not supported. Server : <AD DOMAIN>:636.



  • 2.  Re: [SmDsLdapConnMgr.cpp:720][WARNING][sm-Ldap-02900] Function prldap_set_session_option is not supported. Server :

    Posted Feb 13, 2018 11:40 AM

    Hi, 

     

    Refer to the below KB article :

     

    LDAP Connections manager error to our active directory user store 

     

    Regards,

    Ram,



  • 3.  Re: [SmDsLdapConnMgr.cpp:720][WARNING][sm-Ldap-02900] Function prldap_set_session_option is not supported. Server :
    Best Answer

    Posted Feb 13, 2018 10:50 PM

    Looking at that particular line of  code SmDsLdapConnMgr.cpp:720
    Policy server is trying to set option "PRLDAP_OPT_IO_MAX_TIMEOUT" - The maximum time in milliseconds to block waiting for a network I/O operation to complete.

    and LDAP (AD) is complaining that that option is not supported.

     

    Are you using AD namespace ? If yes, try using LDAP namespace and see if that makes a difference.



  • 4.  Re: [SmDsLdapConnMgr.cpp:720][WARNING][sm-Ldap-02900] Function prldap_set_session_option is not supported. Server :

    Posted Feb 14, 2018 11:49 AM

    Hi Ujwol,

     

    Thanks for the quick update. 

    Could you please help me where i can find what Name Space i am using like any configuration file.



  • 5.  Re: [SmDsLdapConnMgr.cpp:720][WARNING][sm-Ldap-02900] Function prldap_set_session_option is not supported. Server :

    Posted Feb 14, 2018 01:11 PM

    You specify that while creating user directory in Admin UI.

     

    You can not change the namespace once UD is created.

    Probably try creating new one with LDAP namespace.

     

    Sent from my iPhone