Getting error in SOAP receiver in RWB

Hi Experts,
we have some problem in soap receiver.
scenario name is PROXY TO SOAP.
firewall is open already
WEB service team not able to get the message from PI. wHEN WE MONITOR Receiver soap communication channel we are getting the below 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: The message with Action '' cannot be processed at the receiver, due to a ContractFilter mismatch at the EndpointDispatcher. This may be because of either a contract mismatch (mismatched Actions between sender and receiver) or a binding/security mismatch between the sender and the receiver. Check that sender and receiver have the same contract and the same binding (including security requirements, e.g. Message, Transport, None)..
  SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: The message with Action ' cannot be processed at the receiver, due to a ContractFilter mismatch at the EndpointDispatcher. This may be because of either a contract mismatch (mismatched Actions between sender and receiver) or a binding/security mismatch between the sender and the receiver. Check that sender and receiver have the same contract and the same binding (including security requirements, e.g. Message, Transport, None).
when we load the receiver url(webservice url) we are getting the the xml message.
please help us.
thanks
Elton
Edited by: eltonsaranya on Feb 23, 2012 12:47 PM

Hi Elton,
Most probably you need to type the SOAP Action in the receiver Communication Channel. You can find it in the .wsdl file for your scenario in the following tag:
<wsdl:operation name="SaveShipment">
   <wsdl:input wsdl:Action="http://namespace.com/Integration/SomeAction" name="SomeAction"/>
</wsdl:operation>
In this case, you would use the following SOAP Action in your receiver channel: http://namespace.com/Integration/SomeAction.
Hope this helps,
Greg

