cancel
Showing results for 
Search instead for 
Did you mean: 

SUM tool execution error.

0 Kudos

Hello All,

I run into this issue while deploying MII 15.1 on NW 7.5. Basically I think the mistake that made was to include MII OEE components in original Stack.

My SUM tool is showing following error, not sure how to proceed from here.

Here are error logs that I have in SUM log


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.

May 3, 2016 10:09:09 AM  Info: com.sap.ASJ.dpl_api.001074 +++ Wait for server response +++. Deploying offline [16] seconds. Will timeout in [7183] seconds.

May 3, 2016 10:09:09 AM  Error: com.sap.ASJ.dpl_api.001224 Could not establish connection to AS Java on [NIWNPR-MII02D:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.

May 3, 2016 10:09:11 AM  Error: com.sap.ASJ.dpl_api.001224 Could not establish connection to AS Java on [NIWNPR-MII02D:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.

May 3, 2016 10:09:13 AM  Error: com.sap.ASJ.dpl_api.001224 Could not establish connection to AS Java on [NIWNPR-MII02D:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.

May 3, 2016 10:09:15 AM  Error: com.sap.ASJ.dpl_api.001224 Could not establish connection to AS Java on [NIWNPR-MII02D:50004]. End of stream is reached unexpectedly during input from Socket[addr=/10.104.5.50,port=50004,localport=50328]. Check if the host and port specified are correct and AS Java is up and running.

May 3, 2016 10:09:18 AM  Error: com.sap.ASJ.dpl_api.001224 Could not establish connection to AS Java on [NIWNPR-MII02D:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.

May 3, 2016 10:09:20 AM  Error: com.sap.ASJ.dpl_api.001224 Could not establish connection to AS Java on [NIWNPR-MII02D:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.

May 3, 2016 10:09:22 AM  Error: com.sap.ASJ.dpl_api.001224 Could not establish connection to AS Java on [NIWNPR-MII02D:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.

May 3, 2016 10:09:24 AM  Error: com.sap.ASJ.dpl_api.001224 Could not establish connection to AS Java on [NIWNPR-MII02D:50004]. End of stream is reached unexpectedly during input from Socket[addr=/10.104.5.50,port=50004,localport=50353]. Check if the host and port specified are correct and AS Java is up and running.

May 3, 2016 10:09:26 AM  Info: com.sap.ASJ.dpl_api.001074 +++ Wait for server response +++. Deploying offline [32] seconds. Will timeout in [7167] seconds.

May 3, 2016 10:09:26 AM  Error: com.sap.ASJ.dpl_api.001224 Could not establish connection to AS Java on [NIWNPR-MII02D:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.

May 3, 2016 10:09:28 AM  Error: com.sap.ASJ.dpl_api.001224 Could not establish connection to AS Java on [NIWNPR-MII02D:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.

May 3, 2016 10:09:30 AM  Error: com.sap.ASJ.dpl_api.001224 Could not establish connection to AS Java on [NIWNPR-MII02D:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.

May 3, 2016 10:09:32 AM  Error: com.sap.ASJ.dpl_api.001224 Could not establish connection to AS Java on [NIWNPR-MII02D:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.

May 3, 2016 10:09:34 AM  Error: com.sap.ASJ.dpl_api.001224 Could not establish connection to AS Java on [NIWNPR-MII02D:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.

May 3, 2016 10:09:42 AM  Info: com.sap.ASJ.dpl_api.001068 Assuming a subsequent restart of the server due to exception: [P4ConnectionException], message: [Error. Server process is down or disconnected from ICM. Check server process traces and ICM logs for details. Error message: the requested server is not available]

May 3, 2016 10:09:42 AM  Info: com.sap.ASJ.dpl_api.001074 +++ Wait for server response +++. Deploying offline [0] seconds. Will timeout in [7200] seconds.

May 3, 2016 10:09:42 AM  Error: com.sap.ASJ.dpl_api.001224 Could not establish connection to AS Java on [NIWNPR-MII02D:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.

May 3, 2016 10:09:44 AM  Error: com.sap.ASJ.dpl_api.001224 Could not establish connection to AS Java on [NIWNPR-MII02D:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.

May 3, 2016 10:09:49 AM  Error: com.sap.ASJ.dpl_api.001224 Could not establish connection to AS Java on [NIWNPR-MII02D:50004]. Cannot establish connection with any of the available profiles:

url=NIWNPR-MII02D:50004 protocol=p4 (None); Reason: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection to host: 10.104.5.50 and port: 50004

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.

May 3, 2016 10:09:52 AM  Error: com.sap.ASJ.dpl_api.001224 Could not establish connection to AS Java on [NIWNPR-MII02D:50004]. Cannot establish connection with any of the available profiles:

url=NIWNPR-MII02D:50004 protocol=p4 (None); Reason: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection to host: 10.104.5.50 and port: 50004

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.

May 3, 2016 10:09:55 AM  Error: com.sap.ASJ.dpl_api.001224 Could not establish connection to AS Java on [NIWNPR-MII02D:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.

May 3, 2016 10:09:57 AM  Info: com.sap.ASJ.dpl_api.001074 +++ Wait for server response +++. Deploying offline [15] seconds. Will timeout in [7184] seconds.

May 3, 2016 10:09:57 AM  Error: com.sap.ASJ.dpl_api.001224 Could not establish connection to AS Java on [NIWNPR-MII02D:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.

May 3, 2016 10:09:59 AM  Error: com.sap.ASJ.dpl_api.001224 Could not establish connection to AS Java on [NIWNPR-MII02D:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.

May 3, 2016 10:10:01 AM  Error: com.sap.ASJ.dpl_api.001224 Could not establish connection to AS Java on [NIWNPR-MII02D:50004]. End of stream is reached unexpectedly during input from Socket[addr=/10.104.5.50,port=50004,localport=50412]. Check if the host and port specified are correct and

AS Java is up and running.

May 3, 2016 10:10:03 AM  Error: com.sap.ASJ.dpl_api.001224 Could not establish connection to AS Java on [NIWNPR-MII02D:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.

May 3, 2016 10:10:05 AM  Error: com.sap.ASJ.dpl_api.001224 Could not establish connection to AS Java on [NIWNPR-MII02D:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.

May 3, 2016 10:10:07 AM  Error: com.sap.ASJ.dpl_api.001224 Could not establish connection to AS Java on [NIWNPR-MII02D:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.

May 3, 2016 10:10:10 AM  Error: com.sap.ASJ.dpl_api.001224 Could not establish connection to AS Java on [NIWNPR-MII02D:50004]. End of stream is reached unexpectedly during input from Socket[addr=/10.104.5.50,port=50004,localport=50432]. Check if the host and port specified are correct and AS Java is up and running.

May 3, 2016 10:10:12 AM  Error: com.sap.ASJ.dpl_api.001224 Could not establish connection to AS Java on [NIWNPR-MII02D:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.

May 3, 2016 10:10:14 AM  Info: com.sap.ASJ.dpl_api.001074 +++ Wait for server response +++. Deploying offline [32] seconds. Will timeout in [7167] seconds.

May 3, 2016 10:10:14 AM  Error: com.sap.ASJ.dpl_api.001224 Could not establish connection to AS Java on [NIWNPR-MII02D:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.

May 3, 2016 10:10:16 AM  Error: com.sap.ASJ.dpl_api.001224 Could not establish connection to AS Java on [NIWNPR-MII02D:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.

May 3, 2016 10:10:18 AM  Error: com.sap.ASJ.dpl_api.001224 Could not establish connection to AS Java on [NIWNPR-MII02D:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.

May 3, 2016 10:10:20 AM  Error: com.sap.ASJ.dpl_api.001224 Could not establish connection to AS Java on [NIWNPR-MII02D:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.

May 3, 2016 10:10:57 AM  Info: com.sap.ASJ.dpl_api.001023 Deployment of [name: 'xapps~mpm~mii', vendor: 'sap.com' (sda)] finished.

May 3, 2016 10:10:59 AM  Info: com.sap.ASJ.dpl_api.001052 +++ Deployment of session ID [81] finished with status [Error] +++. [[ deployerId=3 ]] [[#92: 133.031 sec]] [

===== Summary - Deploy Result - Start =====

------------------------

Type | Status  : Count

------------------------

> SCA(s)

   - [Aborted] : [1]

> SDA(s)

   - [Aborted] : [1]

   - [AlreadyDeployed] : [5]

------------------------

------------------------

Type | Status  : Id

------------------------

> SCA(s)

   - [Aborted] : name: 'OEE_MII', vendor: 'sap.com',

> SDA(s)

   - [Aborted] : name: 'xapps~mpm~mii', vendor: 'sap.com',

   - [AlreadyDeployed] : name: 'xapps~mpm~umeactions', vendor: 'sap.com', name: 'xapps~mpm~dict', vendor: 'sap.com', name: 'xapps~mpm~ui', vendor: 'sap.com', name: 'xapps~mpm~ctc~content', vendor: 'sap.com', name: 'xapps~mpm~ear', vendor: 'sap.com',

------------------------

===== Summary - Deploy Result - End =====

]

Accepted Solutions (1)

Accepted Solutions (1)

dastefl_muc
Explorer

Hi Bajaj,

here was a solution found.


Danke und einen schönen Tag noch

Stefan

janos_fekete2
Advisor
Advisor
0 Kudos

Hi Bajaj,

OEE is not a core component, but it has dependencies with the core components.
SAP note 2146857 describes the topic. In this case seems OEE has already been deployed.

Best Regards,
Janos

dastefl_muc
Explorer
0 Kudos

Hello,

in our case we had an error; Configuration error in the Provider.xml </jars> we has after each entry

(right in the Picture)

With best wishes,

Stefan

0 Kudos

Hello there

Sorry for late reply,

I raised an incident with SAP and they suggested following which helped.

Solution 1

Could you please check directory called oldSUM under /usr/sap/SID/SYS/global/security/data then remove or rename it.

Then Restart SUM. Let me know the result.

Solution 2

Could you please try to rename the file /usr/sap/SM2/SYS/global/security/data/sumExecutions.xml .

After renaming this file , restart SUM again.

Solution 3

.Resetting the update procedure on operating system level

a.

On operating system level, change to the SUM directory with the following command:

cd /usr/sap/<SID>/SUM/abap/bin

b.

From the command line interface, start the internal SAPup executable using the

gt=scroll parameter:./SAPup gt=scroll

c.

Choose the Back button.

d.

In the dialog on the command line interface, choose Reset.e.

I did all of them above and not sure which exactly worked, but in the end I got rid of old instance of SUM.

Good Luck.

Rupesh

Answers (1)

Answers (1)

former_member206857
Active Participant
0 Kudos

I have the same issue, which of the options from SAP worked?