HTTP Error code 404 in SAP PI.

[Former Member]

Dear All,

We have a synchronous scenario from Legacy to ECC thru PI. The issue now is for few

synchronous message (may be < 1% of messages) we are getting "HTTP Error: Receiving Message"

in MONI. Please find the detailed error below:

  <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!--  Call Adapter
  -->
- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
  <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>

***************************************************************************

Error: -20
Version: 7200
Component: ICM
Date/Time: Tue Mar 12 13:46:00 2013 
Module: icxxconn.c
Line: 2271
Server: HOSTNAME_XXX_10
Error Tag: {001b5d55}
Detail: Connection request from (43/22524/0) to host: XXXXXX, service: 8100 failed (NIECONN_REFUSED) EX-T43, U22524, 950 PIAFMIP, 10.XX.XX.XX, 13:45:55, M0, W5, , 1/0

FYI:     This happens only for few sync messages.
            IE config in SXMB_ADM is fine. 
            All other setting are working correctly.
           This is not a data issue. The same messages can be sent back again.

            is this the problem with the ECC Server of PI. If its a PI/ECC issue,  Please let us know to resolve this issue.

Thanks in Advance.

[santosh_k3 · Accepted solution]

Hi Kumar,

Try searching with this ICM_HTTP_CONNECTION_FAILED in forum.

there are lot of threads on this.

May be this can help you.

https://scn.sap.com/thread/1423385

http://scn.sap.com/thread/2032413

Regards,

Sai.

[former_member190293]

Hi Kumar!

Actually, according to HTTP 1.1 Status Code definitions HTTP 400 means:

10.4.1 400 Bad Request

The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications.

I think you must try to re-test your faulty messages to figure out the cause of this error.

Regards, Evgeniy.

[former_member183816]

While configuring, don't use http://DestName, use Dest://DestName

[rodrigoalejandro_pertierr]

did you check the HTML attached? coul you provide an screenshot?

RGds

[former_member190681]

Hi Kumar,

This is common error for connection lost,

Before going to this link you have check the following points

1) Check Connection of Port , Http, RFC Destination

2) Check network connectivity of xi to other application.

3) Check ICM with SMICM T-CODE.

For this types of connection issue please follow the below link, it may helpful to you.

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c059d583-a551-2c10-e095-eb5d95e03...

Regards,

Kiran Polani

[former_member207892]

Hi Kumar,

Please check the links for the lead.

http://scn.sap.com/thread/2032413

https://scn.sap.com/thread/1423385

Http 400 error can also occur if any problem with HTTP destination config in SM59 [ECC]. Please check

Also these type of issues sometimes occur due to heavy traffic of message flow through PI.

Please check SMQ1 and SMQ2 in PI to make sure everything is flowing as expected.

Hope this might help you.

Please try and let us know.

Thanks!

Praveen.

[former_member690959]

Hi Praveen.

My problem, like Kumars is not config in SM59 HTTP Destination, because most of the messages are being delivered, just a few of them show this error.

In my case it can't be due to heavy traffic or huge message flow, we are having about 2500 messages daily for all the interfaces that are actually running and just about 600 for the proxy ECC->PI with the issues.

In transaction SMQ2 we can see the locked queues when this problem happens and we have to execute LUW in order to push the first message and let the enqueued ones to flow. In transaction SMQ1 there are no issues.

I've checked the threads you posted and the notes inside them, none of them applies in this case.

Thank you for your answer, if you have any other thought that might help, please let me know.

[former_member690959]

Hi Kumar an ll the people in this thread.

I'm facing exactly te same problem, we are getting HTTP response code 400 with message ICM_HTTP_CONNECTION_FAILED just for a few messages like you, maybe less than 1% of the messages.

My scenario is an async proxy interface ECC -> PI 7.31.

My basis team and I are thinking that maybe it can be some quality network issue, but we are not sure.

It can not be some config mistake because delivering is working fine for most of the messages.

How is this issue going for you Kumar? Did you solve it?

Can anyone share some knowledge around this issue?

Thank you.

[Former Member]

Generally for ALL Error Code 400 WE need to Check SM58 and the RFC connection. It seems that for few message the RFC connection is dropping down. Also on the legacy side please check if the SOAP channel has proper data connectivity.

[smavachee]

Cross check your Integration Engine Configuration at SXMB_ADM

Provide the URL as http://host:port/sap/xi/engine?type=entry

Also make sure that

> HTTP Port Number and other Parameters are correctly defined

> RFC Destination is working

> XI Services in ECC are activated

Hope it helps.!

Regards,

Sunil