Similar Messages

  • Error on SOAP Receiver for Axis

    Hi all, 
    Is there anybody to help for solution?
    Thanks.
    Error on SOAP Receiver for axis
    Error Message
    <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: javax.ejb.EJBException: Exception in getMethodReady() for stateless bean sap.com/com.sap.aii.axis.appxml|com.sap.aii.adapter.axis.ejb.jarxml|AFAdapterBean; nested exception is: com.sap.engine.services.ejb3.util.pool.PoolException: javax.ejb.EJBException: Exception raised from invocation of public void com.sap.aii.adapter.axis.modules.AFAdapterBean.ejbCreate() throws javax.ejb.CreateException method on bean instance com.sap.aii.adapter.axis.modules.AFAdapterBean@3ff5ea5d for bean sap.com/com.sap.aii.axis.appxml|com.sap.aii.adapter.axis.ejb.jarxml|AFAdapterBean; nested exception is: javax.ejb.CreateException: java.lang.NoClassDefFoundError: org/apache/axis/types/URI$MalformedURIException</SAP:AdditionalText>
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>

    We deployed com.sap.aii.af.axisproviderlib.sda to use SOAP for axis.
    We sent data from SAP to Axis, error below ocured?
    What must we do to solve problem?
    Thanks.
    Error
    <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <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: org.apache.axis.ConfigurationException: handler is not instantiated org.apache.axis.ConfigurationException: handler is not instantiated at com.sap.aii.adapter.axis.modules.HandlerCore.process(HandlerCore.java:73) at com.sap.aii.adapter.axis.modules.HandlerBean.process(HandlerBean.java:75) at sun.reflect.GeneratedMethodAccessor360_10000.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 $Proxy2634_10000.process(Unknown Source) at com.sap.aii.af.app.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:275) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 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 $Proxy1431_10000.process(Unknown Source) at com.sap.aii.af.app.listener.AFWListenerBean.onMessage(AFWListenerBean.java:332) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 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 $Proxy1479_10000.onMessage(Unknown Source) at com.sap.engine.messaging.impl.spi.ServicesImpl.deliver(ServicesImpl.java:314) at com.sap.aii.adapter.xi.ms.XIEventHandler.onDeliver(XIEventHandler.java:1000) at com.sap.engine.messaging.impl.core.queue.consumer.RequestConsumer.onMessage(RequestConsumer.java:73) at com.sap.engine.messaging.impl.core.queue.Queue.run(Queue.java:921) at com.sap.engine.messaging.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:152) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)</SAP:AdditionalText>
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>

  • While creatinf Depo dec order VA01 i get error  shipping point receivable

    while creatinf Depo dec order VA01 i get error  shipping point receivable   whent i try to enter the point message i get is shipping cond 02 loading group plant not defined

    Dear,
    This is config issue.
    Please follow following Path to do the setting,
    SPRO-- LOGISTIC EXECUTION-- SHIPPING-- BASIC SHIPPING FUNCTION--ASSIGN SHIPPING POINT( DOUBLE CLICK)
    and maintain following data,
    02 (SC)  Loading grp mainatined in Mat. Master(LGrp)   xxxx (Plant )  ur shipping point (PrShp)ur shipping point(MShpPt)
    Note: Please make habbit of updating your thread.If isuue has been resolved pls close ur thread,
                        if not then upadate where are you getting stuck
    Regards
    AJIT K SINGH
    Edited by: AJIT K SINGH on Sep 29, 2010 4:13 PM

  • 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

  • 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 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

  • Error in SOAP Receiver channel

    Hi,
    We are working on IDOC to SOAP Scenario (Connecting to third party).
    We have configured the SOAP Receiver channel with the Target URL and teh corresponding SOAP Action.
    But the SOAP Receiver channel gives the error while processing and sends back the following error message in log :
    "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 process request. ---> Value cannot be null. Parameter name: s."
    Payload seems to look fine in XI and SAP.
    Any help on this ?
    Thanks and regards,
    Vikas

    Hi Vikas,
                Copy the payload from SXMB_MONI  after mapping and check with SOAPGUI or Altova, if it working fine then your payload is good. You can use the WSDL to ganarate and send independent soap request from these tools.
    Besides this IDOC is Asyc, you need to use RequestResponseBean and ResponseOneWayBean to get the response from SOAP.  Check the following  and try to simulate it.
    https://wiki.sdn.sap.com/wiki/display/XI/File-RFC-File%28Without+BPM%29
    Server was unable to process request. ---> Value cannot be null. Parameter name: s."
    The error specifies that the request has null value, check the parameter specified in the error message and make sure that is not null while you are sending the request.
    Regards,
    Prasanna

  • 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

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

  • "Invalid content type" error in SOAP receiver

    Hi ,
    I have ABAP Proxy->XI->Webservice scenario.
    I have configured the SOAP receiver with all neccessary information (Target URL pointing to WSDL , proxy details)
    However i get the following error when i try sending data to the webservice. "Invalid Content type for SOAP: text/html"
    I have seen some forums and blogs on this site on this but still not able to solve the error.
    Please advice...

    Hi Anand,
    Have a look into this thread- similar discussion
    DeliveryException:: invalid content type for SOAP: TEXT/HTML
    Also check this- in the Reciever SOAP Adapter configuration i.e Target URL must be url of the WSDL.
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/40728f7b-0401-0010-d9bc-8c73884a3789
    Hope this helps.......
    Regards,
    Abhy

  • 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.

  • Getting error in SOAP XI Channel

    Hi My scenario is File to Proxy and we are using PI7.31 Java only stack.
    I am getting below errors in Proxy -SOAP-XI communication channel. I have tried this with the several ways as suggested in other SCN, but no luck.
    can someone please tell how to get rid of this.
    Thank you.
    1. Error during parsing the received XMB message.
              tried for this error as per the post : http://scn.sap.com/thread/3184803, but no luck on this.
    2. SOAP: Call failed: com.sap.aii.af.sdk.xi.srt.BubbleException: System Error Received. HTTP Status Code = 200: However System Error received in payload ErrorCode = SLD_NO_OWN_BS ErrorCategory = XIServer Parameter1 = ECCSystemName Parameter2 = ClientNumber Parameter3 = Parameter4 = Additional text = ErrorStack = Error while reading ID of own business system from the SLD for system ECCSystemName and client ClientNumber [http://sap.com/xi/XI/Message/30^Error "SLD_NO_OWN_BS"]
    3.Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.af.sdk.xi.srt.BubbleException: System Error Received. HTTP Status Code = 200: However System Error received in payload ErrorCode = SLD_NO_OWN_BS ErrorCategory = XIServer Parameter1 = ECCSystemName Parameter2 = ClientNumber Parameter3 = Parameter4 = Additional text = ErrorStack = Error while reading ID of own business system from the SLD for system ECCSystemName and client ClientNumber  [http://sap.com/xi/XI/Message/30^Error "SLD_NO_OWN_BS"]
         for the above 2 and 3 errors i have tried several ways of checking business system and SLDCHeck..everythng is fine..but no luck again.

    Hi,
    Go through the below link, You can understand the SLD configuration.
    Basic Configuration for Connecting SAP PI and SAP ABAP Systems - Business Suite Connectivity Configuration # Overview - …
    http://scn.sap.com/people/boris.zarske/blog/2008/03/21/sld-general-recommendation-how-to-set-up-the-system-landscape-directory
    And also refer the below discussion.
    SLD configurations in PI 7.3
    How to configure PI for Central SLD ?
    Regards,
    Tulasiram.

  • Getting error while running Receiving Transaction Processor

    Hi all,i am getting an error in po_interface_errors after running Receiving Transaction Processor concurrent program
    INTERFACE_TYPE       COLUMN_NAME                           ERROR_MESSAGE                     
    RCV-856                  INTERFACE_TRANSACTION_ID      RCV_TP_INVALID_TRX_TYPE     
    TABLE_NAME
    RCV_TRANSACTIONS_INTERFACEI am trying to do an Inter Org transfer and i put the transaction_type as 'RECEIVE' .Can someone kindly suggest what should be the transaction_type for an Inter Org Transfer in rcv_transactions_interface table.Any help is appreciated
    Thanks in advance!!

    HI,
    We are getting the transaction_type error eventhough the transaction_type is a valid.
    Please advise.
    Regards
    MV

  • I am getting error message "SSL received a record with an incorrect Message Authentication Code" when trying to access a secure site

    I am having difficulty in accessing secure sites with Firefox v6.0.2 operating in Windows 7. I get the error message "Secure Connection Failed." SSL received a record with an incorrect Message Authentication Code. Error code: ssl_error_bad_mac_read. This happens will all https sites.

    It works after I disabled IPv6 in Firefox. Thank you for your help :)

Maybe you are looking for