cancel
Showing results for 
Search instead for 
Did you mean: 

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

Former Member
0 Kudos


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.

Accepted Solutions (1)

Accepted Solutions (1)

Reagan
Advisor
Advisor
0 Kudos

Similar issue has been discussed here

Could you supply E:\CDs\SUM\SUM\sdt\log\SWITCH\DELETE-REMOTE-BOOTSTRAP-JARS_44.LOG log file?

It appears to me that the problem could be with the JVM. Try updating the JVM and see if it helps.

Have you tried the parameter service/protectedwebmethods = NONE +OSExecute like suggested in the above thread? Make sure you restart the service after modifying the parameter.

Former Member
0 Kudos

Hello Reagan

Yes I did go thru the link you mentioned earlier and I did upgrade the JVM to 6 (from4) on both Primary and Secondary App server. Rebooted server. Checked permissions. Chose NONE+OSExecute (I did not put space). I put service/protectedwebmethods = NONE+OSExecute

. Only NONE ans also SDEFAULT. Nothing helped.

and also followed OSS Note 927637 and set

service/admin_users=<domain>\sp1adm <domain>\SAPServiceSP1

As of now we have these two set

service/protectedwebmethods = DEFAULT

service/admin_users=CHECKFREE\sp1adm CHECKFREE\SAPServiceSP1

Here are the results

E:\usr\sap\SP1\J01\exe>sapcontrol -nr 01 -function GetStartProfile | findstr pro
tectedwebmethods
service/protectedwebmethods = DEFAULT

E:\usr\sap\SP1\J01\exe>

The latest DELETE-REMOTE-BOOTSTRAP-JARS file is *52 so I am attaching that. Its the same exact error every time. I have tried accessing the .jar files from the app server and they are all accessible fine

<!--LOGHEADER[START]/-->

<!--HELP[Manual modification of the header may cause parsing problem!]/-->

<!--LOGGINGVERSION[2.0.7.1006]/-->

<!--NAME[E:\CDs\SUM\SUM\sdt\log\SWITCH\DELETE-REMOTE-BOOTSTRAP-JARS_52.LOG]/-->

<!--PATTERN[DELETE-REMOTE-BOOTSTRAP-JARS_52.LOG]/-->

<!--FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%6s]: %m)]/-->

<!--ENCODING[UTF8]/-->

<!--LOGHEADER[END]/-->

Nov 6, 2014 3:57:52 PM [Info  ]: Creating a proxy to the sapcontrol web service at http://as1sp1:50113

Nov 6, 2014 3:57:55 PM [Info  ]: Setting the credentials for user CHECKFREE\sp1adm and a password.

Nov 6, 2014 3:57:55 PM [Info  ]: Using user name CHECKFREE\sp1adm to authenticate against the SAPControl web service API.

Nov 6, 2014 3:57:55 PM [Info  ]: Setting the service timeout to 300 s.

Nov 6, 2014 3:57:55 PM [Info  ]: Executing 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, host as1sp1 with timeout 300s, log file SUM_1415311075265.log ...

Nov 6, 2014 3:57:55 PM [Error ]: Could not execute command "[Ljava.lang.String;@39772437" on instance javax.xml.ws.soap.SOAPFaultException: Start Service runs with administrative privileges, OSExecute disabled on host $(2) using the sapcontrol web service at $(3). Check if sapcontrol is running and the log file $(4) in the sapcontrol work directory. In case of permissions issues, check SAP note 927637.

Nov 6, 2014 3:57:55 PM [Error ]: The following problem has occurred during step execution: com.sap.sdt.tools.sapcontrolws.SapControlWsException: 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_1415311075265.log in the sapcontrol work directory. In case of permissions issues, check SAP note 927637.

javax.xml.ws.soap.SOAPFaultException: Start Service runs with administrative privileges, OSExecute disabled

.

Reagan
Advisor
Advisor
0 Kudos

javax.xml.ws.soap.SOAPFaultException: Start Service runs with administrative privileges, OSExecute disabled

It appears to me the issue is with the administrative privileges which you added before.

Check these SAP notes as they suggest to remove the admin rights.

2042404 - service/protectedwebmethods = NONE +OSExecute, Permission Denied, on Windows

1116057 - Remove SAPService<SID> admin privileges on Windows

Set the parameter value as suggested in the SAP notes. Acoording to the note the value NONE will disable OSExecute so try with the values suggested and finally with this value service/protectedwebmethods = NONE +OSExecute with the space as well.

Restart the service.

Cheers

Reagan

Answers (0)