Quantcast
Channel: SCN : Popular Discussions - SAP Enterprise Portal: Migration and Upgrade
Viewing all articles
Browse latest Browse all 767

SUM 7.4 Upgrade error - execution of the Delete remote bootstrap jars

$
0
0


Hello

We are upgrading Portal from 7.02 to 7.4 and stuck at the downtime/execution phase

 

JDK version........: 1.6.0_85 SAP AG

SUM version........: 1.0.11.8

Source release.....: 7.02

Target release.....: 7.40

ABAP stack present.: false

 

An error has occurred during the execution of the Delete remote bootstrap jars step with action execute. Service com.sap.sdt.j2ee.services.servicesimpl.RemoteExecutionService failed with the following message:

 

Could not execute command "\\passp1\sapmnt\SP1\SYS\exe\jvm\NTAMD64\sapjvm_6.1.071\sapjvm_6\bin\java.exe -cp \\passp1\sapmnt\SP1\SYS\global/sdtremote/sdt_trace.jar;\\passp1\sapmnt\SP1\SYS\global/sdtremote/sdt_util.jar;\\passp1\sapmnt\SP1\SYS\global/sdtremote/sdt_tools.jar;\\passp1\sapmnt\SP1\SYS\global/sdtremote/sap.com~tc~sec~csi.jar com.sap.sdt.tools.remote.SdtRemoteOperationsExecutor deleteBootstrapJars e:/usr/sap/SP1/J01 SWITCH_UPGRADE" on instance 1 on host as1sp1 using the sapcontrol web service at http://as1sp1:50113. Check if sapcontrol is running and the log file SUM_1415290308665.log in the sapcontrol work directory. In case of permissions issues, check SAP note 927637.

 

You can find more information in the files E:\CDs\SUM\SUM\sdt\log\SWITCH\DELETE-REMOTE-BOOTSTRAP-JARS_44.LOG and ProcessOverview.html.

 

Use the information provided to trouble-shoot the problem. There might be an OSS note providing a solution to this problem. Search for OSS notes with the following search terms:

 

SWITCH,execute,pre-component-deploy,delete-remote-bootstrap-jars,com.sap.sdt.j2ee.services.servicesimpl.RemoteExecutionService,class com.sap.sdt.tools.sapcontrolws.SapControlWsException

 

 

 

We have already tried the below:

1600846 - JSPM/SUM calls sapcontrol without

user credentials

1563660 - sapcontrol, <sid>adm authorization issues

(SUM) (we gave DEFAULT, NONE - nothing worked)

 

Gave full permisssion (everyone, sidadm, SAPServiceSID)

to sapmnt/saploc/ entire sap folder in BOTH primary and secondary

app servers.


Viewing all articles
Browse latest Browse all 767

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>