Last updated on JUNE 16, 2017
Applies to:Oracle Communications ASAP - Version 4.2.0 to 7.2.0 [Release 4.2 to 7.2]
Information in this document applies to any platform.
***Checked for relevance on 01-NOV-2012***
Why does BIND_ERR appear in ASAP's diagnostic file on occasions?
What does this error mean?
What do we need to do if BIND_ERR appeared in ASAP diag files?
104342.399:8: LOW:RPC Param :1377:control/libasc/ctlib.c
Sending RPC [log_event] with 6 Parameters
1 : appl_cd = NEP_ASAP
2 : file = sarm/libnep/sess_mgr.c
3 : reason = [N_NETOP-JAX_RPC_1_CONNECTION]: No Ports Available to NE - either already Bound
4 : line = 3103
5 : event = BIND_ERR
6 : event_log = 1
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms