ICM_HTTP_CONNECTION_FAILED

[Former Member]

Hi all,

i know there are a lot of ICM_HTTP_CONNECTION_FAILED threads already but I can't seem to find a solution in any of those threads.

here's my situation, we replaced our old xi server with a new one. i configured the new server with the same config as the old one. we're not having any problems in our ERP QAS and SRM QAS. the problem is with the ERP DEV. it cannot connect to the new server. as seen from sxi_monitor:

Connection request from (76/8773/0) to host: oldserver, service: 8000 failed (NIECONN_REFUSED)

it's still trying to connect to the old server. also the service no should have been 8020.

I have tried everything in all the previous threads

1) double checked sm59

2) used ip addresses instead of the host name

3) verified the hostname and the service no

any help would be appreciated. thanks!

[RKothari · Accepted solution]

Hi,

Check the below mentioned SAP notes:

1. SAP Note 773830 - FQHN Determination in ICM and make sure the host

name is set correctly.

2. Check the dev_icm trace file and see whether there are any errors.

More details in SAP Note 634006 - ICM Messages Explanatory Note.

-Rahul

[Former Member · Accepted solution]

dev_icm is showing the same error as in sxi_monitor:

Connection request from (76/8773/0) to host: oldserver, service: 8000 failed (NIECONN_REFUSED)

it's trying to connect to the old server but we have turned that off. it should be connecting now to the new server.

i have tried deleting the RFC and recreating a new one.

[RKothari · Accepted solution]

Hi,

1. Check the URL that is used to send the message to PI, for example

https://server:ICM-port/sap/xi/engine?type=entry

https://server:J2EE-port/MessagingSystem/receive/AFW/XI

2. Try to execute the URL in the browser using the user XIAFUSER/PIAFUSER(name as set during installation).

Check that the port really is the ICM HTTP port (transaction SMICM) and not the Java port.

If the port is wrong, change the pipeline URL in the SLD in the business system of the Integration Server.

Restart the Java Engine to reset the SLD buffer of the Adapter Engine.

3. Check if service com.sap.aii.af.ms.app is active or not. Try to (re)start the application using the SAP NetWeaver

Administrator. Choose Systems --> Start & Stop -->Java EE Applications or restart the Java engine.

-Rahul

[Former Member · Accepted solution]

Thanks Rahul. I've tried your sugeestions just now but I still have an error. This is weird since it's already working in QAS but not in DEV. I can't understand why it's still connecting to the old XI server instead of the new one.

[RKothari · Accepted solution]

Hi,

Can you let me know, the error details you are recieving when you try to open the URL's?

-Rahul

[former_member4985]

Hi there,

Increase the values (TIMEOUT AND PROCTIMEOUT) as seen below example for the R/3 parameters (via SMICM):

icm/keep_alive_timeout

old value: <your_old_value>

new value: 900

You will also see the parameters where PROT=HTTP. Please change the

values here too similar to as seen below:

icm/server_port_0

old value: PROT=HTTP,PORT=<your_port>,HOST=<your_host>

,TIMEOUT=<your_old_value>, PROCTIMEOUT=<your_old_value>

new value: PROT=HTTP,PORT=<your_port>,HOST=<your_host>

,TIMEOUT=900,PROCTIMEOUT=900

.

.

.

icm/server_port_<n>

old value: PORT=<your_port_value>,PROT=HTTP

new value: PORT=<your_port_value>,PROT=HTTP,TIMEOUT=900

,PROCTIMEOUT=900

Also, change the icm/host_name_full to full qualified host name.

You could also take a look into these notes:

#824554 - ICM and SAP Web Dispatcher Timeout Parameter

Afterwards, ensure you restart the system so that new values will take effect.

Regards,

Caio Cagnani

[Former Member]

Thanks. We chose to use the old server again because there are issues. I'll get back to you once we reuse the new server.

[rajasekhar_reddy14]

Hi

,

Better to create new connection with new server details with out editing old opne and try once.

Regards,

Raj