ICM_HTTP_CONNECTION_FAILED

[Former Member]

Hi All,

The scenario is IDOC to File (XML). IDOC is triggered in ERP, comes to PI ( i can see in MonI)

After all pipeline steps in PI, while in call adapter in PI, i see error

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!--  Call Adapter

  -->

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">

  <SAP:Category>XIServer</SAP:Category>

  <SAP:Code area="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>

  <SAP:P1>400</SAP:P1>

  <SAP:P2>ICM_HTTP_CONNECTION_FAILED</SAP:P2>

  <SAP:P3>(See attachment HTMLError for details)</SAP:P3>

  <SAP:P4 />

  <SAP:AdditionalText />

  <SAP:Stack>Error while receiving by HTTP (error code: 400 , error text: ICM_HTTP_CONNECTION_FAILED) (See attachment HTMLError for details)</SAP:Stack>

  <SAP:Retry>A</SAP:Retry>

  </SAP:Error>

All other Proxy to file and file to proxy interfaces, works fine .. No issues in SLDHECK etc.

HTTP RFC works fine ( PI to ABAP & vice versa)

Can you please advice, what could be the issue

Thxs

[hasan_celebi]

Hi Techie;

Have you checked the RFC Connections(sm59). is it working properly?

Regards

Hasan

[Former Member]

Thanks All. I have checked the RFC and it is giving  below results..The internal server error but this is the same results in all other system and idoc to file is working fine in those systems so don;t think this issue

I have done all other suggested things, SXMB_ADM, Cache refresh, full refresh with no success..

Also proxy to file works fine..

Thxs

[Former Member]

Hi All,

Please advice, if you have any further advice. Thxs

[Bhargavakrishna]

Hello

Check your Integration Engine configuration in SXMB_ADM --> Integration engine configuration --> Specific configuration and provide the url as  http://host:port/sap/xi/engine?type=entry

Since the target is file server, you configured host name / IP address in the communication channel? try to give the IP address instead of host name and try again.

Try to check the connectivity from OS level using Ping.

Regards

Bhargava Krishna

[Former Member]

Hi Techie,

Check this sap note.

1930823 - 400 ICM_HTTP_CONNECTION_FAILED 404 Resource not found Partner not reached

Cause
Parameter icm/conn_timeout is used to set the timeout when setting up the connection. 
If the timeout is exceeded, an error page is generally displayed with the information 
"404 Resource not found" "Partner not reached".

Resolution
Please increase the Instance Profile parameter icm/conn_timeout to "10000"(msec) 
on application system and PI system. Please also increase it on the Web Dispatcher, if you use one.
If the problem persists, you can increase the parameter to 15000 and 20000.

Regards,

Praveen.

[bhavesh_kantilal]

Which version of PI are you on? PI 7.31 and above returns HTTP 500 for the Integration Directory HMI Test connection which is expected.

Like I have mentioned previously and so has Hasan Basri -  please check the Adapter Engine cache URL in SXI_CACHE. This URL could be incorrect causing all the issues.

Regards

Bhavesh

[bhavesh_kantilal]

Sorry correction - In PI 7.31 and above, Integration Directory HMI return HTTP 403 and not HTTP 500.

Regards,

Bhavesh