SAP Knowledge Base Article - Preview

2414774 - Software Update Manager (SUM) fails to start the J2EE stack in the step START-AS-JAVA for Dual Stack Upgrade to Target Release >= NW 7.1

Symptom

  • Software Update Manager (SUM) throws the below error in the step START-AS-JAVA (Logfile: <Path to SUM>/SUM/sdt/log/SUM/START-AS-JAVA_XX.LOG)
Apr 19, 2017 8:07:53 PM [Error ]: The following problem has occurred during step execution: com.sap.sdt.util.diag.DiagException: Could not start SAP instance with number <source instance number>.
Could not check if the instance number <source instance number> on host <PAS host> is started.
Sapcontrol client could not perform action wait for started on instance <source instance number>
Return code condition success evaluated to false for process sapcontrol for action wait for started
  • The SAPCONTROL_WAITFORSTARTED_<source instance number>_XX.OUT in the location <Path to SUM>/SUM/sdt/log/SUM throws the below error:
19.04.2017 20:07:53
WaitforStarted
FAIL: Timeout
  • The SAPCONTROL_GETPROCESSLIST_<source instance number>_XX.OUT in the location <Path to SUM>/SUM/sdt/log/SUM shows no processes:
19.04.2017 18:07:53
GetProcessList
OK
name, description, dispstatus, textstatus, starttime, elapsedtime, pid

 


Read more...

Environment

  • Upgrade of Dual Stack System with SUM
  • Source release < 7.1
  • Target >= NW 7.1

Keywords

START-AS-JAVA, timeout, waitforstarted, com.sap.sdt.util.diag.DiagException, "Could not start SAP instance with number", adapt-java-profile-dual-stack , 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.