- During a System Copy or new system installation sapinst fails to start an instance due to an issue in the connection to the message server.
- This can happen in different steps, but most commonly this happens during the Install Instance Basics phase and in the sapinst_dev.log we have messages similar to the following:
ERROR 2015-06-10 16:25:11.605 [csistepexecute.cpp:1187]
FCO-00011 The step startASCSInstance with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|onehost|0|NW_CI_Instance|ind|ind|ind|ind|ci|0|startASCSInstance was executed with status ERROR ( Last error
reported by the step: Instance <SID>/ASCS<nn> [PARTIAL] did not start after 5:10 minutes. Giving up.).
- Looking further in the sapinst_dev.log file we also see the below message:
WException thrown: nw.msConnectException:
An exception occurred while connecting to the message server instance <SID>/ASCS<nn> on host <hostname>, port 39<nn>. DIAGNOSIS: The original exception was: wapsmod.ms.MsAttachFailed:
Connect to message server (<hostname>/<port>) failed: MSENILAYER..<br>SOLUTION: Make sure that the message server is started.
- Operating system independent
- Database independent
instance basis installation, SCS, ASCS, message server, network, niping, connection broken, NiTClientLoop, sapinst, SWPM, software provisining manager, error occurred while processing option, instance did not start after, giving up startASCSInstance setMessageIdOfExceptionMessage, nw.progress.waitingForStartFailed, ESAPinstMsgException , KBA , BC-INS , Installation Tools (SAP Note 1669327) , BC-INS-MIG , OS/DB Migrations with SWPM and DB refresh , BC-INS-NT , SAP Netweaver based Solutions on Windows , BC-INS-UNX , Installation Unix , BC-INS-FWK , sapinst and slplugin/slcb , How To
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.