Skip to Content
avatar image
Former Member

Upgrade Solution Manager

Hi ! I am trying to upgrade SAP SolMan 7.1 to 7.2 and getting this error in java process execution:

I cant' start shadow instance because abap process execution is already killed it:

sm1adm 52> ./SAPup stopshd ; ./SAPup startshd

At this time of the procedure, the shadow instance does not exist anymore since you are past phase STOP_SHDI_*!


What should I do ? Thanks!

/sap/inst/SUM/SUM/sdt/log/SUM/DEPLOY-SHADOW-INSTANCE_02.LOG:

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

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

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

<!--NAME[/sap/inst/SUM/SUM/sdt/log/SUM/DEPLOY-SHADOW-INSTANCE_02.LOG]/-->

<!--PATTERN[DEPLOY-SHADOW-INSTANCE_02.LOG]/-->

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

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

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

Nov 17, 2016 9:37:58 AM [Info ]: Number of source deployed components detected from components provider: 26

Nov 17, 2016 9:37:58 AM [Info ]: Number of source deployed components detected from components provider: 26

Nov 17, 2016 9:37:58 AM [Info ]: DeployController release is 7.10. Component version rule UPDATE_LOWER_ONLY will be used.

Nov 17, 2016 9:37:58 AM [Info ]: Deploy version rule has been set to updateLowerOrChanged in file /sap/inst/SUM/SUM/sdt/param/jspm_config.txt.

Nov 17, 2016 9:37:58 AM [Info ]: Deploy error strategy has been set to stop in file /sap/inst/SUM/SUM/sdt/param/jspm_config.txt.

Nov 17, 2016 9:37:58 AM [Info ]: Deployment prerequisite check error strategy has been set to stop in file /sap/inst/SUM/SUM/sdt/param/jspm_config.txt.

Nov 17, 2016 9:37:58 AM [Info ]: Undeploy error strategy has been set to skipDepending in file /sap/inst/SUM/SUM/sdt/param/jspm_config.txt.

Nov 17, 2016 9:37:58 AM [Info ]: Undeploy dependency rule has been set to stop in file /sap/inst/SUM/SUM/sdt/param/jspm_config.txt.

Nov 17, 2016 9:37:58 AM [Info ]: Deploy timeout has been set to 7200 seconds in file /sap/inst/SUM/SUM/sdt/param/jspm_config.txt.

Nov 17, 2016 9:37:58 AM [Info ]: Start parsing deployment order definition file /sap/inst/SUM/SUM/sdt/config/dodf.xml.

Nov 17, 2016 9:37:58 AM [Info ]: File /sap/inst/SUM/SUM/sdt/config/dodf.xml is parsed and relative deployment data model is extracted.

Nov 17, 2016 9:37:58 AM [Info ]: Start parsing deployment order definition file /sap/inst/SUM/SUM/sdt/config/dodfNonsupportedDCType.xml.

Nov 17, 2016 9:37:58 AM [Info ]: File /sap/inst/SUM/SUM/sdt/config/dodfNonsupportedDCType.xml is parsed and relative deployment data model is extracted.

Nov 17, 2016 9:37:58 AM [Info ]: Number of source deployed components detected from components provider: 26

Nov 17, 2016 9:37:58 AM [Info ]: Deploying Java components...

Nov 17, 2016 9:37:58 AM [Info ]: Deploying Java components...

Nov 17, 2016 9:37:58 AM [Info ]: You can find additional information in log file /sap/inst/SUM/SUM/sdt/log/SUM/DEPLOYMENT_RESULTS_02.LOG.

Nov 17, 2016 9:37:59 AM [Info ]: Deployment of Java components finished.

Nov 17, 2016 9:37:59 AM [Error ]: com.sap.engine.services.dc.api.ConnectionException: [ERROR CODE DPL.DCAPI.1144] Could not establish connection to AS Java on [msk-solman:50204]. Cannot establish connection with any of the available profiles:

url=msk-solman:50204 protocol=p4 (None); Reason: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection to host: 172.0.0.27 and port: 50204

Check if server is started, access point for the protocol is available, and IP/Host name is accessible on network.. Check if the host and port specified are correct and AS Java is up and running.

Nov 17, 2016 9:37:59 AM [Error ]: Could not connect to Deploy Controller. Make sure that AS Java and Deploy Controller service are running.

Nov 17, 2016 9:37:59 AM [Info ]: Overal deployment message : Could not connect to Deploy Controller. Make sure that AS Java and Deploy Controller service are running.

