Error in SOAP channel in SAP PI 7.31

Hey Experts,
We have a scenario in which we send IDOCs to our Business Partners via a SOAP channel. It is an asynchronous scenario. However, we are getting the following error:
MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.security.lib.exception.SecurityException: SecurityException in method: apply( Message, CPALookupObject ). Message: SecurityException in method: apply( Message, CPALookupObject ). WSSEThread-Exception: SecurityException in method: run(). Message: [com.sap.ASJ.wssec.030153] Error during the processing of the encryption element. Error was: org.w3c.dom.DOMException HIERARCHY_REQUEST_ERR: An attempt was made to insert a node where it is not permitted. .. To-String: com.sap.security.core.policy.exceptions.ProcessException: [com.sap.ASJ.wssec.030153] Error during the processing of the encryption element. Error was: org.w3c.dom.DOMException HIERARCHY_REQUEST_ERR: An attempt was made to insert a node where it is not permitted. .. Key: 0153; To-String: com.sap.aii.security.lib.exception.SecurityException: SecurityException in method: run(). Message: [com.sap.ASJ.wssec.030153] Error during the processing of the encryption element. Error was: org.w3c.dom.DOMException HIERARCHY_REQUEST_ERR: An attempt was made to insert a node where it is not permitted. .. To-String: com.sap.security.core.policy.exceptions.ProcessException: [com.sap.ASJ.wssec.030153] Error during the processing of the encryption element. Error was: org.w3c.dom.DOMException HIERARCHY_REQUEST_ERR: An attempt was made to insert a node where it is not permitted. .. Key: 0153. To-String: com.sap.aii.security.lib.exception.SecurityException: SecurityException in method: apply( Message, CPALookupObject ). WSSEThread-Exception: SecurityException in method: run(). Message: [com.sap.ASJ.wssec.030153] Error during the processing of the encryption element. Error was: org.w3c.dom.DOMException HIERARCHY_REQUEST_ERR: An attempt was made to insert a node where it is not permitted. .. To-String: com.sap.security.core.policy.exceptions.ProcessException: [com.sap.ASJ.wssec.030153] Error during the processing of the encryption element. Error was: org.w3c.dom.DOMException HIERARCHY_REQUEST_ERR: An attempt was made to insert a node where it is not permitted. .. Key: 0153; To-String: com.sap.aii.security.lib.exception.SecurityException: SecurityException in method: run(). Message: [com.sap.ASJ.wssec.030153] Error during the processing of the encryption element. Error was: org.w3c.dom.DOMException HIERARCHY_REQUEST_ERR: An attempt was made to insert a node where it is not permitted. .. To-String: com.sap.security.core.policy.exceptions.ProcessException: [com.sap.ASJ.wssec.030153] Error during the processing of the encryption element. Error was: org.w3c.dom.DOMException HIERARCHY_REQUEST_ERR: An attempt was made to insert a node where it is not permitted. .. Key: 0153
If anyone has some information or views to share on this, kindly do so. I have attached a screenshot for your reference.
Regards,
Pritish

Hi Jens,
Thank you very much for your prompt reply to my post. We did go through the note and since we are on Patch 11, we are not sure exactly how relevant it is to us.
However, I would be much obliged if you could clear up one thing. We are using an SOAP adapter to send IDOCs, and the note that you have advocated pertains to an IDOC adapter.
Will the note still be able to help?
Regards,
Pritish

Similar Messages

Error in SOAP Sender Communication Channel

Hello Gurus,
I am trying for a SOAP (Axis) -> PI -> IDOC scenario and getting an error while sending message to SOAP Channel.
Message structure used
<?xml version="1.0" encoding="UTF-8"?>
<MaterialData>
<field1>value</field1>
more fields
</MaterialData>
Basically a XML message.
I am getting below error message for Axis (channel monitoring):
MP: exception caught with cause org.xml.sax.SAXException: Bad envelope tag: MaterialData
Can you please let me know what should be the message format when testing Axis? I do not intend to use any SOAP envelope.
I have already referred: Re: SAP PI 7.0 Receiver SOAP Axis (Bad envelope tag: html)
Please help.
Thank you!

