Solution Manager Upgrade 7.1 to 7.2

former_member81360 · ‎01-04-2019

Upgrading from 7.1 to 7,.2. THis error occurs on the java portion of a dual stack upgrade. I have tried to repeat, stop java and perform the repeat.

Current step: Start shadow instance SCS Error in Start shadow instance SCS Step The following error or errors have occurred during the execution of the current step: Could not start SAP instance with number 5. Could not check if the instance number 5 on host SAPSolMgr2 is started. Sapcontrol client could not perform action wait for started on instance 5 Return code condition success evaluated to false for process sapcontrol for action wait for started. For more information, see the files Z:\SUM\sdt\log\SUM\START-SCS-SHADOW_05.LOG.

        Trouble Ticket Report

Update to SAP SOLUTION MANAGER 7.2 (ABAP)SAP SOLUTION MANAGER 7.2 (JAVA)

SID................: SLM
Hostname...........: sapsolmgr2
Install directory..: e:\usr\sap\SLM
SUM directory......: Z:\SUM\sdt
Database...........: MSS
Operating System...: WIN
JDK version........: 1.6.0_211 SAP AG
Source release.....: 702
Target release.....: 740
ABAP stack present.: true
SUM Java scenario..: SWITCH_UPGRADE

An error occured during the execution of Start shadow instance SCS of action pre-execute.
Service com.sap.sdt.j2ee.services.servicesimpl.EngineControllerService failed with the following message:

