Upgrading Solution Manager to 7.1 Solution Manager

[georg_salmen]

Hi,

While downtime (Abap+Java) I got the following error.

ABAP ERROR:
Detected the following errors:

# /ns600/sap_disks/SSM/SUM/abap/log/SAPR702XPRA90000002.SME:
1 ETP109 version and release : "380.08.46" "721"
1 ETP198
2 EPU126XPost-import methods for change/transport request: "SAPK702XPRA90000002"
4 EPU111 on the application server: "fmgsme"
2 EPU122XPost-import method "AFTER_IMP_CHDO" started for "CHDO" "L", date and time: "20140604120440"
1AETR012XProgram terminated (job: "RDDEXECL", no.: "12044000")
1AEPU320 See job log"RDDEXECL""12044000""SME"

JAVA ERROR:

Could not start SAP instance with number 52. The instance with number 52 on host fmgsme could not be started within the specified timeout.

SUM  execute  component-deploy-700  start-as-java  com.sap.sdt.j2ee.services.servicesimpl.EngineControllerService  class com.sap.sdt.util.diag.DiagException

I am currently using SUM ver 1.0 SP10_4

Has anyone had this error? about every helpful tip would be very grateful!

Thanks

Georg

XPRASUPG.txt.zip

START-AS-JAVA_10.txt.zip

SAPR702XPRA90000002.txt.zip

[georg_salmen]

Hi,

I accept the non-serve error & continue the phase and still get the same error.

About every tip I would be very grateful.

Thanks & Regards,

Georg

[Former Member]

Hi Georg,

What was the solution for this error. My ABAP phase is running but java has stopped with the exact error.

Regards,

SJ

[georg_salmen]

Hi,

Sorry for the late reply.

Oh that was long ago, in my documentary I have the following written.

Open the file jump_config in the SUM Directory SDT>PARAM an edit

/sapstartsrv/httpsconnection = true

to

/sapstartsrv/httpsconnection = false

That has helped me.

Regards,

Georg

[former_member182657]

Hi Georg,

Please follow SCN thread .

Also you can accept the non-serve error & continue the phase .

Regards,

Gaurav