Hello,
Can you please let me know what should be the message format when testing Axis? I do not intend to use any SOAP envelope.
Correct me if I'm wrong, but I think you will only be able to plain message to the Axis sender when using REST. See SAP Note 1039369 FAQ XI Axis Adapter, under Sender Adapter General Question 35.
35. Can I post a plain no-soap request (REST) to the sender adapter servlet?
Yes. You need to include a query parameter rest in the request URL, as http://host:port/XIAxisAdapter/MessageServlet?...&rest. For the availability of this feature, refer to Note 1448849.
All the other messages require a SOAP Envelope.
Hope this helps,
Mark

SOAP Channel Error

Hi,
I am getting the following error in soap receiver communication channel.
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: uatserver1.premierfoods.co.uk: java.net.UnknownHostException: uatserver1.sdd.co.uk
I tried individually copying the tarter url and pasting it in Internet Explorere. I did get the response.
I am not sure why I am getting an error.
I have given the target URL as http://<url>
Let me know what needs to be done on this.
Regards
Krish

>>> tried individually copying the tarter url and pasting it in Internet Explorere. I did get the response.
Using IE and do the above test is just ping test and it's not complete test. Import the target WSDL in soap ui client or xmlspy and see whether you get the response.
Hints: After you successfully test in soap client tool or xmlspy ,use that wsdl url in the comm channel. Are u specifying soap action in the soap cc? If you dont find action or operation in the wsdl, then leave blank in action. This will help.

SOAP channels in rwb showing error "No Adapters registered for this channel

SOAP channels in rwb is showing error "No Adapters registered for this channel",
what is the problem?
i tried to locate and restart the SOAP adapter from Visual admin, but couldnt find it in visual admin, pls help in locating it in visual admin

Hi,
In Visual Admin, Cluster tab --> Server -> Services -> Deploy --> Radiobutton Application
--> sap.com/com.sap.aii.af.soapadapter --> Press start / stop
This way youmay restart the SOAP adapter.
Also Please check if there is any cahce problem, Try to refresh it. & SAP Note- 856597
Thanks
Swarup

Receiver SOAP channel error-- Cant parse the document; HTTP 200 OK

Hi All,
I am facing below error in SOAP receiver communication channel
SOAP: Error occurred: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: Cant parse the document; HTTP 200 OK
If I use "Do Not se SOAP Envelop" in receiver communication channel then it shows successfully delivered in message monitoring but never reached to target application. And if I uncheck "Do Not se SOAP Envelop" then the error is as I mentioned above.
Both ways it not working foe me.
Please advice.
Thanks
Shivi

Hi
I had a similar issue recent times and I have enablede the xpi inspector to check the logs of the request and the response sent and received...
Based on that you can check whether your payload is able to sent to receiver in proper format or any other issues..
Also try to check the payload format using the SOAPUI whether the ws is working fine for that or not.
HTH
Rajesh

"Unauthorized" error for SOAP receiver channel

Hi all,
I have a scenario in which I am calling a .NET web service from a UDF in which the XML payload is constructed manually. I have configured a SOAP receiver channel. Also, since the web service needs certificate authentication, I have checked the corresponding parameter in the SOAP channel and selected appropriate client certificate.
When I execute the mapping, I get the following error -
com.sap.aii.mapping.lookup.LookupException: Exception during processing the payload.Problem when calling an adapter by using communication channel SOAP_RCV_IMWS_Change (Party: , Service: IMWS, Object ID: dda07d364ca73d4ab9e89e562a971b36) XI AF API call failed. Module exception: 'com.sap.aii.af.ra.ms.api.RecoverableException: invalid content type for SOAP: TEXT/HTML; HTTP 401 Unauthorized: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 401 Unauthorized'. Cause Exception: 'invalid content type for SOAP: TEXT/HTML; HTTP 401 Unauthorized'.
Is this related to error in certificate authentication process, OR wrongly formed XML payload OR anything else ?
Regards,
Shankar