Jan 4, 2019 2:28:47 PM [Info ]: Enable service for instance 5 on host SAPSolMgr2... Jan 4, 2019 2:28:47 PM [Info ]: Process ID 224, name sc.exe has been started. Jan 4, 2019 2:28:47 PM [Info ]: Command line: sc.exe config SAPSLM_05 start= auto Jan 4, 2019 2:28:47 PM [Info ]: Standard out: Z:\SUM\sdt\log\SUM\ENABLE_SERVICE_05_05.OUT Jan 4, 2019 2:28:47 PM [Info ]: Process ID 224 has been started. Jan 4, 2019 2:28:47 PM [Info ]: Waiting for process ID 224, name sc.exe to finish. Jan 4, 2019 2:28:47 PM [Info ]: Process ID 224, name sc.exe has been finished, exit code 0. Jan 4, 2019 2:28:47 PM [Info ]: Service for instance 5 on host SAPSolMgr2 has been enabled. Jan 4, 2019 2:28:47 PM [Info ]: Start service for instance 5 on host SAPSolMgr2... Jan 4, 2019 2:28:47 PM [Info ]: Process ID 225, name sapcontrol has been started. Jan 4, 2019 2:28:47 PM [Info ]: Command line: E:\usr\sap\SLM\ASCS01\exe\sapcontrol -nr 5 -user slmadm <SecureField> -prot NI_HTTP -function StartService SLM Jan 4, 2019 2:28:47 PM [Info ]: Standard out: Z:\SUM\sdt\tmp\SAPCONTROL_STARTSERVICE_5_05.OUT Jan 4, 2019 2:28:47 PM [Info ]: Process ID 225 has been started. Jan 4, 2019 2:28:47 PM [Info ]: Waiting for process ID 225, name sapcontrol to finish. Jan 4, 2019 2:28:47 PM [Info ]: Process ID 225, name sapcontrol has been finished, exit code 0. Jan 4, 2019 2:28:47 PM [Info ]: Wait for service for instance 5 on host SAPSolMgr2 to start... Jan 4, 2019 2:28:49 PM [Info ]: Process ID 226, name sapcontrol has been started. Jan 4, 2019 2:28:49 PM [Info ]: Command line: E:\usr\sap\SLM\ASCS01\exe\sapcontrol -nr 5 -host SAPSolMgr2 -user slmadm <SecureField> -prot NI_HTTP -function GetProcessList Jan 4, 2019 2:28:49 PM [Info ]: Standard out: Z:\SUM\sdt\tmp\SAPCONTROL_GETPROCESSLIST_5_09.OUT Jan 4, 2019 2:28:49 PM [Info ]: Process ID 226 has been started. Jan 4, 2019 2:28:49 PM [Info ]: Waiting for process ID 226, name sapcontrol to finish. Jan 4, 2019 2:28:49 PM [Info ]: Process ID 226, name sapcontrol has been finished, exit code 0. Jan 4, 2019 2:28:49 PM [Info ]: The sapcontrol service on host SAPSolMgr2 and instance 5 is started. Jan 4, 2019 2:28:49 PM [Info ]: Service for instance 5 on host SAPSolMgr2 has been started. Jan 4, 2019 2:28:49 PM [Info ]: Process ID 227, name sapcontrol has been started. Jan 4, 2019 2:28:49 PM [Info ]: Command line: E:\usr\sap\SLM\ASCS01\exe\sapcontrol -nr 5 -host SAPSolMgr2 -user slmadm <SecureField> -prot NI_HTTP -function GetTraceFile Jan 4, 2019 2:28:49 PM [Info ]: Standard out: Z:\SUM\sdt\log\SUM\SAPCONTROL_GETTRACEFILE_5_193.OUT Jan 4, 2019 2:28:49 PM [Info ]: Process ID 227 has been started. Jan 4, 2019 2:28:49 PM [Info ]: Waiting for process ID 227, name sapcontrol to finish. Jan 4, 2019 2:28:49 PM [Info ]: Process ID 227, name sapcontrol has been finished, exit code 0. Jan 4, 2019 2:28:49 PM [Info ]: sapstartsrv PID is 9268 Jan 4, 2019 2:28:49 PM [Info ]: Process ID 228, name sapcontrol has been started. Jan 4, 2019 2:28:49 PM [Info ]: Command line: E:\usr\sap\SLM\ASCS01\exe\sapcontrol -nr 5 -host SAPSolMgr2 -user slmadm <SecureField> -prot NI_HTTP -function Bootstrap Jan 4, 2019 2:28:49 PM [Info ]: Standard out: Z:\SUM\sdt\log\SUM\SAPCONTROL_BOOTSTRAP_5_05.OUT Jan 4, 2019 2:28:49 PM [Info ]: Process ID 228 has been started. Jan 4, 2019 2:28:49 PM [Info ]: Waiting for process ID 228, name sapcontrol to finish. Jan 4, 2019 2:28:49 PM [Info ]: Process ID 228, name sapcontrol has been finished, exit code 1. Jan 4, 2019 2:28:49 PM [Error ]: Error bootstrapping instance [Ljava.lang.String;@159ef0bf on host com.sap.sdt.tools.sapcontrol.SAPControlException: Sapcontrol client could not perform action bootstrap on instance 5 Return code condition success evaluated to false for process sapcontrol for action bootstrap. . Jan 4, 2019 2:28:49 PM [Warning]: Error bootstrapping instance 5 on host SAPSolMgr2. Sapcontrol client could not perform action bootstrap on instance 5 Return code condition success evaluated to false for process sapcontrol for action bootstrap. Jan 4, 2019 2:28:49 PM [Info ]: Process ID 229, name sapcontrol has been started. Jan 4, 2019 2:28:49 PM [Info ]: Command line: E:\usr\sap\SLM\ASCS01\exe\sapcontrol -nr 5 -host SAPSolMgr2 -user slmadm <SecureField> -prot NI_HTTP -function GetTraceFile Jan 4, 2019 2:28:49 PM [Info ]: Standard out: Z:\SUM\sdt\log\SUM\SAPCONTROL_GETTRACEFILE_5_194.OUT Jan 4, 2019 2:28:49 PM [Info ]: Process ID 229 has been started. Jan 4, 2019 2:28:49 PM [Info ]: Waiting for process ID 229, name sapcontrol to finish. Jan 4, 2019 2:28:49 PM [Info ]: Process ID 229, name sapcontrol has been finished, exit code 0.

former_member81360 · ‎01-11-2019

I looked at the two SNOTES; The second applied, unfortunately I was at a point where I could not restart. So I restored the server and started over. The SNOTE talked about permissions and extracting sum under the correct LOGONID. Made sure this was correct the second time. Still, cannot start up the shadow instance. Different problem this time around. I would attached some of the logs but when I try it, iI get a message that tells me that I have the wrong file type, even though I am trying to attach a .txt file. Not sure why. Maybe someone can give me a lesson in attachments.

Current Phase: MAIN_SHDPREPUT/START_SHDI_PREPUT

Severe error(s) occurred in phase

MAIN_SHDPREPUT/START_SHDI_PREPUT!

Last error code set:

Shadow instance

couldn't be started, check 'STARTSSC.LOG' and 'DE

To analyze errors during the start of the shadow instance, check
the      'STARTSSC.LOG' and 'DEVTRACE.LOG' files in directory
Z:\SUM\abap\log'.Repeat the phase until the shadow instance is started and you
can log on to      instance number '04'

This portion is from the sapup.eco:


EXECUTING z:\SUM\abap\exe\sapcontrol.exe -prot PIPE -host SAPSolMgr2 -nr 04 -function StartWait 300 10


11.01.2019 09:42:57
Start
OK


11.01.2019 09:44:17
StartWait
FAIL: process disp+work.EXE Dispatcher not running


This trouble ticket was created by SAPup on 20190111094417 
-------------------------------------------------------------
SAPup broke during phase START_SHDI_PREPUT in module MAIN_SHDPREPUT / Shadow System Operations: Preput
Error Message: Last error code set:
Shadow instance
couldn't be started, check 'STARTSSC.LOG' and 'DEVTRACE.LOG': Process z:\SUM\abap\exe/sapcontrol.exe exited with 2, see 'z:\SUM\abap\log\SAPup.ECO' for details


-------------------------------------------------------------
-------------------------------------------------------------
Summary of SAPup:
-------------------------------------------------------------
SAPup Release:		lmt_004
SAPup Version:		SAPup release lmt_004 version 53.000
Start Release:		702
Target Release:		740
-------------------------------------------------------------
Summary of host system details:
-------------------------------------------------------------
SID:			SLM
Host:			SAPSolMgr2
MS Host:		SAPSolMgr2
GW Host:		SAPSolMgr2
Start Path:		E:\usr\sap\SLM\DVEBMGS00\exe	
Kernel Path:		E:\usr\sap\SLM\DVEBMGS00\exe
-------------------------------------------------------------
Summary of operating system details:
-------------------------------------------------------------
OS Type:		Windows NT X86_64
OS Version:		6.3
-------------------------------------------------------------
Summary of database details:
-------------------------------------------------------------
Database Type:		mss
Database Version:	11.00.7001.00
-------------------------------------------------------------
Summary of RFC details:
-------------------------------------------------------------
Host:			SAPSolMgr2
GW Host:		SAPSolMgr2
Client:			000
Destination:		SLM
Language:		E
System No.:		04
-------------------------------------------------------------
-------------------------------------------------------------

Sriram2009 · ‎01-06-2019

Hi Owen.

Refer the SAP notes 2309573 & 2595246 reference of error message "Service com.sap.sdt.j2ee.services.servicesimpl.EngineControllerService failed with the following"

Regards

Solution Manager Upgrade 7.1 to 7.2

Accepted Solutions (0)

Answers (2)

Answers (2)

Re: GUI oddities with new 2022 ABAP Trial

Re: Adding SAP Cloud ALM to "Instances & Subscript...

Re: AATP-BOP runs without selecting and updating a...

Re: SFTP receiver - error Cannot store file cause:...

Re: CF Deployment Error: Error getting tenant t0