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;

This issue can occur when the Adapter Engine Cache in SXI_CACHE is populated with an incorrect entry.

1. Go to transaction SXI_CACHE -> Goto -> Adapter Engine Cache.
2. If the entry here is incorrect, delete it.
3. Then resend a message which will allow the correct Adapter Engine Cache entry to be populated.

However status HTTP Response should be "200" for Sap PI .

Regards

Hasan

[Former Member]

HI All,

I tried all the options on my PI 7.1 system.

(1) RFC is giving Response of 500 with text of Internal sever error. However, all the 3 system has the same status and IDOC to file is not working in only in 1 system.

(2) SXMB_ADM.. All settings looks fine. Also proxy scenario works fine. IDOC is reaching PI but failing

(3) SICM looks Ok and deleted the entries in SXI_CACHE as well..

As mentioned only IDOC scenarios are failing  as shown below & rest all is going fine.

Thanks all for your time & appreciate any feed back.

[nitindeshpande]

Hello,

Have you done all the relevant configurations in Java stack of SAP PI system?

Please find the below blog for the relevant configurations to be done -

http://scn.sap.com/docs/DOC-31398

I think so InboundRA resource adapters and JCOs are not created.

Regards,

Nitin

[Former Member]

Hello ,

In parallel with above comments, check the below activities too ..

1.Go to smicm---> HTTP prot is in activate or not ..

2. H type RFC destination created user and password also check.. In case you used normal users kindly use standard user and re verify it ,,

3.SXMB_ADM->Integration Engine Configuration->Corresponding Integration Server enrty should be dest://<Http Integration server-Destination> Where < Http Integration server -Destination > is the RFC destination (SM59) of type HTTP connection (type H) to the Integration Server. In this case, host name, port, and path prefix are saved in the RFC destination.

4.Check that the port really is the ICM HTTP Port and not the J2EE port i.e SMICM then menu GOTO --> SERVICES and check the port number for HTTP. It should be HTTP port

5.Go to SXMB_ADM->Integration Engine Configuration->Choose Edit from Menu -> Change Global Configuration Data to switch to change mode. Then select System Landscape - Load Configuration.

Regards,

Azmath.

[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

[apu_das2]

Can you maintain this in SXMB_ADM -> Integration Engine Configuration -. Specific Configuration and check. It worked for me when I was working on dual stack -

[engswee]

Hi Techie

The exception says "see attachment HTMLError for details". Can you provide screenshot of what is in HTMLError?

Regards

Eng Swee

[Former Member]

This is error in HTML editor

404 Resource not found

Partner not reached

Error is logged with Tag: {00124a9b}

---

[engswee]

Might be an intermittent connectivity issue between ABAP stack and the Java stack. Sometimes this can happen due to big amount of processing going on causing resource limitation.

Can you try if you can restart/resend the message?

[Former Member]

Thanks for quick reply.. I tried the reprocess but  with same error..Thinking of restarting the java stack..?

[bhavesh_kantilal]

Hello,

Can you go to SXI_CACHE --> Adapter Engine and check the Adapter Engine URL? Is this a valid Adapter Engine URL with a valid host name and port?

Regards

Bhavesh

[Bhargavakrishna]

Hello,

Please go through the below thread

Regards

Bhargava Krishna