No. I didn't provide any login info. The web service doesn't specify username login requirement. Instead, it needs client certificate for authentication, which I provided in SOAP receiver channel.
I am testing the web service by executing the message mapping. The web service was executed successfully from its 'Test Page' like for SAP web services we have web service navigator. So it runs ok from that test page, but gives error when called from UDF.
Regards,
Shankar

ABAP-Proxy to SOAP: Error in SOAP Adapter

Hi!
I would like to implement ABAP-Proxy to SOAP scenario.
Unfortunately my SOAP receiver channnel has the following error:
SOAP: call failed: java.io.IOException: No SOAP Envelope but 1 definitions; HTTP 200 OK
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: No SOAP Envelope but 1 definitions; HTTP 200 OK: java.io.IOException: No SOAP Envelope but 1 definitions; HTTP 200 OK
Furthermore the call of /sap/bc/soap/rfc of business system B is erroneous
http://<server system B>:8000/sap/bc/soap/rfc
Here I get the error: HTTP 500 Internal Server error
Can some one help me to solve this problem?
Thank you very much!
regards
Holger

Hi,
Are you using the webservice exposed by SAP or it is third party webservice. Can you explain your complete scenario? What is the url you have given in your receiver SOAP Channel? Was that no configured earlier?
If at all you are using the SAP webservice, the wsdl link should be.
http://<server>:<http port>/sap/bc/soap/wsdl11?services=BAPI_MATERIAL_EXISTENCECHECK&sap-client=200
The target url you will be able to see in the wsdl itself also
amit

Error in SOAP receiver adapter.

Hi All,
Problem : 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

Hello All,
I am getting the below error in the sender communication channel for FILE - PI -SOAP scenario.
i am using integrated configuration in configuration.
"Transmitting the message using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error encountered while executing mapping: com.sap.aii.af.service.mapping.MappingException: Could not determine mapping steps for message c24a403b-b048-11e0-9c28-00001e07abf4."
Specified operation mapping in the integrated configuration correctly. cache is also up to date.
Could you please let me know what could be the issue.

Hi ,
Pleas make sure your system is PI 7.1 EHP1 otherwise you cant do this.
also you cant use ABAP mapping or paremeterized mapping with AAE also dont able to see error message in SXMB_MONI
I will suggest you to go with classical approach. or Atleast first test the end to end interace with classical ID IR approach.
And then go with AAE for performance improvement
Your error may be for response mapping for SOAP.
Please set messaging.syncMessageRemover.removeBody" parameter to "false",in the SAP XI AF Messaging Service
refer this help.
http://help.sap.com/saphelp_nw04s/helpdata/EN/59/25ee41c334c717e10000000a155106/frameset.htm
This .property will allow you to error analysis soap response.
Do you have any fault message structure and mapping in SOAP receiver side?
Do a dummy change in the maaping and activate and then do complete cache refresh0
Delta Cache Refresh:
CPA-Cache and Mapping Runtime Cache are updated independently, i.e.
1.
Mappings objects per activation/change are transferred to ALL Mapping Runtime Caches of all Advanced Adapter Engines
2.
CPA-Cache-Refresh is usually carried out after activation/change of directory objects. Objects are just transferred to the Advanced Adapter Engine where configured to be used
Can be viewed in the Cache Monitoring of the RWB. (other monitoring is reused; no SXMB_MONI).
Refer this:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70b8adc3-728c-2a10-7fad-d43f29074ef8?quicklink=index&overridelayout=true
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/700058f0-b1a1-2a10-39a8-ab2627b87cfa?quicklink=index&overridelayout=true

Error capturing SOAP fault for Sync Messages

