After an upgrade / installation procedure, one or more servers fail to start.
The most common situation for which this document applies is where we have one instance running normally and this instance is ASCS or Central Instance (The one in which message server is running) and one or more presenting errors to initialize and work correctly.
Upon checking the message server trace file (/usr/sap/<SID>/<instance>/work/dev_ms) the following entries are seen over and over:
[Thr 01] MsSSetRelInfo: client ip.addr.from.client not compatible system/client (release: 7XX / 7YY, complvl: 0/0)
7XX is the current kernel release of the message server
7YY is the current kernel release of the client trying to connect, in this case the application server with IP ip.addr.from.client
Upon checking the dispatcher trace file (/usr/sap/<SID>/<instance>/work/dev_disp) from the affected application server, the following entries can be seen:
*** ERROR => MsISnd2: not_attached [msxxi.c 1818]
***LOG Q0N=> DpSendToMs, MsSndName () [dpMessageSer 3706]
***LOG Q1K=> MsIAttachEx: compatibility check failed, Kernel not compatible with system [msxxi.c 1031]
DpMsCheck: DpMsAttach failed (-1), retry msg server attach in 1 sec
DpUpdateStatusFileWith: state=YELLOW, reason=Server in state STARTING
SAP Netweaver release independent.
KBA , BC-CST-STS , Startup Service , BC-CST , Client/Server Technology , 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.