LDAP STC cannot started
search cancel

LDAP STC cannot started

book

Article ID: 111641

calendar_today

Updated On:

Products

Compliance Event Manager

Issue/Introduction

error messageĀ daemon: bind(6) failed errno=111 (EDC5111I Permission denied.)

Got problem when start CEMELDAP stc, got ended with RC=256,
but no error messages found:
output as: 12.59.25 STC07742 ---- THURSDAY, 16 AUG 2018 ---- 12.59.25 STC07742 IEF695I START CEMELDAP WITH JOBNAME CEMELDAP IS ASSIGNED TO USER CEMSTC , GROUP CAI 12.59.25 STC07742 $HASP373 CEMELDAP STARTED 12.59.25 STC07742 IEF403I CEMELDAP - STARTED - TIME=12.59.25 12.59.30 STC07742 ETLDP21I CA LDAP Server is starting 020 12.59.31 STC07742 ETLDP27I CA LDAP Server load of module back_cemdc_utf.dll succeeded 12.59.32 STC07742 ETLDP40I CA LDAP Server load of module CADCDC32 succeeded 12.59.32 STC07742 ETLDP40I CA LDAP Server load of module CADCPP32 succeeded 12.59.32 STC07742 ETLDP40I CA LDAP Server load of module CADCDB32 succeeded 12.59.32 STC07742 ETLDP40I CA LDAP Server load of module CADCMF32 succeeded 12.59.33 STC07742 ETLDP40I CA LDAP Server load of module libcci.so succeeded 12.59.33 STC07742 ETLDP32I CA LDAP Server registration of module back_cemdc_utf.dll (15.1.2016.0801) as a null module succeeded 12.59.34 STC07742 ETLDP00I CA LDAP Server r15.1 is starting on URL(s) 12.59.34 STC07742 ETLDP03I CA LDAP Server r15.1
has endedĀ 

Environment

z/os

Resolution

I found another example of the cause of this message
daemon: bind(6) failed errno=111 (EDC5111I Permission denied.)

Port 389 was not defined in TCPIP for the ldap STC