Hi
We have a Sync interface which makes a Proxy call from ECC to PI and then PI makes Soap Sync call to Web application. We are having issues when handling Exceptions. Sender is getting misleading errors in response, even though they are application errors the proxy sender is getting error like MappingObjectNotFound.
When debug the PI system, PI is truncating error info when it return the reponse.
Below is the scenario of Synchronous interface:
ECC(Proxy) -> PI(Soap Receiver Adapter) -> MasterDataApp-(Webserver)
Below is the actual response from Webserver (Extracted via TCPGW sniffer):
<?xml version="1.0" encoding="utf-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Server.userException</faultcode>
<faultstring>*java.rmi.RemoteException: No Messages Found*</faultstring>
<detail>
<ns1:hostname xmlns:ns1="http://xml.apache.org/axis/">hostname.com</ns1:hostname>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
But PI receives this response payload like this :
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
<ns1:hostname xmlns:ns1="http://xml.apache.org/axis/">hostname.com</ns1:hostname>
and then Sync Request mesasge fails with below error because of the unexpected response payload as shown above:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <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="MAPPING">NO_MAPPINGPROGRAM_FOUND</SAP:Code>
<SAP:P1>Object ID B0CC6B27847A368AA04F4171EF6460F4 Software Component 86524CE0304911DEAE48CC6C83461631</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Mapping program is not available in runtime cache: Object ID B0CC6B27847A368AA04F4171EF6460F4 Software Component 86524CE0304911DEAE48CC6C83461631</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Also in the response message see this error message:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<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>
Please let me for any clues how to handle this error response.
Thanks,
laxman

Hi Laxman,
SOAP Adapter cannot handle fault responses. I understand your issue. You even want to send the errorneous response from the Webservice as a payload back to the sender. But because of application error from Webservice, you are getting an error in the response message (Mapping Not found). SOAP Adapter cannot handle application error (i.e you will not get the errorneous response in form of payload) . For details please read below:
The receiver adapter expects a SOAP message as response. For synchrnous calls, a successful response should be returned with HTTP 200. In this case, the content of the SOAP body will be returned to the caller as the response payload. When some error occurs, the SOAP message may contain the SOAP fault element. In this case, when the fault detail element is not empty, its content will be returned as the fault payload in an application error message. For others, a system error message will be returned to the caller.
HTTP/1.1 200 OK
Content-Type: text/xml; charset="utf-8"
<SOAP:Envelope
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Body>
<m:GetLastTradePriceResponse xmlns:m="Some-URI">
<Price>34.5</Price>
</m:GetLastTradePriceResponse>
</SOAP:Body>
</SOAP:Envelope>
will result in an application response message with response payload
<m:GetLastTradePriceResponse xmlns:m="Some-URI">
<Price>34.5</Price>
</m:GetLastTradePriceResponse>
HTTP/1.1 500 Internal Server Error
Content-Type: text/xml; charset="utf-8"
<SOAP:Envelope
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Body>
<SOAP:Fault>
<faultcode>SOAP:MustUnderstand</faultcode>
<faultstring>SOAP Must Understand Error</faultstring>
</SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
will result in a system error message.
HTTP/1.1 500 Internal Server Error
Content-Type: text/xml; charset="utf-8"
<SOAP:Envelope
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Body>
<SOAP:Fault>
<faultcode>SOAP:Server</faultcode>
<faultstring>Server Error</faultstring>
<detail>
<e:myfaultdetails xmlns:e="Some-URI">
<message>My application didn't work</message>
<errorcode>1001</errorcode>
</e:myfaultdetails>
</detail>
</SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
will result in an application error message with fault payload
<e:myfaultdetails xmlns:e="Some-URI">
<message>My application didn't work</message>
<errorcode>1001</errorcode>
</e:myfaultdetails>
In order to send the erroneous response as a payload to the sender, you should develop flow in below manner:
ECC(Proxy) -> PI --> ECC(Proxy)
In PI make a SOAP lookup. The response of the SOAP lookup will contain the response given by the WebService (it can be a vaid response or an application error in WebService). Now map this response to the proxy...In this way you can handle the application error msgs from webservice..
I hope this helps you...
Regards,
Rakesh Sharma

