Error in Soap Reciever Adapter?

Hi all
Please do suggest resolution of this error in SOAP Reciever adapter
2006-07-04 04:50:47 Error SOAP: error occured: java.io.IOException: invalid content type for SOAP: TEXT/HTML
2006-07-04 04:50:47 Error Exception caught by adapter framework: invalid content type for SOAP: TEXT/HTML
2006-07-04 04:50:47 Error Delivery of the message to the application using connection AFW failed, due to: invalid content type for SOAP: TEXT/HTML.
with regards
subrato kundu

Hi,
Please look at this thread:
DeliveryException:: invalid content type for SOAP: TEXT/HTML
Regards
Vijaya

Similar Messages

No SOAP Envelope error in SOAP Receiver Adapter

Hello Friends,
Informaiton:-
I have configured one Synchronous scenarion for SAP R/3 to PI 7.1 to Java based web applicaiton.
On the Receiver/Outbound side, i have configured the SOAP Receiver Adapter with the Target URL and SOAP Action.
Outbound and Inbound service interfaces have Request/Response and Fault messages.
Issue:-
While sending the Message, Below error is noticed in ABAP stack SXMB_MONI during the Call Adapter Stage and also in RWB (Channel Monitoring) .
com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: No SOAP Envelope but 1 {}RESPONSES; HTTP 200 OK
I also found that Request message is not reaching to the Java Web server.
I am taking the Same message Payload (found at Call Adapter Stage) and ussing it in XML Altova SPY Web client tool. There it is running scuccessfully and getting the Response message.
please suggest.
Thanks & Regards
Jagesh

Hi,
Yesterday i consumed the same WSDL file in Altova XML SPY and there it is working, getting the Response.
Now comparing the SOAP Request message reaching to the Third party Web server (which fall within the same Lane network)
from SAP PI and Altova XML SPY tool. I used TCP Gateway for the below scenarios.
(1)First i sent the SOAP message from PI and observed the RESPONSE message without the SOAP Envelope in TCP Gatway Trace and hence i am getting the No SOAP Envelope Error in PI.
(2)I consumed the same WSDLfile in Altova XML SPY and sent the SOAP message, here i got the Proper SOAP Response message and hence success in this case. (Used the same Data Payload as used in point 1)
(3)Now to identify the issue in the SOAP Request message being sent from PI, i used the same SOAP message sent in step 1 here, that means copy the entire SOAP ENvelope from the TCP gateway Trace and pasted it in Alota Spy and sent, there it is found running (got the response message from Third Party server).
One difference i found in HTTP Protocol statements in SOAP Request message in Point no 1 and Point no 2 above.
HTTP Protocols in Point 1 (Through PI).
POST HTTP/1.0
Accept: /
Host: 172.24.138.142:4544
User-Agent: SAP-Messaging-com.sap.aii.af.sdk.xi/1.0505
CallingType: SA
content-id: <soap-00306EEAC2051ED1839136CEE8564900 sap.com>
Content-Type: text/xml; charset=utf-8
Content-Length: 1195
SOAPACTION: "Action1"
HTTP Protocols in Point 2 (Through Altova).
POST / HTTP/1.1
Content-Type: text/xml
User-Agent: XML Spy
SOAPAction: "Action1"
Host: 172.24.138.142:4544
Content-Length: 1195
Connection: Keep-Alive
Cache-Control: no-cache
Thanks to Mr. Stefan Grube for writting such a nice blog.
Troubleshooting SOAP, HTTP and Mail Adapter Scenarios with TCPGateway
Experts, please suggest me further.
Thansk & Regards
Jagesh

SOAP reciever adapter problem

Hi,
I am getting below error in the adapter monitor for my SOAP recv adapter.
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException
This is using external definition. I ported my PI 7.0 content to PI 7.1. I am wondering how external definitions and interfaces will effect with the setting of software component verion " use of interface objects"
Do I need to put as SAP netweaver 7.0 since it is PI 7.0 content.
Can I change this setting any time. How this will effect.
I could not see this adapter error in my 7.0 env. And not in 7.1 SP04.
is there anything i should check here to avoid this error.
Thanks,
Srinivasa

