Symptom
Upgrade using Software Update Manager (SUM) stops in START-AS-JAVA phase with following error.
-
START-AS-JAVA_XX.LOG:
Jul 3, 2017 9:05:15 AM [Info ]: Command line: E:\usr\sap\<SID>\J00\exe\sapcontrol -nr 0 -host <hostname> -user <SID>adm <SecureField> -prot NI_HTTP -function WaitforStarted 7200 5
Jul 3, 2017 9:05:15 AM [Info ]: Standard out: E:\usr\sap\<SID>\SUM\sdt\log\SUM\SAPCONTROL_WAITFORSTARTED_0_02.OUT
Jul 3, 2017 9:05:15 AM [Info ]: Process ID 1633 has been started.
Jul 3, 2017 9:05:15 AM [Info ]: Waiting for process ID 1633, name sapcontrol to finish.
Jul 3, 2017 9:05:25 AM [Info ]: Process ID 1633, name sapcontrol has been finished, exit code 2.
Jul 3, 2017 9:05:25 AM [Error ]: Return code condition success evaluated to false for process sapcontrol for action wait for started.
Jul 3, 2017 9:05:25 AM [Error ]: The following problem has occurred during step execution: com.sap.sdt.util.diag.DiagException:
Could not start SAP instance with number 0.Could not check if the instance number 0 on host <hostname> is started.
Sapcontrol client could not perform action wait for started on instance 0Return code condition success evaluated to false for process sapcontrol for action wait for started.
-
SAPCONTROL_WAITFORSTARTED_0_02.OUT:
03.07.2017 09:05:25
WaitforStarted
FAIL: j2ee process server0 failed
- \usr\sap\<SID>\<instance>\work\std_server0.out
Service [p4] start ================= ERROR =================
CSN Component [BC-JAS-COR-RMT], DC Name [sap.com/p4]
com.sap.engine.frame.ServiceConfigurationException: P4 core service could not start because of missing or wrong port configuration. Check ICM configuration and logs.
Check that configured (or default) port for RMI-P4 protocol is not occupied.
at com.sap.engine.services.rmi_p4.server.P4ServiceFrame.start(P4ServiceFrame.java:199)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)
FATAL: Critical shutdown with exit code [-2106] was requested due to [AS Java cannot be started; core service [p4] failed to start because of incorrect configuration
[P4 core service could not start because of missing or wrong port configuration.
Check ICM configuration and logs. Check that configured (or default) port for RMI-P4 protocol is not occupied. ]]
-
dev_icm:
[Thr 1668] Started service PORT=50001,PROT=HTTPS,TIMEOUT=60,PROCTIMEOUT=600,VCLIENT=1
[Thr 1668] SSL settings: verify_client: 1, cache_size: -1, cache_lifetime: -1, credfile: SAPSSLS.pse, ciphers: default, alpn:-
[Thr 1668] *** ERROR => IcmBindService: NiHostToAddr failed for 127.0.0.1:xxx.xxx.xxx.xxx (rc=-2) [icxxserv.c 3943]
[Thr 1668] *** WARNING => IcmAddService: Could not start service (rc=-1) HOST=127.0.0.1:xxx.xxx.xxx.xxx ,PORT=50004,PROT=P4,TIMEOUT=60,PROCTIMEOUT=60 [icxxserv.c 1375]
[Thr 1668] *** ERROR => IcmBindService: NiHostToAddr failed for 127.0.0.1:149.204.246.106 (rc=-2) [icxxserv.c 3943]
[Thr 1668] *** WARNING => IcmAddService: Could not start service (rc=-1) HOST=127.0.0.1:149.204.246.106,PORT=50006,PROT=P4SEC,TIMEOUT=60,PROCTIMEOUT=60,VCLIENT=1 [icxxserv.c 1375]
[Thr 1668] Started service PORT=50007,PROT=IIOP,TIMEOUT=60,PROCTIMEOUT=60
[Thr 1668] Started service PORT=50003,PROT=IIOPSEC,TIMEOUT=60,PROCTIMEOUT=60,VCLIENT=1
Read more...
Environment
- Software Update Manager (SUM)
- SAP NetWeaver AS JAVA
Product
Keywords
SUM, start, JAVA, upgrade, update, start, startup, ICM, bindhost, update, Software Update Manager, P4, icm/server_port_X, AS Java cannot be started, j2ee process server0 failed, P4 core service could not start, Could not start SAP instance, P4 core service could not start, 2106, dev_icm, IcmBindService: NiHostToAddr failed , KBA , BC-UPG-TLS-TLJ , Upgrade tools for Java , 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.
SAP Knowledge Base Article - Preview