SET_PAYLOAD_FAILED error in SOAP to Proxy scenario

Hi PI Experts,
We have an inbound syncronus interface (Non sap system to SAP) using the SOAP to Proxy scenario.
When we test the interface using any soap tool like soapui it is working fine but when the interface is triggered end to end from source system then the below error is getting dispalyed on source system.
500 Internal Server Error
In XI below is the error message -
<?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>XIProxy</SAP:Category>
<SAP:Code area="ABAP">SET_PAYLOAD_FAILED</SAP:Code>
<SAP:P1>IN</SAP:P1>
<SAP:P2>REQUEST</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Internal error when completing the message object (setting the payload, direction: IN message: REQUEST)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Can any please let me know what is the issue here?
Appreciate your help.
Regards,
Jitender

We had a similar issue with a Synchronous Interface
The interface worked perfectly when sending the request directly to the integration server, but when sending it using SOAP the issue appeared.
It was very tricky to solve it because we had similar interfaces that worked without any issues.
SOLUTION: Create a new Service interface with a new name different from the one failing. And make sure The Message Types are in the same namespace as the service interface.
Why?:
The issue turned out to be in the sender agreement, and name-spacing issues.
Our Outbound Service Interface belonged to one SWCV and ns, We will call it "ns1:SI_A_OUT".
In PI 7.3, and I believe 7.11 also, the you no longer assign a default interface in the to the SOAP communication channel sender agreement pair.
Therefore the SOAP adapter determines the soap method from the payload. If The internal message type in the soap message belong to different namespace, the the java method getMessage() does not find the correct XML node, therefore does not find the payload.
<"ns1:SI_A_OUT">
...<ns2:MT_element>
getMessage( ns1:MT_element)
We are not sure if the issue is the implementation of the SOAP protocol or in the WSDL generation. But this issues seem to create orphan object during runtime, and even if you re-implement the complete interface, the sender agreement seems to be corrupt.
Therefore the only was we could solve this, was to move our MT to the same namespace as the service interface and rename the interface "ns1:SI_A2_OUT"
Hope this helps someone.
Juan Francisco Zurita Duque
NNIT A/S

Error in SOAP synchronus request.

Hi,
I'm trying to make a SOAP call to Salesforce.com. I've created my own soap envelope using xsl(disabled soapenv in the channel).
Following is my payload:
<?xml version="1.0" encoding="utf-8"?>
<soapenv:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
 <soapenv:Header>
 <SessionHeader soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next" soapenv:mustUnderstand="0" xmlns:ns1="urn:horizon:sesionmgmt">
 <ns1:sessionId>aaaaaaaa</ns1:sessionId>
 </SessionHeader>
 </soapenv:Header>
 <soapenv:Body>
 <upsert xmlns="urn:enterprise.soap.sforce.com">
 <externalIDFieldName>SAP_Customer__c</externalIDFieldName>
 <sObjects xsi:type="ns1:Account" xmlns:ns1="urn:sobject.enterprise.soap.sforce.com">
 <ns1:Name>EntUpdatee</ns1:Name>
 <ns1:SAP_Customer__c>ExternalId</ns1:SAP_Customer__c>
 </sObjects>
 </upsert>
 </soapenv:Body>
</soapenv:Envelope>
This is the error I'm getting in Moni:
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<soapenv:Fault>
 <faultcode>soapenv:Server</faultcode>
 <faultstring>org.xml.sax.SAXException: Deserializing parameter 'sObjects': could not find deserializer for type Account</faultstring>
 <detail/>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
The strange thing is, If I copy and paste the payload into a soap client, it works fine! So looks like this error is on XI side. If so, how do I fix it?
Regards,
Harsh

