cancel
Showing results for 
Search instead for 
Did you mean: 

Receiver SOAP Adapter error

Former Member
0 Kudos

Hi All,

I am getting this response error message in my receiver SOAP Adapter while invoking a synchronous webservice.

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

- <!--

Request Message Mapping

-->

- <ProcessMessageResponse xmlns="http://Sleek.Integrator.Messaging" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<ProcessMessageResult>Value cannot be null. Parameter name: Request string is a null reference.</ProcessMessageResult>

</ProcessMessageResponse>

Thx in advance

Ravijeet

Accepted Solutions (1)

Accepted Solutions (1)

stefan_grube
Active Contributor
0 Kudos

The request that you have sent to the web service is wrong.

Check the request message against the web service specification.

Regards

Stefan

Former Member
0 Kudos

Hi All,

I am still getting the same error value is null. I am not able to track what could be the cause of the error. If I am taking the message from SXMB_MONI and using it in a client tool it is successfully calling the webservice.

Do we need to explicitly mention in some configuration that content type is soap/xml. SOAP header is omitting the content type or is not specifying "soap/xml" as the content type.

I am interacting with a WAF websevice, is there any compatibilty issue with Windows Webservice and SAP XI?

Also what should I pick as the SOAP Action from this wsdl file definition

<wsdl:portType name="IMessageProcessor">

<wsdl:operation name="ProcessMessage">

<wsdl:input message="tns:IMessageProcessor_ProcessMessage_InputMessage" wsaw:Action="XXX.Messaging/ProcessMessage"/>

<wsdl:output message="tns:IMessageProcessor_ProcessMessage_OutputMessage" wsaw:Action="XXX.Messaging/ProcessMessageResponse"/>

</wsdl:operation>

</wsdl:portType>

<wsdl:service name="MessageProcessor">

<wsdl:port name="BasicHttpBinding_IMessageProcessor" binding="i0:BasicHttpBinding_IMessageProcessor">

<soap:address location="http://XXX.com/cardax/provisioningservice"/>

</wsdl:port>

Thx in advance

Ravijeet

Former Member
0 Kudos

Hi Ravijeet,

I request you to please specify your scenario of SAP XI.

To answer your query:

1) Which action type I should use:

In the wsdl file for the input message you have the action

XXX.Messaging/ProcessMessage, this you may use in your receiver soap adapter action.

2. The error you are getting seems to be more related to string value.

Are you using CDATA Tag etc????

Or is there any case where your webservice accepts the string formats only. please check it with your webservices team.

Thanks & Regards

Prabhat

Former Member
0 Kudos

Hi Prabhat,

My scenario is ABAP PROXY to Webservice(Based on WAF) sync call. I am sending a Soap Request to this sync Webservice.I am getting a error message as such:

<ProcessMessageResponse xmlns="http://xxx.Integrator.Messaging" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<ProcessMessageResult>Value cannot be null. Parameter name: Request string is a null reference.</ProcessMessageResult>

</ProcessMessageResponse>

Thanks and regards

Ravijeet

Former Member
0 Kudos

Hi All,

I am still stuck up with this issue. I was trying to figure out what is going wrong. In my SXMB_MONI, CallAdapter I am able to SoapHeader, SoapBody and Payload. In the Payload I am getting the desired xml as per my mapping. But if I go to communication channel monitoring and in the Message Tool of Receiver SOAP adapter, if I check the message tab there on viewing the SOAP Document I can't see the xml payload.

There I see <SOAP Body>

<sap Manifest> but no <sap:Payload> whereas I can see the payload in SXMB_MONI CallAdapter messages. What could be the reason?

Thx in advance

Ravijeet

Answers (3)

Answers (3)

rodrigoalejandro_pertierr
Active Contributor
0 Kudos

hi,

get the inbound message from SXI_MONITOR>inbound message>Main Document.

later go to IR-->mmessage mmaping and do a test Mapping.

surely you will get and error that specify you that you are mapping a mandatory field with a null value.

in this case assign a value for this field and check is there other errors in mapping if not, just solicit to sender system team that you are specting the field with a value so it fail.

they will tell you what you have to do.

Thanks

Rodrigo

Former Member
0 Kudos

Hi,

Try invoking using a SAOP tools available online like SOAP UI.This way it is easier to test and know the error.

Thanks

agasthuri_doss
Active Contributor
0 Kudos

Hi,

Check the Message mapping Whether it passes all the mandatory values to the Target

Regards

Agasthuri Doss