Hey,
> I am wondering how external definitions and interfaces will effect with the setting of software component verion " use of >interface objects"
No, If so Mapping might have failed,
>Do I need to put as SAP netweaver 7.0 since it is PI 7.0 content.
It is good to have latest one
>Can I change this setting any time. How this will effect.
Sure, You can, After upgrade do a Regression Testing.
Cheers
Agasthuri

Error in SOAP receiver adapter.

Hi All,
<b>Problem</b> : Receiver soap adapter not working
1)I have used Java mapping which is working fine.
2)After sending message; In RWB the SOAP channel is shown INACTIVE.
3)In SXMB_MONI it is shown successful.
4)My username pwd is right.
4)My wsdl path is right.
5)I am not using any security certificate.
6)Web service is tested.
I dont know what exactly is the problem
Please help.
regards,
Sumit

Hi,
Sorry for late reply.
This is what i got from message monitoring:
Time Stamp Status Description
2007-07-23 11:18:52 Success Message successfully received by messaging system. Profile: XI URL: http://hydhtceaixi1:50000/MessagingSystem/receive/AFW/XI Credential (User): XIISUSER
2007-07-23 11:18:52 Success Using connection SOAP_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2007-07-23 11:18:52 Success Message successfully put into the queue.
2007-07-23 11:18:52 Success The message was successfully retrieved from the receive queue.
2007-07-23 11:18:52 Success The message status set to DLNG.
2007-07-23 11:18:52 Success Delivering to channel: Invoice_info_receive_CC
2007-07-23 11:18:52 Success SOAP: request message entering the adapter
2007-07-23 11:18:53 Error SOAP: call failed
2007-07-23 11:18:54 Success SOAP: sending a delivery error ack ...
2007-07-23 11:18:54 Success SOAP: sent a delivery error ack
PLease help as I urgently need to make this working.
Thanks for showing interest.
Regards,
Sumit Oberoi

Error in SOAP Receiver Adapter with HTTPS

Dear All,
I am developing a SOAP to SOAP scenario with HTTPS i.e. client without authentication and I am facing an issue with the receiver adapter. Few messages fails in the receiver side while rest are successful.
Error - Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: Failed to get the input stream from socket: iaik.security.ssl.SSLCertificateException: Peer certificate rejected by ChainVerifier
Please let me know what can be the reason for the error.
Thanks and Regards,
Rana Brata De

Hi Rana,
Check the certificates sequence as well the certificates end dates in STRUST in SAP PI system. if, deployed in NWA level check over there.
One more :: sending the data to web server or web page. make sure, PI is pointing to which server.
Regards,
Kesava.

SOAP reciever adapter user authentication

Hi,
I have configured SOAP receiver communication channel using User authentication.
How I can confirm that these credentials are being sent out.
Please let me now where to check these in XI?

Thank You both for your replies.
I observed two things
1) I selected adapter engine in Message Monitoring, in Audit log, it shows
Adapter Framework caught exception: null and the message failed with System Error.
but on Integration Engine it shows all messges are succesfsul
2) I have installed TCP Gateway on my PC, and created two connections with two different port numbers namely 50081, 50082.
In my receiver SOAP channel, I have given URL as http://local PC ip address:50081
When I send message from R3 system it reached XI and messages shows successful in moni,. but I could not see any in TCP Gateway.
Is there anything Iam missing,
Edited by: Vamsi on Jul 9, 2009 3:52 PM

SOAP Reciever Error message in Comp Moni

Hello
This is the first time i'm experiencing this error for SOAP receiver adapter. Attached the link for the error:
[url]http://fb.esnips.com/doc/fe28959a-d718-4bd1-ba84-14e321fdabcf/soap-recv-error-message[url]
Any inputs for troubleshooting this error?
thkx
Prabhu

Hi Prabhu,
Have you tried to trace your SOAP mesage?
If not refer SAP note - 856597. It may help you..:)
Q: How can I trace the whole message?
A: If you have a third-party web service server or client and if it
works with their own test tool but not with the SOAP adapter, you
need to analyze the messages that are transported. Typically, this
is done by either inseting a TCP gateway between the client and the
server or non-invasively using some packet catching utility. You
are free to use any tool but make sure that the tool can capture
the messages as raw bytes. Some tools are known to store the
captured messages as text and corrupt some characters.
You can find a tool called TCPGateway in the attachment section of
this note (stored in tcpgw.zip). Please unpack this zip file and
open index.htm for more details
Regards,
Sunil

