Receiver soap : Error ADAPTER.SOAP_EXCEPTION

Hi all,
My Scenario is IDOC -> XI -> WEBSERVICE using BPM & SOAP adaptor.
when i send idoc from R/3 it is going Xi
From Xi to web service using WSDL Request message .it is not reach to web service(connection is ok but wsdl request massage is not going properly) .
sxmb-moni :error is
<?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: com.sap.webservice.SchemeTopupDeliveryService</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
<SAP:AdditionalText>soap fault: com.sap.webservice.SchemeTopupDeliveryService</SAP:AdditionalText> : this service is not related to my service (It is showing wrong service name)
Pleas tell me where error is happened

this service is not related to my service (It is showing wrong service name)
This is the reason, you somehow call the wrong web service. But are you talking about BI or XI here?
Best regards
Dirk

Similar Messages

PI 7.11 Receiver SOAP (Axis) Adapter with MTOM (Attachments)

Hello,
Iu2019m trying to configure the Receiver SOAP (Axis) adapter for sending SOAP attachments via MTOM to a third-party webservice, but I'm not getting that PI transform the binary encode64 data in an payload element into a MTOM attachment (xop:include).
The configuration looks like this:
Transport Protocol: HTTP (Axis)
SOAP Version: 1.2
Encapsulation Format: MTOM
Keep Attchments: enabled
Payload Extraction: SOAP Body Child
First of all, could you confirm if this is supported?
Or Axis only supports MTOM for the transport protocol 'File (Axis)' like it seems refered in [Configuring the Receiver Axis SOAP Adapter|http://help.sap.com/saphelp_nwpi711/helpdata/en/45/a3c48c87cd0039e10000000a11466f/frameset.htm]
Can you please provide me some guidance here?
Thanks in advance!
Kind Regards,
Alexandre

Hello,
I am facing the exact same issue.
I can't seem to set the cookie in the http header after following the guide.
Cookie: WSL-credential=MyOwnCookie
I managed to set the SOAPAction though.
Anyone has any ideas?

Error in Receiver SOAP AXIS adapter.

I have configured a receiver soap adapter and get the below error. Any help with this? Since I am able to see the Axis option in the adapter configuration, this means the axis framework is deployed or does it need to be delpoyed?
Delivering 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: javax.ejb.TransactionRolledbackLocalException:
(Failed in component: sap.com/com.sap.aii.axis.app, BC-XI-CON-AFW-TAD) Exception raised from invocation of public
com.sap.aii.af.lib.mp.module.ModuleData com.sap.aii.adapter.axis.modules.AFAdapterBean.process
(com.sap.aii.af.lib.mp.module.ModuleContext,com.sap.aii.af.lib.mp.module.ModuleData) throws
com.sap.aii.af.lib.mp.module.ModuleException method on bean instance
com.sap.aii.adapter.axis.modules.AFAdapterBean@681b240 for bean

Had to deploy the axis framework.

Receiver soap error

Hi,
i have abap proxy 2 soap (sync). and i imported wsdl into IR, which created by target web server(tomcat).
here is target soap adapter info.
target url : http://58.232.198.104:8080/axis/ApprovalService.jws?wsdl
action : Approval
actually, you can access above url now. please check
<?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>Application</SAP:Category>
<SAP:Code area="UNKNOWN">APPLICATION_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>application fault</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="http://xml.apache.org/axis/">hostname</SAP:ApplicationFaultMessage>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
thanks
venjamin

Hi,
i checked this web service can accept and response with this url http://58.232.198.104:8080/axis/ApprovalService.jws?method=Approval&args1=1&args2=2. response value was returned as well. but on sxmb_moni. i got error as above my first contents
on receiver soap adapter;
target url : http://58.232.198.104:8080/axis/ApprovalService.jws
Soap Action : Approval
mapping, i used message type from wsdl impoted into external definition for requets and response.
you can test above url.. little slow.... please check what was my fault
and also why appplication fault is saying hostname?
please help me. is there a special things i have to do for target webservice?
thanks
venjamin

SAP PI 7.3 Receiver SOAP Axis adapter header Cookie

Hello
We are currently working a synchronous scenario like SAPERP --> PI --> WebService.
The WebService requires cookie authentication.
I have successfully tested SOAPUI <-->WebService Scenario.
The Issue is when I try to put the Cookie in the SOAP header using Axis Frame work.
1. I have followed the blog How to Set http-Header Parameters Using the Axis Framework (NW7.0)
Guess the only one available on net.
2. I have checked my http://<host>:<port>//XIAxisAdapter/MessageServle
2.1 and the status of the mandatory components are in green.
3. We are on SAP PI 7.3
When I try to execute the scenario and capture the SOAP request in TCPGateway the following is the result.
POST /ABC/ABCService_v1 HTTP/1.0
Content-Type: text/xml; charset=utf-8
Accept: application/soap+xml, application/dime, multipart/related, text/*
User-Agent: Axis/1.4
Host: MYIPaddress:54000
Cache-Control: no-cache
Pragma: no-cache
SOAPAction: "urn:ABC/DEF/interface/v1.0/TEST/GetCalculation"
Content-Length: 2228
The below is the SOAP header from the soapUI application and I am expecting to achieve something similar/workable one with SAP PI.
POST /ABC/ABCService_v1 HTTP/1.0
Accept-Encoding: gzip,deflate
Content-Type: text/xml;charset=UTF-8
SOAPAction: "urn:ABC/DEF/interface/v1.0/TEST/GetCalculation"
Cookie: WSL-credential=MyOwnCookie
Content-Length: 2512
Host: www.DEVTESTHOST.com
Connection: Keep-Alive
User-Agent: Apache-HttpClient/4.1.1 (java 1.5)
Can anyone pls let me know why I am not able to put the cookie in the SOAP header.
Anyone who have already tried and was successful in this scenario pls do let me know what I am missing.
Thanks in advance.
Regards
Prasanna

Hello,
I am facing the exact same issue.
I can't seem to set the cookie in the http header after following the guide.
Cookie: WSL-credential=MyOwnCookie
I managed to set the SOAPAction though.
Anyone has any ideas?

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.

Error in the Receiver SOAP Adapter

Hello Experts,
I am sending an order number by running a report on the ECC 6.0 server to a web service for publishing the information on the web site. The receiver side is configured as Receiver SOAP Adapter . I am getting the following error in the SXMB_MONI Transaction.
com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Not enough message parts were received for the operation.
Kindly let me know to overcome this problem.
Thanks
Best Regards
S Joshi

Hi Ramesh,
The message Iam getting in MONI is as follows:
com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Not enough message parts were received for the operation.
This is the response for the request that i am sending for order creation. I did checked the fields also it is same and the values of the fields too. they all are correct. Over and above this it was working fine till last week , but suddendly this week I am getting this error.
Regards

Error:SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to read request. --- There is an error in XML document (1, 447). --- Input string was not in a correct format.

Hi All,
We have a scenario of FTP-->PI---> Webservice. While triggering the data in the FTP, it is failing in the PI with the below error
SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to read request. ---> There is an error in XML document (1, 447). ---> Input string was not in a correct format.
Can you please help?

Hi Raja- It seems to be a data quality issue.
Check for the value @ 1447 position in the xml message that you are trying to send to web service..
may be a date filed/decimal value which is not in expected format.

Receiver SOAP Adapter error

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" ?>
- 
- <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

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

ADAPTER.HTTP_EXCEPTION, HTTP 500 Internal Server Error, in Receiver soap A

Greetings All,
In my scenario i am calling external service of SFDC using receiver soap adapter but i am facing below error in the response.
ADAPTER.HTTP_EXCEPTION, HTTP 500 Internal Server Error
I am creating the soap structure/envelope using Java mapping since need to add additional parameter in soap header.
I am setting the URL in java UDF using parameter TServerLocation.
In comm channel checked "do not use soap envlope" also set the format to text/xml using MessageTransformBean.
The service was working fine when tested in SoapUI tool.
Looking forword for your help and will be appreciated.
Thanks,
Sandip

Hello Sandip, I hope you are doing fine!
I`m not sure if you are using a sync or async scenario...
The behavior that you describe is the expected behavior for SOAP receiver adapter in nosoap mode, asynchronous case.
The explanation that lies behind it is that in nosoap mode the bahavior is just similar to pure HTTP communication. An HTTP 4/5 error received from the target server is treated as HTTP internal error and logged into AFW as an error. The message in an asynchronous scenario without acknowledgements is normally seen as successful on IE side as it is successfully sent to the target system. It can be even successfully consumed by the target webservice, but for amo other reason, the HTTP request from SAP PI to the target system returns HTTP 500 error.
If you ask for system delivery acknowledgements, you should get a non-successful delivery acknowledgement.
In synchrnous scenarios, when a response is expected, the behavior is different.
If this is a sync scenario, there is an official patch released on the service marketplace. SAP Note 1533195 is released.
In addition to deploying the patch, apply the additional configuration steps. As per this note, for the default module
sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
you will need to set:
Module Key = soap
Parameter Name = noSOAPMakeSysErrFromResponseFault
Parameter Value = false
If you need to bypass the HTTP errors in the communication with the target system, you need to apply note 1055678.
To apply it, just add for the default module
sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean in your receiver
channel, Modules tab the following:
Module Key = soap
Parameter Name = XMBWS.NoSOAPIgnoreStatusCode
Parameter Value = false
If you need any SOAP fault related behavior or any other SOAP related feature, you should setup the channel to run normal SOAP mode, since as already mentioned nosoap mode is used now.
In addition, check note:
856597 - FAQ: XI 3.0 / PI 7.0 / PI 7.1 SOAP Adapter
section "1. Sender Connection"
Q: I get a server error "500 Internal Servler Error" from the
adapter's servlet. What went wrong?
and get the trace to give you more details of the error.
One more thing, VERY IMPORTANT.
I STRONLGY recommend you to update all XI-PI components to latest patch available in the Service Marketplace. Thery are:
XITOOLS, XIESR, XIAF, XIAFC, MESSAGING, XIGUI. Some of them might not be present depending on the release of you system. e.g: 3.0, 7.0, 7.1
I hope this helps you.
Cheers
Jorge Eidelwein

Error in applying security settings in Receiver SOAP Adapter

Hi,
I've used Web Services Security (Oasis standard) and the digital signature and encryption certificate in receiver SOAP adapter and the corresponding Sender Agreement, for adding digital signature and encrypting the message. While sending the message we are getting an error in the adapter engine as below. If anyone can throw light on this it'll be highly appreciated :
2008-07-18 17:00:21 Error SOAP: error occured: com.sap.aii.af.ra.ms.api.RecoverableException: java.security.PrivilegedActionException: com.sap.aii.af.security.impl.exception.MessageSecurityException: MessageSecurityException in Method: ApplyMessageLevelSecurity.run(). AccessControlException. Please check that your Code has the XiSecurityRuntimePermission.Context: com.sap.aii.af.security.impl.exception.MessageSecurityException: Exception in Method: apply( Message, CPALookupObject ). General exception, no further informations. Message: MessageSecurityContext in Method: apply( Message, CPALookupObject ). ApplyThread-Exception Message: SAXException in Method: run().; To-String: com.sap.aii.af.security.impl.exception.MessageSecurityException: SAXException in Method: run().. To-String: com.sap.aii.af.security.impl.exception.MessageSecurityException: MessageSecurityContext in Method: apply( Message, CPALookupObject ). ApplyThread-Exception Message: SAXException in Method: run().; To-String: com.sap.aii.af.security.impl.exception.MessageSecurityException: SAXException in Method: run()..
2008-07-18 17:00:21 Error Exception caught by adapter framework: java.security.PrivilegedActionException: com.sap.aii.af.security.impl.exception.MessageSecurityException: MessageSecurityException in Method: ApplyMessageLevelSecurity.run(). AccessControlException. Please check that your Code has the XiSecurityRuntimePermission.Context: com.sap.aii.af.security.impl.exception.MessageSecurityException: Exception in Method: apply( Message, CPALookupObject ). General exception, no further informations. Message: MessageSecurityContext in Method: apply( Message, CPALookupObject ). ApplyThread-Exception Message: SAXException in Method: run().; To-String: com.sap.aii
2008-07-18 17:00:21 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.security.PrivilegedActionException: com.sap.aii.af.security.impl.exception.MessageSecurityException: MessageSecurityException in Method: ApplyMessageLevelSecurity.run(). AccessControlException. Please check that your Code has the XiSecurityRuntimePermission.Context: com.sap.aii.af.security.impl.exception.MessageSecurityException: Exception in Method: apply( Message, CPALookupObject ). General exception, no further informations. Message: MessageSecurityContext in Method: apply( Message, CPALookupObject ). ApplyThread-Exception Message: SAXExce.
Thanks,
Dipankar

hi dipanker,
check the note 856597
its usefull
regards
kummari

Error in Adapter engine of receiver soap adapter

Hi All,
There is one production issue i am currently facing in receiver SOAP adapter while interacting with third party web service(Asynchronous call).
Below is the description i am getting in audit logs.
Success SOAP: completed the processing
Error SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Invalid Session ID or Session Expired
Success SOAP: sending a delivery error ack ...
Success SOAP: sent a delivery error ack
Error MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Invalid Session ID or Session Expired
Error Exception caught by adapter framework: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Invalid Session ID or Session Expired
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: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Invalid Session ID or Session Expired.
Error The message status set to NDLV.
Moreover this is a production issue and interface was running fine till last friday.
Has someone ever faced this issue ?
Please provide your valuable inputs on this.
Thanks
Anku

Hi,
Search in sdn with your error message string,you will find ton of links.
HTTP401 error occurs for many reasons.
still no solution let us know..
Regards,
Raj

Error using SSL on Receiver Soap Adapter

Hi there,
I'm having some problems on connecting to a third-party application running a webservice (meaning, through Receiver Soap Adapter). The third-party appl. demands us to use a SSL connection (its url starts with https), with user authentication through certificate.
We've installed SAP Java Cryptographic toolkit and have a proper certificate configured on the KeyStorage entry, on Visual Administrator.
On Soap Adapter, I've configured HTTP Transport Protocol and have selected the "configure certificate authentication" option and selected the certificate, filled the mandatory fields (target URL and soap action) but I keep getting this error message on SXMB_MONI: "com.sap.aii.af.ra.ms.api.DeliveryException: unable to create a socket".
Is there anything else than installing SAP Java Cryptographic Toolkit to enable SSL on Soap Adapter? Is there another configurations that need to be done?
Thanks in advance,
Henrique.

Hi
can u please tell me, how u r able to resolve the problem
i am also stuck in the same error
basically i am working on SSO b/w three systems.
EP>XI>R/3
i am able to do the SSO between the EP-->XI
but when i try with EP-->XI->R/3 it is giving me error at the receiver side means receiver soap adapter is not accepting the SAP Logon Ticket.
can u please tell me what entries should be given in the certificate authentication fields.
please provide the solution.
Thanks & Regards
Rinku Gangwani

Invalid Content Type Error in Receiver SOAP Adapter

Hello Experts,
Is there a solution for this problem?
I am getting the following error in one of my receiver SOAP adapters:
com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapterFramework:...:com.sap.aii.af.ra.ms.api.DeliveryException: invalid content type for SOAP: TEXT/HTML
I have checked the message I am sending to the receiver adapter and it is XML, ok. After checking this thread: Re: Error in soap receiver adapter and SAP note 856597 I used the TCPGateway program to check what the web service is answering to the adapter request and I found the problem is due to an authentication failure. The TEXT/HTML is an error page the SAP WebAS that hosts the webservice is sending out as response saying no login method succeeded.
However... The webservice URL and basic authentication information, the user and password, are configured correctly. I double checked it and I can also run the webservice using that information directly with wsnavigator on that WebAS.
Checking the request message I found out that the root problem is that the adapter is not sending out a basic authentication request as configured. It is actually sending a header with SAP SSO2 (single signon) ticket instead.
The most strange thing is that I configured another channel exactly the same way and it sends a basic authentication header as it should and works correctly.
So as a workaround I am using this new channel instead of the problematic one but why is the original sending SSO2 tickets? It is configured exactly the same as other channels. I think that SAP SSO authentication is not even supported by XI SOAP channels!!!???
Thanks in advance for your kind responses.
-Sam.

Shabarish:
Thanks for the link, but the real issue is not the request message (regarding your blog) but that the reply from the webservice is the standard HTML page informing no login module succeeded because the adapter is deciding completely on its own that it should use SAP single signon ticket instead of basic authentication as configured.
Volker:
I have performed full and delta cache refreshes to see if the channel performs as configured in the ID but it doesn't. It insists in trying to use SSO2 ticket instead of basic authentication.
I am sure this is an ugly bug in the WEBAS Java, more so because an identically configured channel does use the basic authentication as it should. Anyone knows about a SAP note regarding this? I have performed many searches on the support service but haven't retrieved anything significant.
Thanks for your help guys!
-Sam.

Error in Receiver SOAP adapter - but ok in sxmb_moni

HI,
i am trying to call a WS wich takes only input. so it is a asynchronous call.
I configured CRM-XI-WS.
My sxmb_moni is ok in XI. But when i check Adapter monitoring it is throwing the following error... any help please..
2008-01-03 16:55:53 Error MP: exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to read request. ---> There is an error in XML document (1, 179). ---> The specified node cannot be inserted as the valid child of this node, because the specified node is the wrong type.
2008-01-03 16:55:53 Error Exception caught by adapter framework: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to read request. ---> There is an error in XML document (1, 179). ---> The specified node cannot be inserted as the valid child of this node, because the specified node is the wrong type.
2008-01-03 16:55:53 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: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to read request. ---> There is an error in XML document (1, 179). ---> The specified node cannot be inserted as the valid child of this node, because the specified node is the wrong type..
2008-01-03 16:55:53 Success The asynchronous message was successfully scheduled to be delivered at Thu Jan 03 17:00:53 CST 2008.

I changed my structure to a smiple structure... still i am getting the error...
even i tried taking the payload from sxmb_moni and tested the mapping in IR .. it is failing... saying: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)
my payload is :
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:HSBP_Out_MT xmlns:ns0="http://tsfco:A_TSFCO_CRM_WS_COMM_SWC:CD:HsBpFromCrm">
<Name>test</Name>
</ns0:HSBP_Out_MT>
Edited by: ashok sri on Jan 4, 2008 1:14 AM

Receiver soap : Error ADAPTER.SOAP_EXCEPTION

Similar Messages

Maybe you are looking for