2439572 - Dialog instance(s) fail to start while ASCS works normally

Dialog instance cannot be brought online. It is important to inform that by "dialog instance" this document mean any instance other than ASCS (message server + enqueue server).

After each attempt to launch the affected instance, the dispatcher trace, dev_disp, is updated. Deeper investigation at dev_disp shows the following entries:

*****************************************************************************
* LOCATION SAP-Dispatcher servername_SID_00 on host servername
* ERROR mserrno received (MSEACCESSDENIED)
*
* TIME Mon Mar 6 14:54:33 2017
* RELEASE 749
* COMPONENT MS (message handling interface, multithreaded)
*****************************************************************************
*** ERROR => Not allowed to connect to message server via port 3901 [dpMessageSer 1841]
*** ERROR => Please check your configuration (profile parameter rdisp/msserv_internal) [dpMessageSer 1842]

The analysis is moved to the Message Server process (running on ASCS instance). Upon checking the message server trace, dev_ms, the following entries are confirmed:

[Thr 140626887612192] *** ERROR => MsInitAclInfo: /usr/sap/SID/SYS/global is empty, no attach of application server possible [msxxacl.c 760]

(...)

[Thr 140626887612192] *** ERROR => MsSLoginClient: client servername_SID_00 (<IP from the affected instance>) is not in acl list, access denied [msxxserv.c 5583]

• System management
• Startup failure
• System down situation

startup, production down, system fail, cannot start, system offline, starting issue , KBA , BC-CST-STS , Startup Service , BC-CST-MS , Message Service , Problem