cancel
Showing results for 
Search instead for 
Did you mean: 

XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 400 Bad Request

Former Member
0 Kudos

Hi,

We are doing File to WCF Scenario( SOAP ). I am trying to post the Data to WCf usingf SOAP Reciver Adapter.

Getting the Following error.

Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 400 Bad Request

Thanks in advance

Accepted Solutions (0)

Answers (5)

Answers (5)

former_member181985
Active Contributor
0 Kudos

what is the application platform for the receiver system which is hosting the webservice?

e.g., .NET, Java/J2EE etc..

Former Member
0 Kudos

Hi all.

Thanks for your prompt response..

The applicxation is .NET

former_member181985
Active Contributor
0 Kudos

I faced similar problem with .NET webservices few months back.

There are couple of authentications possible with .net webservices.

The problem could be the net webservice is designed to support only http GET method. Find out this from .NET devloper.

Ask them to support for POSTmethod as well.

Also how many inputs does this webservice has?

Former Member
0 Kudos

Hi all>

Right now we are facing up the same issue>

SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 400 Bad Request

Background>

We would like to send orders PO to an external supplier. The problem is found in the adapter type.

baskar_gopalakrishnan2
Active Contributor
0 Kudos

>>> Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 400 Bad Request

Answer: Use the third party wsdl in SOAP UI or any soap client tool and send the request and see the response. The problem here is the message structure mismatch between your request to the webservice and webservice expecting...

Possible 2 reasons:

1) You are not creating the target message based on the wsdl structure or not configured soap receiver properly.

or

2 ) Your wsdl is not latest or updated one or some changes have happened in the third party webservice hosting side.

markangelo_dihiansan
Active Contributor
0 Kudos

Hello,

The bad request would mean that you have sent a request to the webservice that it does not understand (did not respect the HTTP Protocol). Would you be able to load the WSDL in a third-party program such as SOAP UI and then compare the request structure generated by SOAP UI to the one that you are sending to your webservice? They should be almost the same (except the namespaces generated).

Are you using XIAdapter? XI SOAP XML is different from SOAP over HTTP XML.

Hope this helps,

Mark

iprieto
Contributor
0 Kudos

Hi,

Maybe the response XML returned by receiver server is not the same that the service interface used for the response.

Check out this XML and compare it with you service interface structure.

Best Regards

Ivá