Symptom
While upgrading the Solution Manager 7.2 from SP01 to SP26, the error "Shadow instance couldn't be started, check 'STARTSFI.LOG' and 'DEVTRACE.LOG': Process <Drive>:\usr\sap\<SID>\SUM\abap\exe/sapcontrol.exe exited with 1, see '<Drive>\usr\sap\<SID>\SUM\abap\log \SAPup.ECO' for details" .
STARTSFI.LOG:
1 ETQ399 SYSTEM MANAGER: SAPControl action START failed for instance 04 ('SAPCONTROL MANAGER: call (sapcontrol.exe) failed with return code '-1'
').
1 ETQ399 SYSTEM MANAGER: CheckSystemStatus.
1 ETQ399 SAPCONTROL MANAGER: getProcessList with host: <host> and instance: 04
3 ETQ120 20230712090140: PID 6196 execute '~\exe\sapcontrol.exe -format script -prot PIPE -host <host> -nr 04 -function GetProcessList', output written to 'D:\usr\sap\<SID>\SUM\abap\log\SAPup.ECO'.
3WETQ123 20230712090140: PID 6196 exited with status 1 (time 0.00 real)
1EETQ399 SYSTEM MANAGER: START of mandatory instance 04 on server <host> has failed
2EETQ399 Starting shadow instance failed
1EETQ399 Last error code set is: Shadow instance
1EETQ399Xcouldn't be started, check 'STARTSFI.LOG' and 'DEVTRACE.LOG': Process D:\usr\sap\<SID>\SUM\abap\exe/sapcontrol.exe exited with 1, see 'D:\usr\sap\<SID>\SUM\abap\log\SAPup.ECO' for details
1EETQ204 Upgrade phase "START_SHDI_FIRST" aborted with severe errors ("20230712090140")
The shadow instance (in SM04) service does not start. It goes from start, running, to stop
DEVTRACE.LOG:
---------------------------
M ThCallDbBreak: no sql statement active
M Wed Jul 12 08:21:13:566 2023
M ThIErrHandle: action is STOP_WP, skip rollback
M ThIErrHandle: Entering DpRecoverMtxAfterProcessCrash
M DpRecoverMtxAfterProcessCrash: recover mutex after crash of W0
M ThIErrHandle: DpRecoverMtxAfterProcessCrash o.k.
M ThTriggerExecShutDown: shutdown server
M ThCallHooks: call hooks for event BEFORE_SHUTDOWN
M ThCallHooks: call hook >abRtmShutdown< for event BEFORE_SHUTDOWN
M PfSemLock: lock sem 42
M PfWriteIntoFile: shared buffer is empty.
M PfSemUnlock: unlocked sem 42
M ThIErrHandle: do not call ThrCoreInfo (no_core_info=0, in_dynp_env=0)
SAPCPESTD.OUT:
EXECUTING D:\usr\sap\<SID>\SYS\exe\uc\NTAMD64\sapcpe.EXE "pf=\\<host>\sapmnt\<SID>\SYS\profile\<SID>_DVEBMGS00_<host>"
SAPup> Process with PID 4944 terminated with status -1073740791 at 20230718120639!.
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
Read more...
Environment
Solution Manager 7.2
Keywords
"Shadow instance couldn't be started ", "STARTSFI.LOG" , "DEVTRACE.LOG ", "SAPCONTROL MANAGER: call (sapcontrol.exe) failed with return code '-1' ", Starting shadow instance failed, SAPup.ECO, "START_SHDI_FIRST", sapcpe, , KBA , BC-UPG-TLS-TLA , Upgrade tools for ABAP , 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