Single SOAP receiver adapter for multiple interfaces

Hi,
I have to send multiple interfaces like Vendor, Customer, Material to one receiver.
I want to configure only one communication channel (receiver SOAP adapter) to send all these interfaces. Is this possible?
Currently I am provided with different URLs from the receiver system as below.
http://host:port/Services/Vendor.wsdl
http://host:port/Services/customer.wsdl
http://host:port/ServicesMaterial.wsdl
I will be having 3 Sender agreement, 3 receiver determination, 3 interface determination and 3 Receiver agreement.
I want only one SOAP reciever adapter which goes inside all the above 3 Receiver agreement.
So When I give the target url as http://host:port/Services, the messages fail.
But When I specify the full targert url in the adapter as http://host:port/Services/Vendor.wsdl then it works.
Which means I would have to create as many communication channel as interfaces.
Is there a work around for this?

hi kantheri,
For this, we have to fill the TargetURL and the SOAPAction in Receiver Communication channel dynamically.
So, we need to write UDF in Message Mappings using DynamicConfiguration to fill the TargetURL and the SOAPAction Dynamically.
DynamicConfigurationKey keyURL = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/SOAP","THeaderSOAPACTION");
DynamicConfigurationKey targetURL=DynamicConfigurationKey.create("http://sap.com/xi/XI/System/SOAP","TServerLocation");
// access dynamic configuration
DynamicConfiguration conf = (DynamicConfiguration) container
.getTransformationParameters()
.get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
conf.put(keyURL,"Soap action");
conf.put(targetURL,"target url");
return "";
In this UDF, we are filling the TargetURL in u201CTServerLocationu201D message attribute and SOAPAction in u201CTHeaderSOAPActionu201D message attribute.
So, whenever we execute this corresponding operation these values will be filled in receiver communication channel at runtime.
TargetURL- Give some dummy URL or http://
SOAPAction - *
regards,
ganesh.

SOAP reciever channel inactive

I have a SOAP reciever adapter but in RWB communication channel monitoring it shows tobe "Started but inactive"
Can anyone suggest any possible reason and solution

Hi,
please have a look here:
SOAP Adapter Started but not active
Regards
Patrick

Error while posting messages to SOAP sender adapter SP 13

