ETLDP53E Bind failed, address not available during CA LDAP startup

book

Article ID: 15939

calendar_today

Updated On:

Products

CA-24X7 High-Availability Manager for DB2 for z/OS CA-Batch Processor Compile QQF CA Data Compressor for DB2 for z/OS Data Navigator for DB2 UDB for z/OS CA-DB Delivery for DB2 CA Unicenter NSM CA Log Compress DBA for DB2 Guide Online CA InfoRefiner Advantage InfoRefiner Advantage InfoRefiner Maint Upgrade CA InfoTransport Advantage InfoTransport Maint Upgrade Online Reorg for DB2 for z/OS CA RC/Update for DB2 for z/OS Query Analyzer RI Editor for DB2 for z/OS DB2 TOOLS- DATABASE MISC

Issue/Introduction

How to resolve the 'ETLDP53E Bind failed, address not available' error message during CA LDAP startup.



CA LDAP server comes up with error:

ETLDP27I CA LDAP Server load of module back_catss_utf.dll succeeded
ETLDP32I CA LDAP Server registration of module back_catss_utf.dll (15.1.2016.1115) as a null module succeeded
ETLDP00I CA LDAP Server r15.1 is starting on URL(s) <ldap://123.456.789.10:389>
ETLDP53E Bind failed, address not available
ETLDP03I CA LDAP Server r15.1 has ended

 

Environment

Release:
Component: GEN

Resolution

CA LDAP cant connect using the port and IP address specified because of a TCPIP issue.

Please make sure port 389 is not being used by another application. The port being used cannot be shared by CA LDAP. It must exclusively use it. Please contact your network person who configures TCPIP on your mainframe to see if the port is being used and what ports are free. Any port number can be used, it just has to be unused.

Can you ping the IP address and see if you get a response? If not, you need to contact your network administrator to determine why?