I'll check that, but why should it give an error, when it works from a soap client??
PS: The error in moni is actually:
<?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="HTTP">ADAPTER.HTTP_EXCEPTION</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>HTTP 500 Internal Server Error</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
What I mentioned earlier is the payload... don't know if it makes a diff.

SOAP Channel - ADAPTER.HTTP_EXCEPTION

Hi,
I have a receiver SOAP Channel and when i tried sending messages.
Am getting an adapter exception.
Please guide if someone has faced with the same kind of error
Thanks
Sebin
The error response is pasted below.
<?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="HTTP">ADAPTER.HTTP_EXCEPTION</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>HTTP 401 Access Denied</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thanks
Sebin

hi
Error: HTTP_RESP_STATUS_CODE_NOT_OK 401 Unauthorized
Description: The request requires user authentication
Possible Tips:
Check XIAPPLUSER is having this Role -SAP_XI_APPL_SERV_USER
If the error is in XI Adapter, then your port entry should J2EE port 5<System no>
If the error is in Adapter Engine
then have a look into SAP note- 821026, Delete the Adapter Engine cache in transaction SXI_CACHE Goto --> Cache.
May be wrong password for user XIISUSER
May be wrong password for user XIAFUSER
for this Check the Exchange Profile and transaction SU01, try to reset the password -Restart the J2EE Engine to activate changes in the Exchange Profile After doing this, you can restart the message
source :: /people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi
regards
Ramesh P

Version mismatch error in SOAP interface

Hi
Scenario is SOAP to SOAP.
Sending request by SOAP UI to receiver webservice.
Interface was perfectly done & tested successfully.
Then we have done some changes in Receiver soap channel ...due to some error the changes were reverted
but now i am getting an error while testing as " version mismatch"
The provider webservice is working fine as we have tested it without PI.
The complete discription of error is as follows
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
 <soapenv:Body>
 <soapenv:Fault>
 <faultcode>soapenv:Server.generalException</faultcode>
 <faultstring>senderChannel '54cfea9d7e9b3ad2895bbe47a9aaa877': Catching exception calling messaging system; nested exception is:
 com.sap.engine.interfaces.messaging.api.exception.MessagingException: Version Mismatch</faultstring>
 <detail>
 <ns1:hostname xmlns:ns1="http://xml.apache.org/axis/">usa42113</ns1:hostname>
 </detail>
 </soapenv:Fault>
 </soapenv:Body>
</soapenv:Envelope>
Please suggest the reason for this error & the possible solution
Regards
Abhijit

Hi prateek
yes, we are using Axis Framework.
Earlier the interface was working fine with same configuration...But now its giving error as " Version mismatch"
Regards
Abhijit

How to test HTTP request for Sender SOAP Channel

Hi all,
We are testing Soap requests from SOAP UI tool.
We are able to call HTTPS calls from SOAPUI tool, but unable to call HTTP request.
we eanbles ssl and able to post https requests.
please advice .
Thanks
RGDASARI

Hi Stefan, I configured the way you have put it, but I get the error "no receiver could be determined"
Here are my settings:
Sender service - HTTP_SEND
sender o/b interface - PROD_MSG_INT_OB_ASYNC
receiver service - FILE_RECEIVE
receiver i/b interface - PROD_MSG_INT_IB_ASYNC
receiver communication channel - FILE adapter
JAVA script:
String Party = "MFC";
String Service = "HTTP_SEND";
String XINameSpace = "mfc%3Anamespace1";
String Interface = "PROD_MSG_INT_OB_ASYNC";
String Url = "http://nemo:8000/sap/xi/adapter_plain?";
XML DATA File:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:PRODUCT xmlns:ns0="mfc:namespace1">
<ID>E</ID>
<NAME>thank god</NAME>
<BRAND>SOME BRAND</BRAND>
</ns0:PRODUCT>
Stefan Am I missing anything?
XML error message:
<?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>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_BE</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
It would be great if you have solution for this.
Regards
felix

Error in SOAP channel in SAP PI 7.31

Similar Messages

Maybe you are looking for