Hi Friends,
I have configured a SOAP sender adapter in XI 3.0 and is using the URL
http://host:port/XISOAPAdapter/MessageServlet?channel=:BS_WEBSERVICE:CC_WEBSERVICE_SOAP to post the messages. When I open the URL in the browser I am getting the error.
Message Servlet is in Status ERROR
Status information:
Servlet com.sap.aii.af.mp.soap.web.MessageServlet (Version $Id: //tc/aii/30_VAL_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#5 $) bound to /MessageServlet
Classname ModuleProcessor: null
Lookupname for localModuleProcessorLookupName: localejbs/ModuleProcessorBean
Lookupname for remoteModuleProcessorLookupName: null
ModuleProcessorClass not instantiated
ModuleProcessorLocal not instantiated
ModuleProcessorRemote not instantiated
But when I test the URL http://host:port/XISOAPAdapter/HelperServlet?action=FindChannel&channel=:BS_WEBSERVICE:CC_WEBSERVICE_SOAP to check the communication channel I am getting the right response as below.
<?xml version="1.0" ?>
<http://host:port/XISOAPAdapter/HelperServlet?action=FindChannel&channel=:BS_EBTR_WEBSERVICE:CC_EBTR_WEBSERVICE_SOAP> <s:ChannelInfo xmlns:s="http://sap.com/xi/WebService/xi30">
<channelID>e7ac884596ea3d088cbfd8b434f942f2</channelID>
<name>CC_WEBSERVICE_SOAP</name>
<type xmlns:st="http://sap.com/xi/XI/System">st:SOAP</type>
<direction>INBOUND</direction>
<party />
<service>BS_WEBSERVICE</service>
</s:ChannelInfo
I used the http capture to debug, In the 1st case though I am getting "Message Servlet in status error" I am seeing a 200 OK code in the http capture tool. When the message is posted from .net client proxy we are getting a 500 internal server error.
Am not sure what causes the error ? I saw two notes in SDN related to SOAP - J2EE SP13. We are in SP13. Is this the issue ? Wanted to know your opinion before applying the notes.
Thanks & Regards,
Mathew

ABAP & Java stack was on different SP levels.

Error while passing URL Dynamically in SOAP AXIS adapter..!!

Hi ,
Idoc> XI>SOAP-AXIS
I am doing a scenario where I need to pass the URL dynamically in SOAP-AXIS adapter by taking the RCVPRN of Idoc.
If
RCVPRN = 100 , message has to go to http://10.190.25.16:8210/file/receiver
RCVPRN = 200 , message has to go to http://10.190.25.16:8210/file/receiver2
RCVPRN = 300 , message has to go to http://10.190.25.16:8210/file/receiver3
I used the below UDF and it is working correctly and generating the URL dynamically .
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey keyHeader1 = DynamicConfigurationKey.create( "http://sap.com/xi/XI/System/SOAP", "TServerLocation");
conf.put(keyHeader1, a);
return "";
The value is coming in SOAP document as expected like below.
<sap:DynamicConfiguration xmlns:sap="http://sap.com/xi/XI/Message/30" SOAP:mustUnderstand="1">
<sap:Record namespace="http://sap.com/xi/XI/System/SOAP" name="TServerLocation">http://10.190.25.16:8210/file/receiver3</sap:Record>
</sap:DynamicConfiguration>
I used the below Configuration modules in receiver SOAP-AXIS adapter as suggested in Note 1028961.
AF_Adapters/axis/AFAdapterBean ---> afreq
AF_Adapters/axis/HandlerBean ---> xireq
AF_Adapters/axis/HandlerBean ---> dc
AF_Adapters/axis/HandlerBean ---> remover
AF_Adapters/axis/HandlerBean ---> trp
AF_Adapters/axis/HandlerBean ---> xires
AF_Adapters/axis/AFAdapterBean ---> afres
xireq -> handler.type-> java:com.sap.aii.axis.xi.XI30OutboundHandler
dc -> handler.type-> javasap.aii.axis.xi.XI30DynamicConfigurationHandler
dc ---> key.1 ---> write http://sap.com/xi/XI/System/SOAP TServerLocation
dc ---> location.1 ---> context
dc ---> value.1 ---> transport.url
remover ---> handler.type ---> java:com.sap.aii.axis.soap.HeaderRemovalHandler
remover ---> namespace ---> http://sap.com/xi/XI/Message/30
trp ---> handler.type ---> java:com.sap.aii.adapter.axis.ra.transport.http.HTTPSender
trp ---> module.pivot ---> true
xires ---> handler.type ---> java:com.sap.aii.axis.xi.XI30OutboundHandler
and I am getting the below error in SOAP-AXIS channel at the point java:com.sap.aii.adapter.axis.ra.transport.http.HTTPSender.
2009-03-02 15:23:44 Success Axis: getting handler trp of java:com.sap.aii.adapter.axis.ra.transport.http.HTTPSender
2009-03-02 15:23:45 Error Axis: error in invocation: (500)internal server error
2009-03-02 15:23:45 Error MP: Exception caught with cause (500)internal server error
2009-03-02 15:23:45 Error Exception caught by adapter framework: (500)internal server error
2009-03-02 15:23:46 Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: (500)internal server error: (500)internal server error.
2009-03-02 15:23:46 Error The message status set to NDLV.
Kindly let me know if anyone has any idea what might be wrong?
Note : The given URL is correct one because I cross checked by passing them normally by giving directly in adapter and they are all working and the message is going to receiver.
Thanks
Deepthi

Hi Stefan,
>> dc -> handler.type-> javasap.aii.axis.xi.XI30DynamicConfigurationHandler
>> dc ---> key.1 ---> write http://sap.com/xi/XI/System/SOAP TServerLocation
>> dc ---> location.1 ---> context
>> dc ---> value.1 ---> transport.url
>> Try read instead of write
When I tried with this, I am getting the below error "Connection refused ".
Success Axis: entering HandlerBean
Success Axis: getting handler trp of java:com.sap.aii.adapter.axis.ra.transport.http.HTTPSender
Error Axis: error in invocation: java.net.ConnectException: Connection refused
Error MP: Exception caught with cause java.net.ConnectException: Connection refused
Error Exception caught by adapter framework: ; nested exception is: java.net.ConnectException: Connection refused
Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: ; nested exception is: java.net.ConnectException: Connection refused: java.net.ConnectException: Connection refused.
Success The message status set to WAIT.
It is going successfully when I tried sending directly. Looks like Dynamic Configuration is not working for SOAP-AXIS.
Any Suggestion?
Thanks
Deepthi.

SOAP Receiver Adapter Error in XI RWB - java.lang.NULLPointerException

Hi,
We have a asynchronous scenario in SAP-XI, where we are sending the PO data from SRM to third party (Hubspan / TNT). Proxy is being used at Sender side and SOAP Adapter is used for Receiver Communication Channel.
u2022SRM is sending around 1000 messages through background job and around 995 or 996 messages are being processed successfully and showing the proper XML payload as well in RWB. But 4-5 messages are getting failed in XI RWB for u2018java.lang.NullPointerExceptionu2019. For these failed messages we are not able to see the XML payload as well in XI RWB while these messages are showing successful status in MONI in SRM and XI and we are able to see the payload as well in MONI. The webservice is restarting and trying to send the payload three times in RWB, but it is getting the same Nullexception error.
04.11.2011 16:45:49.715 Success Delivering to channel: CC_B2B_HUBSPAN_RCV
04.11.2011 16:45:49.715 Success MP: Entering module processor
04.11.2011 16:45:49.715 Success MP: Processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
04.11.2011 16:45:49.716 Success SOAP: request message entering the adapter with user J2EE_GUEST
04.11.2011 16:45:49.716 Success SOAP: Target url: https://connect.hubspan.net/mh/server/tp=NMHG/ssid=DAA6F0E9AC1000BD03A41B363BBFD676
04.11.2011 16:45:49.999 Error SOAP: call failed: java.lang.NullPointerException
04.11.2011 16:45:49.999 Success SOAP: sending a delivery error ack ...
04.11.2011 16:45:49.999 Success SOAP: sent a delivery error ack
04.11.2011 16:45:49.999 Error SOAP: error occured: com.sap.aii.af.ra.ms.api.RecoverableException: java.lang.NullPointerException
04.11.2011 16:45:49.999 Error MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: java.lang.NullPointerException
04.11.2011 16:45:50.000 Error Exception caught by adapter framework: null
04.11.2011 16:45:50.022 Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: java.lang.NullPointerException.
04.11.2011 16:45:50.037 Success The message status set to WAIT.
u2022If we are resending the failed message from XI RWB, it is getting failed again with the same error. On the other hand if we are initiating the message again from SRM to Hubspan for the same PO, it is getting processed successfully in RWB but still not showing XML payload in RWB.
u2022If we are getting the payload from XI MONI for the failed message and doing a test with component monitoring in RWB, it is working fine.
Please help me to solve this issue.
Thanks
Sumit

Hi Sumit,
From my experience, when you transfer SAP POs through PI to external webservice, there should be some validation happens at the webservice layer of the target system before the web service passes the original information to their application layer. The validation can be anything like checking the Vendor address, Checking the correctness of the order ...etc etc . So i would suggest to ask your external web service folks to check if they have any validation in place before they pass the data to their application layer.
As you said only some POs/XMLs are failing, i strongly feel that this could be the issue.
Please note if you receive response code other than 200 from webservice, SOAP adapter treats that as error and send the same message back to AE.
Normally webservices won't send 200 code for any validation error
PS: you can still try to use XMLSpy to post the failed message to the web service to know the exact cause.

Error in SOAP Adapter Response

I am getting the following Error in SOAP Response
... but when i tried the with ALTOVA XML SPY its working fine..
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PARSING">ADAPTER.SOAP_EXCEPTION</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>soap fault: Registration Method error</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>

hi,
check the XML that you send to the WS
if the server returned this soap fault it might mean that XML was not correct .
also take a look at the default.trc log file from visual administrator-> server -> services -> log viewer -> locations -> com -> aii -> bc -> soap
regards
kummari
Edited by: kummari on Jul 29, 2008 5:40 AM

Soap Receiver adapter - 401 error

I am getting following error with soap receiver,
com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Unauthorized
I am able to consume the webservice with SOAP UI without any difficulty. I have tried with both the endpoint URL and WSDL url without success. I have tried with/without 'Do not use SOAP envelope'. I am not sure what is wrong. When the message is sent via PI, he is not able to look at the payload (while performing the trace) , while he is able to view the actual soap message with SOAP UI.
When i type the ENDPOINT url in my http address, i get a 'page not found' error.
Any ideas as to what i could be missing?

One more interesting behaviour when I was sending from SOAP UI, The request was posted twice, meaning there were two POST actions in my TCPGATEWAY listening port, while there was only one request via PI.
Wnen my partner put a trace, the SOAP envelop was missing in their TRACE for PI file while the SOAP envelop was available for SOAP ui message (in the second request). Could it have something to do with a fact that we are doing HTTP 1.1with soap uI While PI is HTTP 1.0 (HTTP 1.1 being a persistent connection resulting in second request)
Trace on the partner side,
PI Message
POST /Services/Calculator/Version1/Calculator.asmx HTTP/1.0
accept: * / *
host: www.html2xml.nl
user-agent: SAP-Messaging-com.sap.aii.af.sdk.xi/1.0505
callingtype: SJM
content-id: <soap-4EB90CC8537E011DE1008000CDEB6913>
content-type: text/xml; charset=utf-8
content-length: 888
SOAPAction: "http://tempuri.org/Add"
HTTP/1.0 401
WWW-Authenticate: Basic realm="CASM"
Content-Type: text/html;charset=utf-8
Content-Length: 40
Date: Thu, 10 Nov 2011 11:50:13 GMT
Connection: close
SOAP UI log
POST /Services/Calculator/Version1/Calculator.asmx HTTP/1.1
accept-encoding: gzip,deflate
content-type: text/xml;charset=UTF-8
soapaction: "Create"
user-agent: Jakarta Commons-HttpClient/3.1
host: www.html2xml.nl
content-length: 2496
HTTP/1.1 401
WWW-Authenticate: Basic realm="CASM"
Content-Type: text/html;charset=utf-8
Content-Length: 40
Date: Thu, 10 Nov 2011 12:04:40 GMT
POST /Services/Calculator/Version1/Calculator.asmx HTTP/1.1
accept-encoding: gzip,deflate
content-type: text/xml;charset=UTF-8
soapaction: "Create"
user-agent: Jakarta Commons-HttpClient/3.1
content-length: 2496
authorization: Basic U1lTX1dFQl9TQVBQSTo=
host: www.html2xml.nl
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
</soapenv:Envelope>
HTTP/1.1 200
Set-Cookie: JSESSIONID=A48C8808315935EFD7AFBA8B4B96FC62; Path=/xx
Keep-Alive: timeout=1200000, max=1000
Connection: Keep-Alive
Content-Encoding: gzip
Content-Type: text/xml;charset=utf-8
Content-Length: 2882

Soap Receiver Adapter Error. Pls advice urgent

Hi All,
While using Soap Receiver Adapter for synchronous communication
*My Soap Request is:*
<?xml version="1.0" encoding="UTF-8" ?>
<ns1:SendMessage xmlns:ns1="urn:MMWebSrvService">
<strFrom>XI</strFrom>
</ns1:SendMessage>
*My Soap Response from server is:*
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<tns:SendMessageResponse xmlns:tns="urn:MMWebSrvService" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<return xsi:type="xsd:int">-1</return>
<strErrorDescription xsi:type="xsd:string">String reference not set to an instance of a String. Parameter name: s</strErrorDescription>
</tns:SendMessageResponse>
How to resolve the error.
Regards

Henry,
Your xml message is not xsd compliant...see if you can generate a xml message using your wsdl with random values, compare that to your imcoming msg..and thats your issue..
Hope that helps
Regards
Ravi Raman
Reward points if helpful !

Error in Soap Reciever Adapter?

Similar Messages

Maybe you are looking for