SAP Knowledge Base Article - Preview

2370268 - Message Server didn't start up successfully

Symptom

  • When starting SAP ERP system, Message Servier didn't start up successfully.
  • Developer trace for Message Server(ms_dev)

        [Thr <thread ID>] ***LOG Q01=> MsSInit, MSStart (Msg Server X XXXXX) [msxxserv.c XXXXX]
        [Thr <thread ID>] SigISetDefaultAction : default handling for signal SIGCHLD
        [Thr <thread ID>] *** ERROR => MsSCommInit: NiBufListen(sapms<SID>) (rc=NIESERV_UNKNOWN) [msxxserv.c XXXXX]
        [Thr <thread ID>] *** ERROR => MsSInit: MsSCommInit [msxxserv.c XXXX]
        [Thr <thread ID>] *** ERROR => MsSInit failed, see dev_ms.new for details [msxxserv.c XXXX]
        [Thr <thread ID>] Server state SHUTDOWN
        [Thr <thread ID>] ***LOG Q02=> MsSHalt, MSStop (Msg Server 3100) [msxxserv.c XXXX]
        [Thr <thread ID>] Good Bye .....


Read more...

Environment

  • SAP ABAP System

Product

SAP ERP Central Component 6.0

Keywords

NiPGetServByName, getaddrinfo, WSATYPE_NOT_FOUND , KBA , BC-CST-MS , Message Service , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.