com.sap.engine.services.dc.api.ConnectionException: [ERROR CODE DPL.DCAPI.1144] Could not establish connection to AS Java on [msk-solman:50204]. Cannot establish connection with any of the available profiles:

url=msk-solman:50204 protocol=p4 (None); Reason: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection to host: 172.0.0.27 and port: 50204

Check if server is started, access point for the protocol is available, and IP/Host name is accessible on network.. Check if the host and port specified are correct and AS Java is up and running.

javax.naming.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.interfaces.cross.DestinationException: Cannot establish connection with any of the available profiles:

url=msk-solman:50204 protocol=p4 (None); Reason: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection to host: 172.0.0.27 and port: 50204

Check if server is started, access point for the protocol is available, and IP/Host name is accessible on network.]

com.sap.engine.interfaces.cross.DestinationException: Cannot establish connection with any of the available profiles:

url=msk-solman:50204 protocol=p4 (None); Reason: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection to host: 172.0.0.27 and port: 50204

Check if server is started, access point for the protocol is available, and IP/Host name is accessible on network.

Nov 17, 2016 9:37:59 AM [Info ]: Saving data model Jump.JSPM.DataModel.xml ...

Nov 17, 2016 9:37:59 AM [Info ]: Data model Jump.JSPM.DataModel.xml saved.

Nov 17, 2016 9:37:59 AM [Info ]: Saving data model JUP.J2EE.DataModel.xml ...

Nov 17, 2016 9:38:02 AM [Info ]: Data model JUP.J2EE.DataModel.xml saved.

Nov 17, 2016 9:38:02 AM [Error ]: The following problem has occurred during step execution: com.sap.sdt.jspm.service.JspmServiceException: Could not update components.

Deployment of queue Queue_2016.11.16 at 17:05:07 completed with error Could not connect to Deploy Controller. Make sure that AS Java and Deploy Controller service are running.

com.sap.engine.services.dc.api.ConnectionException: [ERROR CODE DPL.DCAPI.1144] Could not establish connection to AS Java on [msk-solman:50204]. Cannot establish connection with any of the available profiles:

url=msk-solman:50204 protocol=p4 (None); Reason: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection to host: 172.0.0.27 and port: 50204

Check if server is started, access point for the protocol is available, and IP/Host name is accessible on network.. Check if the host and port specified are correct and AS Java is up and running.

javax.naming.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.interfaces.cross.DestinationException: Cannot establish connection with any of the available profiles:

url=msk-solman:50204 protocol=p4 (None); Reason: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection to host: 172.0.0.27 and port: 50204

Check if server is started, access point for the protocol is available, and IP/Host name is accessible on network.]

com.sap.engine.interfaces.cross.DestinationException: Cannot establish connection with any of the available profiles:

url=msk-solman:50204 protocol=p4 (None); Reason: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection to host: 172.0.0.27 and port: 50204

Check if server is started, access point for the protocol is available, and IP/Host name is accessible on network.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

5 Answers

  • avatar image
    Former Member
    Nov 18, 2016 at 02:32 PM

    I reload my virtual machine from backup and start the update from the very begining and get the same error:

    Java is running ok:

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Nov 18, 2016 at 08:22 PM

    Hi Igor,

    I think this is because of unsupported class version. I faced it during NW 7.5 upgrade and I had to download stack.xml again (after adding the correct SAPJVM) and restart the upgrade.

    2318596 - SUM - Deploy Software Components fails due to Unsupported major.minor version.

    Regards,

    Harish Karra

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Nov 21, 2016 at 09:01 AM

    Hi Harish,

    I think I fixed this problem: I found in deploy.0.trc in shadow instance java work directory

    Caused by: com.sap.sql.exception.OpenSQLException: caused by java.io.IOException: ORA-01652: unable to extend temp segment by 128 in tablespace PSAPTEMP

    After extending PSAPTEMP I restarted the shadow instance:

    sapcontrol -nr 02 -function RestartSystem

    sapcontrol -nr 02 -function RestartService

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Dec 02, 2016 at 01:54 PM

    I was wrong

    SAP Note 1473530 RMI_P4 connectivity problem with EOFException

    SAP Note 1036371 HTTP and P4 connections to J2EE Engine are impossible

    note 1036371 helps me

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Dec 02, 2016 at 02:51 PM

    Igor - Good to hear that problem is resolved.

    Add comment
    10|10000 characters needed characters exceeded