IBM Verify

IBM Verify

Join this online user group to communicate across Security product users and IBM experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only

  • 1.  Registry Direct error code HPDAA0512E?

    Posted 05/19/20 02:10 PM

    A  vendor supplied product is being installed at my company, and it needs to communicate with the internal LDAP on one of our Policy Servers. They are encountering difficulties with this, it is my best understanding that testing the network between the two entities works fine, but the application itself fails to connect.

     

    I saw a screenshot of the error message that the application produces when it tries to connect, which is as follows (I had to retype from the screen shot):

    com.tivoli.pd.rgy.ldap.LdapRgyServer.serverDown  HPDAA0512E Communication to the server xxx:636:readwrite:5 has failed.

     

    I thought that it would be easy to determine the root cause by researching the error code HPDAA0512E, but I could not find anything for this error code.

     

    Does anybody have an idea what this error code means? 

     

    Jacques Heydenrych


    CONFIDENTIALITY NOTICE: This e-mail, including any attachments, may contain confidential, privileged and/or proprietary information which is solely for the use of the intended recipient(s). Any review, use, disclosure, or retention by others is strictly prohibited. If you are not an intended recipient, please contact the sender and delete this e-mail, any attachments, and all copies.


  • 2.  RE: Registry Direct error code HPDAA0512E?

    Posted 05/20/20 01:45 AM
    Hi,

    Is this happening all the time? Then check the basics like the communication between the servers, try an ldapsearch from the command-line and so on. 
    Is this happening every now and then? Then take a look at the below link which may help. It's likely that there's things like a firewall between the ISAM and the LDAP, and that firewall may block or slow down a connection every now and then, e.g. during a reconfig.
    https://www.ibm.com/support/knowledgecenter/en/SSPREK_9.0.7/com.ibm.isam.doc/base_admin/reference/ref_conninact.html

    Kind regards, Peter.

    ------------------------------
    Peter Volckaert
    Senior Sales Engineer
    Authentication and Access
    IBM Security
    ------------------------------



  • 3.  RE: Registry Direct error code HPDAA0512E?

    Posted 05/20/20 05:26 AM

    Thank you for your response, Peter.

     

    Yes, this is happening all the time, they are still trying to install the product and has not been successful yet. The communication between the servers are working fine (as checked via a wireshark trace).

     

    This is a vendor supplied product (and server), they do not have an LDAP client installed, I will suggest that they do so. However, even if they do install an LDAP client, and it works fine (as I suspect it will), the call using what seems to be Registry Direct will still be failing with the error code HPDAA0512E, and that is really the root cause that I am trying to address.

     



    ------Original Message------

    Hi,

    Is this happening all the time? Then check the basics like the communication between the servers, try an ldapsearch from the command-line and so on. 
    Is this happening every now and then? Then take a look at the below link which may help. It's likely that there's things like a firewall between the ISAM and the LDAP, and that firewall may block or slow down a connection every now and then, e.g. during a reconfig.
    https://www.ibm.com/support/knowledgecenter/en/SSPREK_9.0.7/com.ibm.isam.doc/base_admin/reference/ref_conninact.html

    Kind regards, Peter.

    ------------------------------
    Peter Volckaert
    Senior Sales Engineer
    Authentication and Access
    IBM Security
    ------------------------------


  • 4.  RE: Registry Direct error code HPDAA0512E?

    Posted 07/07/21 01:34 AM

    Hi,

    We are facing same issue at the customer environment. Did you find the root cause of this issue and how it was resolved?

    Is this issue related to timeout mismatch of firewall and the LDAP connection timeout configured in ISAM?

    Thanks and Regards,

    Prashant Narkhede



    ------------------------------
    Prashant Narkhede
    ------------------------------

    Original Message


Related Content