SAPEhpi connection error - Port 4240

[Former Member]

Hello,

I am trying to install following NW07 EHP1 patches using SAPEhpi in our BW D40 ABAP system. Our current ABAP patch levels are as mentioned below.

ComponentCurrent.Level New.Level

===================================

SAP_ABA--700(14)-701(4)

SAP_BASIS2005_1_700(14)701(4)

PI_BASIS2005_1_700(14)701(4)

SAP_BW700(16)701(4)

BI_CONT703(3)703(14)

We've configure SAPEhpi under /usr/sap/trans_D40/EHPI and starting it with following commands

1. logon as d40adm

2. go to /usr/sap/trans_D40/EHPI

3. ./STARTUP jce_policy_zip=jce_policy-1_2_4.zip

4. soon after starting UA server

5. logging on to browser from local laptop and open <bw-host ip>:4239

6 .click on (STDGui) which loads the GUI

in "Extraction phase" of SAPEhpi it fails with following error right at the begaining. Following is the error log.

==================================================================================

Aug 31, 2009 5:06:46 PM [Error ]: java.net.ConnectException: Connection refused

Aug 31, 2009 5:06:46 PM [Error ]: java.net.ConnectException: Connection refused

Aug 31, 2009 5:06:46 PM [Error ]: Could not connect to host sapbwd40 on port 4240.

Aug 31, 2009 5:06:46 PM [Error ]: Connection to SAPup could not be established, see following messages.

Aug 31, 2009 5:06:46 PM [Error ]: Tool connector failed.

Aug 31, 2009 5:06:46 PM [Error ]: Error from unit observer

Aug 31, 2009 5:06:46 PM [Error ]: Extraction of the ABAP upgrade request ABAP has failed

Aug 31, 2009 5:06:46 PM [Error ]: Unable to execute the SDT request

ABAP operation extract on hostname sapbwd40 instance 00

Aug 31, 2009 5:06:46 PM [Info ]: Request ABAP operation extract status

set to ABORTED Unable to execute the SDT request ABAP operation extract

on hostname sapbwd40 instance 00

Extraction of the ABAP upgrade request ABAP has failed

Error from unit observer

Tool connector failed.

Connection to SAPup could not be established, see following messages.

Could not connect to host sapbwd40 on port 4240.

java.net.ConnectException: Connection refused

java.net.ConnectException: Connection refused

==================================================================================

As confirmed by our network team, port "4240" is not blocked on the firewall and neither it is currently used by any other application. We don't know what else could be the root cause of our problem. We are unable to run SAPEhpi to install our remaining patches due to this.

As per the remedies mentioned in other SDN forums to try "telnet sapbwd40 4240 " however, this will only succeed when SAPEhpi would open this port for communication. Currently, the above command "telnet" command is resulting in "connection refused" because there is no port 4240 free and not being used by SAPEhpi or by any other services. Host and DNS entries in this file are also correct just like our other systems.

We are using the latest version of SAPEhpi as well.

Please advise if anyone has experienced this before.

Harshal

Thanks,

Harshal

[Former Member]

Thanks Rajeev...we were doing that but was failinig with that 4240 error.

Anyway this is how we sloved it

We got this solved by changing the location on the EHPI installion directory. Initially I had the issue as the EHPI was located in a

file systems /XXXX/XXXXXX/XX which was much longer that 25 characters. (we are on a UNIX box)

..../EHPI/INSTALL was failing stating that the path is more than 25 character. So we created a soft link and the INSTALL script started but when the GUI/ Weblink to start the actual installation was troggered it failed with this error:

*******************Could not connect to port 4240. ***********************

To fix that we just created a different physical file system /EHPI in our Unix box and did all actvities there and things went like a charm.

Another point - - Note 1260665 - Error in upgrade phase MAIN_SHDCRE/RUN_RSDBSCPY ...Make sure you have this note applied before you start the whole shebang with notes to avoid the mass activation error in -

MAIN_SHDRUN/ACT_UPG phase of EHP application. If not applied prior to the start you will have to manually do it in the shadow instance .

Hopefully if any one gets this issue, it helps him.

Thanks

Kalinga

[Former Member]

Thanks, i had the same problem, with a shorter path (i created a link first) and new extraction of the SAPehpi.SAR everything is fine...

[rajeev_das]

Hi,

At the very first instance, if possible restart the system to make sure no application is using ths port

Now start /EHPI/STARTUP "jce_policy_zip=<policy zip archive>" in unix or <DRIVE>:\EHPI\STARTUP.BAT

jce_policy_zip=<policy zip archive> in windows server

Finally kick off the frontend gui in your PC using the link - http://<host name>:4239

This should work.

[Former Member]

Hey Harshal:

We also are getting the same error.

Did a lsof -i :4240 at the OS and it doesnot return anything which implies that port is free.

Did you start the EHPI

- /EHPI/STARTUP "jce_policy_zip=90000125.ZIP" command in one session and then use

- http://<hostname:4239/ or start the GUI in another session?

We are also facing the same issue where EHPI is failing at the extraction phase with error

-

---

Unable to execute the SDT request ABAP operation extract on hostname

<hostname> instance 00

Extraction of the ABAP upgrade request ABAP has failed

Error from unit observer Tool connector failed.

Connection to SAPup could not be established, see following messages.

Could not connect to host <hostname> on port 4240.

java.net.ConnectException: Connection refused

java.net.ConnectException: Connection refused

-

---

Any help will be highly appreciated.

Thanks

Kalinga

[Former Member]

Does anyone have implement note 1248907 to resolve this error. The note has a support patch for SAPEhpi but no instructions are given around how to import this patch.

Harshal

[Former Member]

Does anyone has any clue about this ?

Harshal