You notice that there is a delay in the starting of Message Server.
Due to this reason, one or more application servers (D<nr>) are unable to establish connection to Message Server during startup.
System Log entries (transaction SM21) show that system is starting, work processes are being started, but the Dispatcher is unable to establish connection to Message Server:
Dispatcher trace file shows the error when establishing connection to Message Server:
***LOG Q0I=> NiPConnect2: <MS_host>:39<nr>: connect (xxx: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 11
(SI_ECONN_REFUSE/xxx; I4; ST; <MS_host>:39<nr>) [nixxi.cpp 3283]
NiICloseHandle: closing initial hdl 17
*** ERROR => MsIAttachEx: NiBufConnect to <MS_host>/39<nr> failed (rc=NIECONN_REFUSED) [msxxi.c 718]
***LOG Q0L=> DpLoopInit, nomscon () [dpxxdisp.c 1804]
Once the Message Server is started, Dispatcher trace file shows normal connection:
***LOG Q0K=> DpMsAttach, mscon ( <MS_host>) [dpMessageSer 1663]
DpStartStopMsg: send start message (myname is > <hostname>_<SID>_<nr> <)
DpStartStopMsg: start msg sent to message server o.k.
delay, Message Server, Failed to establish a connection to the message server, /bin/sleep, sleep , KBA , BC-CST-MS , Message Service , BC-CST-DP , Dispatcher, Task Handler , Problem
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.