SOAP Receiver - Error in response

Hi Experts,
Please help me with follow.
I have a Interface RFC -> SOAP and in SXMB_MONITOR is OK. But receiver system the data don't OK.
In the Communication Channel i see the error message:
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 503 Service Unavailable
and in Message Monitoring (Message Display), the error message:
2009-03-05 09:01:15 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 503 Service Unavailable
2009-03-05 09:01:15 Error Exception caught by adapter framework: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 503 Service Unavailable
2009-03-05 09:01:15 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 503 Service Unavailable.
But the Webservice is ok and the parameters of the communication channel (URL, Action and other) too.
Thanks in advance.

Hi Pedro,
HTTP Error 503 basically indicates service unavailability.
Check out the following thread : Http 500 internal server error while calling webservice
http://www.checkupdown.com/status/E503.html
Thanks,
Pooja Pandey

Similar Messages

  • SOAP Receiver error - HTTP 500 Internal Server Error

    Hi,
    We have a FILE to SOAP Asynchronous scenario to send data from our PI to customer PI.
    We are sending PGP encrypted file as the payload. So, foll settings have been maintained:
    Do not use SOAP envelope in Sender and Receiver SOAP
    nosoap=true in the URL.
    Message transform bean in the SOAP channels.
    File is successfully sent and received through SOAP protocol.
    But, both the SOAP Receiver and Sender channels are in error:
    SOAP Receiver error:
    SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error.
    As, this is a asynch scenario, we are not expecting the response.
    SOAP sender at customer PI is in error. Error text is not mentioned. It just displays: error occured.
    At both the ends, we do not have Repository objects as there is no mapping.
    Kindly help...
    Thanks,
    Pratibha.

    Hi All,
    For the same scenario, we need to Sign the data using the WebServices Security.
    (We are sending PGP encrypted data as SOAP payload using MTB, i have ticked "Do not use SOAP envelope")
    I have selected WebServicesSecurity as the security profile in the SOAP Receiver and selected "Sign" in the Receiver agreement, have provided our private cert.
    Tried sending a message. Communication channel audit Log shows the message:
    Success MP: Processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
    Success SOAP: request message entering the adapter with user J2EE_GUEST
    Success SOAP: Web Services Security processing...
    Success SOAP: Web Services Security processing skiped. Empty body...
    Success SOAP: completed the processing
    Please suggest how I can apply the WSS..
    Thanks,
    Pratibha.

  • SOAP Receiver Error: HTTP Error response for SOAP Request

    Hi gurus,
    I'm facing a weird error in File --> PI 7.31 java only --> soap receiver proxy.
    The other interfaces runs well. just one get the the following error:
    Exception caught by adapter framework: java.io.IOException: Error receiving or parsing request message: java.io.IOException: HTTP Error response for SOAP request or invalid content-type.
    I check the payload and test in the inbound proxy. on error.
    Any hints?
    Thanks a lot!
    regards
    Christine

    Hello Christine,
    I faced the same issue,
    You can use the beans below to overcome the error.
    And charset should be utf-8

  • Soap Receiver Adapter - No Response Message

    Hi, I've got the following scenario: Idoc - XI - Webservice. I've imported the WSDL from the .NET webservice and used the input and output messages in a syncronous interface.  I've setup a SOAP Receiver adapter with the Webservice details.  Everything is working fine when I call the webservice and the data is received 100% at the target system, but I am not getting ANY response back on XI.
    RECEIVER SOAP ADAPTER Audit LOG:
    2008-01-24 16:41:57 Success SOAP: request message entering the adapter with user J2EE_GUEST
    2008-01-24 16:41:57 Success MP_LEAVE1
    2008-01-24 16:41:57 Success The message was successfully delivered to the application using connection SOAP_http://sap.com/xi/XI/System.
    2008-01-24 16:41:57 Success Acknowledgement creation triggered for type: AckNotSupported
    2008-01-24 16:41:57 Success SOAP: completed the processing
    2008-01-24 16:41:57 Success SOAP: continuing to response message 83638fb0-ca8a-11dc-b36c-00145eed9500
    2008-01-24 16:41:57 Success SOAP: sending a delivery ack ...
    2008-01-24 16:41:57 Success SOAP: sent a delivery ack
    2008-01-24 16:41:57 Success The message status set to DLVD.
    2008-01-24 16:41:57 Success Acknowledgement sent successfully for type: AckNotSupported
    Has it got anything to do with the "AckNotSupported" type?  Is "AckNotSupported" the default setting for the receiver SOAP adapter?  If so, where do I change this setting?
    When I call the webservice with the exact same input using a standalone tool, I get the response message back 100%.  Any help will be appreciated.
    Thanks
    Rudi

    Hey
    you are confusing between a response and an acknowledgement.
    response and acknowledgement and not one and the same thing.
    response is basically used when you send some query to the receiver system and expect a set of value(s) for your query.for e.g sending a query to a Database(JDBC) or SAP system(RFC)
    and acknowledgement is just a notification that the message was receiver by the receiver correctly,it does not returns you a set of value(s).
    now coming to your question,ALEAUDIT IDOC is generated when an IDOC is posted,since in your case you are not posting and IDOC,instead your are sending it ,i m not sure if ALEAUDIT will be generated or not,one thing that will come to your rescue is that every receiver SOAP adapter expects a HTTP response(irrespective of you explicitly asking it or not).
    a HTTP 200 means that messages were posted successfully,and HTTP 500 means application error,get this HTTP response and send it back to the SAP system,most probably you would need to use BPM for this.
    Thanx
    Aamir
    Edited by: Aamir Suhail on Jan 24, 2008 11:26 AM

  • SOAP receiver: error HTTP 302 (Moved Temporarily)

    Dear all,
    I configured scenario where SOAP web service is consumed from SAP ABAP system via PI. The problem is in communication with the web service: the error observed in communication channels monitor for the configured SOAP receiver channel is:
    Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: invalid content type for SOAP: TEXT/HTML; HTTP 302 Moved Temporarily: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 302 Moved Temporarily
    The consumed web service is based on the function module developed in SAP NetWeaver 7.00 system. Endpoint for the service was then created via SOAMANAGER, generated binding's address was used as a target URL in the SOAP receiver channel.
    If the service is consumed not via PI, but tested directly from external SOAP client (I used soapUI) with the same WSDL and endpoint, the response is fine and error-free.
    Please advise possible root cause of the issue.
    My regards,
    Vadim

    Hi,
    I am working on a similar scenario where I my consuming an external web service using https protocol from PI.
    I have configured a soap receiver channel to call the target url of this web service as https://portal.xyz.org.uk/webservice_alt.
    I am getting an error HTTP 302 suggesting that PI is not able to follow the re-direction to the target URL as the service resides not on that URL but on https://portal1.xyz.org.uk/webservice_alt or https://portal2.xyz.org.uk/webservice_alt.
    This is their server fail over handling mechanism which is very common. But PI 7.0 is not able to handle this.
    So if I change the target URL on the SOAP receiver channel to  https://portal1.xyz.org.uk/web service  or  https://portal2.xyz.org.uk/webservice_alt , PI works fine without errors . But this is not the right approach because, every time the web service provider takes one of these systems down for upgrade/patching etc, they inform us and then I manually go and change the target URL to the available server on my production PI system config.
    My problem is I want to resolve this redirection error in PI. I have tried raising a call with SAP itself and they pointed out to use Axis adapter which is still not working.
    So I am here asking for help. any suggestions please from the experts?
    Thanks
    Jhansi.

  • SOAP Receiver Error.

    Hi Experts,
    The scenario is esell system to SOAP receiver. we shared the wsdl for the partners.
    during testing i am facing the below error in the SOAP receiver comm channel.
    Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server did not recognize the value of HTTP Header SOAPAction: http://sap.com/xi/WebService/soap1.1.
    Adapter Framework caught exception: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER_SOAP_EXCEPTION - soap fault: Server did not recognize the value of HTTP Header SOAPAction: http://sap.com/xi/WebService/soap1.1.
    NOte: The WSDL which shared with parter has soap action. how should i fix this error.
    When we ask our partners they are telling that they have loaded the wsdl which we provide.
    Could anyone throw some light on how to fix the issue.
    Thanks,
    --Sai.

    Hi Sai,
    I Agree with Bhaskar please check the below blogs for reference...
    RFC -> XI -> WebService - A Complete Walkthrough (Part 1)
    RFC -> XI -> WebService - A Complete Walkthrough (Part 2)
    Thanks and Regards,
    Naveen

  • Received error -41 response when loading content to iDVD.  What is the solution?

    Error note received:  error -41 occurred when attempting to load i-movie content into iDVD.  What is the issue?  What is the solution?

    Also The error (-41) is a memory error or file did not load error. Why you get this not always easy to figure out it seems. You cold start by running repair disk and repair permissions using disk utility on your Machine.

  • SOAP Receiver error in PI 7.1

    Hi Experts,
    Please help me with follow.
    I have a Interface Proxy -> SOAP and in SXMB_MONITOR is OK. But receiver system the data don't OK.
    In the Communication Channel i see the error message:
    2009-04-29 11:20:24 Error SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Internal Error
    2009-04-29 11:20:24 Information SOAP: sending a delivery error ack ...
    2009-04-29 11:20:24 Information SOAP: sent a delivery error ack
    2009-04-29 11:20:24 Error Adapter Framework caught exception: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Internal Error
    2009-04-29 11:20:24 Error 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: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Internal Error.
    2009-04-29 11:20:24 Information The message status was set to WAIT.
    But the Webservice is ok and the parameters of the communication channel (URL, Action and other) too.
    Thanks in advance.

    check this one:
    Async Scenario converted to Sync by PI

  • SOAP Receiver- Error While Sending Message: 500 Internal Server Error

    Hello,
    Our scenario: IDoc to SOAP
    I have added a third party system in the SLD and have used the same in my ID configuration.
    An idoc will be triggered from R/3, which will received in PI, PI will transform the IDoc into SOAP message for the third party system.
    I have tested the scenario in ID from Interface Determination and its successful.
    But when i try to try to test it from RWB, using Test Message in Adapter Engine, I get an error,
    "Error while sending message:500 Internal server error"
    If we test it using a testing software like SOAP UI, it works fine but from PI we get the error mentioned above.
    Regards,
    Abhishek

    Hello,
    Since the IDOC adapter resides on the ABAP stack, you can use this URL instead (it will be sent to the integration engine as Venkata suggested)
    http://host:port/sap/xi/engine?type=entry
    Also check your firewall settings from PI to the third-party system.
    Hope this helps,
    Mark
    Edited by: Mark Dihiansan on Feb 7, 2012 11:48 AM

  • SOAP Receiver Error - Recoverable Exception

    Can someone please explain why I am getting this:
    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 Application/UNKNOWN/APPLICATION_ERROR - application fault.

    Yeah, since it's an application fault.
    If you have sync2sync scenario, you can map this fault message to an exception in outbound interface.
    If you have bpm calling the web service, you can catch the fault message and execute and exception branch in bpm.
    Regards,
    Henrique.

  • JDBC receiver error No response available

    Hi All,
    I am getting below error in Proxy to JDBC synchronous scenario. This interface is to select the records based on between two dates. when number of records comes above 20000, it is failing with below error in sxmb_moni. i am getting this error in QA system.
    With same number of records, it works fine in Development system.
    please share your thoughts to overcome this issue.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--
    Inbound Message
    -->
    - <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
    <SAP:Category>XIAdapterFramework</SAP:Category>
    <SAP:Code area="MESSAGE">GENERAL</SAP:Code>
    <SAP:P1 />
    <SAP:P2 />
    <SAP:P3 />
    <SAP:P4 />
    <SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: No response available.</SAP:AdditionalText>
    <SAP:Stack />
    <SAP:Retry>M</SAP:Retry>
    </SAP:Error>
    Regards,
    Muni

    Hi Inaki,
    i check the channel logs. getting below error.
    Delivery of the message to the application using connection JDBC_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessageExpiredException: Sync application request expired.. Setting message to status failed
    I tried using syncTimeout in the channel. set the value 300000. no luck.
    PI dev and QA systems are connected to QA DB.
    in the development it takes less than 3 mins to fetch the records. that is why it is successful.
    But in the QA , it is taking more than 3 mins. so getting error-ed out. Not sure why syncTimeout  setting is not having any impact.
    Regards,
    Muni.

  • SOAP (Receiver): error occured: Connection refused:

    Hi experts,
    I have a RFC -> XI -> SOAP scenario and while testing the same it gets cancelled with the following errors:
    SOAP: error occured: com.sap.aii.af.ra.ms.api.RecoverableException: Connection refused: connect: java.net.ConnectException: Connection refused: connect
    MP: exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Connection refused: connect: java.net.ConnectException: Connection refused: connect
    Exception caught by adapter framework: Connection refused: connect
    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: Connection refused: connect: java.net.ConnectException: Connection refused: connect.
    Please help me out.
    Regards,
    Daniela

    Hi,
    1. Either the SOAP Url in the SOAP adapter is wrong,
    2. Or there is a proxy server between XI and the Webserivce and so provide the proxy server details in the SOAP adapter ( with Authentication ) if needed and give it a shot.
    Regards
    Bhavesh

  • Error in SOAP receiver channel: java.io.IOException: invalid http response:

    Hi experts,
    I have a IDOC to SOAP scenario where SOAP receiver channel is sending data to web service. In the receiver channel I am getting error as below. Kindly help me to resolve this issue. Thanks.
    "Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid http response: null"

    Did you check this?
    http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40611dd6-e66e-2910-f383-e80fb44f9cd4
    Regards
    Pothana

  • Error while signing in SOAP receiver channel

    Hi,
    I have a Source PI which is sending a XML message to a target PI through SOAP adapter. Its a secure commnication. I am using message level encryption and signing on the source receiver agreement and message level decryption and validation on target sender agreement. The message is failing in the SOAP receiver cahnnel on source PI with the below error message. Also, I am using a certificate which is signed by Verisign and its valid for two years. I have checked the validity, it has not expired yet.
    It works fine if the certificate is signed by SAP(that is, test certificate which is valid for 8 weeks).
    Error Message
    Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIServer/UNKNOWN/ADAPTER.JAVA_EXCEPTION - com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.security.lib.exception.SecurityException: SecurityException in method: verify( Message, byte[], CPALookupObject ). Message: SecurityException in method: verify( Message, byte[], CPALookupObject ). WSSEThread-Exception: SecurityException in method: run(). Message: [_policy0230] The part /soap:Envelope/soap:Body was required to be signed by the policy with the transformations [], but the signature was not accepted. (Info: number of valid signatures: 1, number of accepted signer certificates: 0.).. To-String: com.sap.security.core.policy.exceptions.VerifyException: [_policy0230] The part /soap:Envelope/soap:Body was required to be signed by the policy with the transformations [], but the signature was not accepted. (Info: number of valid signatures: 1, number of accepted signer certificates: 0.).; To-String: com.sap.aii.security.lib.exception.SecurityException: SecurityException in method: run(). Message: [_policy0230] The part /soap:Envelope/soap:Body was required to be signed by the policy with the transformations [], but the signature was not accepted. (Info: number of valid signatures: 1, number of accepted signer certificates: 0.).. To-String: com.sap.security.core.policy.exceptions.VerifyException: [_policy0230] The part /soap:Envelope/soap:Body was required to be signed by the policy with the transformations [], but the signature was not accepted. (Info: number of valid signatures: 1, number of accepted signer certificates: 0.).. To-String: com.sap.aii.security.lib.exception.SecurityException: SecurityException in method: verify( Message, byte[], CPALookupObject ). WSSEThread-Exception: SecurityException in method: run(). Message: [_policy0230] The part /soap:Envelope/soap:Body was required to be signed by the policy with the transformations [], but the signature was not accepted. (Info: number of valid signatures: 1, number of accepted signer certificates: 0.).. To-String: com.sap.security.core.policy.exceptions.VerifyException: [_policy0230] The part /soap:Envelope/soap:Body was required to be signed by the policy with the transformations [], but the signature was not accepted. (Info: number of valid signatures: 1, number of accepted signer certificates: 0.).; To-String: com.sap.aii.security.lib.exception.SecurityException: SecurityException in method: run(). Message: [_policy0230] The part /soap:Envelope/soap:Body was required to be signed by the policy with the transformations [], but the signature was not accepted. (Info: number of valid signatures: 1, number of accepted signer certificates: 0.).. To-String: com.sap.security.core.policy.exceptions.VerifyException: [_policy0230] The part /soap:Envelope/soap:Body was required to be signed by the policy with the transformations [], but the signature was not accepted. (Info: number of valid signatures: 1, number of accepted signer certificates: 0.). at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:996) at sun.reflect.GeneratedMethodAccessor546_10002.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy2684_10002.process(Unknown Source) at com.sap.aii.af.app.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:275) at

    Hi,
    as per the error message is:
    "... The part /soap:Envelope/soap:Body was required to be signed by the policy with the transformations [], but the signature was not accepted. (Info: number of valid signatures: 1, number of accepted signer certificates: 0.) ..."
    I guess the cert. setup either on your side or the other system's side is not fully correct. Check whether all cert., priv keys and public keys are exchanged propperly and setup as trusted certs.
    Regards,
    Kai
    Edited by: Kai Lerch-Baier on Jul 9, 2009 1:24 PM

  • Error in SOAP receiver channel in Synchronous Proxy to SOAP scenario

    Hi all,
    We are experiencing an issue with a synchronous Proxy to SOAP scenario. Getting below error message in the SOAP receiver communication channel for the response message.
    SOAP: Response message contains an errorXIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
    Returning to application. Exception: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error encountered while executing mapping: com.sap.aii.af.service.mapping.MappingException: com.sap.aii.utilxi.misc.api.ResourceException: Could not determine mapping steps for message 1364b76e-ecbf-11e4-85f4-000023acfde6.
    We are running PI 7.4.
    Any help is appreciated.
    Thanks,
    Pushpa

    Hi,
    Seems the Receiver Webservice is not reachable. Did you try to test it using SOAP UI tool.
    1. Test a fresh message from local SOAP UI tool.
    2. Pick 3rd party WSDL file and Import in SOAP UI tool.
    3. Put some dummy data for mandatory fields
    4. Trigger it msg and ckh if you get successful / response msg.
    5. Check if firewall is open and that URL is not blocked.
    Hope it helps
    Regards,
    Azhar

Maybe you are looking for