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

Similar Messages

  • SOAP Receiver via https - Error:  Invalid SSL message, peer seems to be tal

    Hi,
    I have a SOAP Adapter that send a message to a HTTPS WebService.
    I'm having the following error:
    Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Invalid SSL message, peer seems to be talking plain!: iaik.security.ssl.SSLException: Invalid SSL message, peer seems to be talking plain!
    If I check the URL via Internet Explorer it showme a confirmation dialog with a security Alert, and ask me if I want to continue, then, I can reach the WS with any problem (from de IE).
    I checked the steps of this PDF:
    http://help.sap.com/saphelp_nw04/helpdata/en/14/ef2940cbf2195de10000000a1550b0/content.htm
    and all seems to be right.
    Any bode can help me with this problem?
    Thanks
    Martin

    Hello,
    finally you run your request from your ERP System about your ICF.
    To establish a SSL Connection to the Web Service target system about an SAP WebAS and ICF, it is necessary to create a certificate on client site about Internet explorer using target URL and importing it on STRUST. Take the junction "SSL-Client (Anonym)" to include your certificate for your system.
    Take a reboot of ICM Monitor.
    Then create a HTTP Connection to rhe external server via SM59 (Typ G).
    Don't forget to configure the following points:
    Under the menu tab Registration&Security:
    - Registration Process: No Registration
    - status of security protocols: activ and ANONYM SSL-Client (Anonym)
    In most cases, you don't need to edit your user data.
    Mostly only then one can usually connect about SAP XI or PI to some servers with SSL method.

  • PO 7.4: NW BPM: HTTP Error response for SOAP request or invalid content-type.HTTP 200 OK

    Hi Experts
    I am trying to call NW BPM scenario(File to BPM) from PI, and using below adapter config.
    I am getting below error.
    Failed to call the endpoint: Error in call over HTTP: HTTP 200 OK
    SOAP: Call failed: java.io.IOException: HTTP Error response for SOAP request or invalid content-type.; HTTP 200 OK
    SOAP: Error occurred: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: HTTP Error response for SOAP request or invalid content-type.; HTTP 200 OK
    MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: HTTP Error response for SOAP request or invalid content-type.; HTTP 200 OK
    Transmitting the message to endpoint <local> using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: HTTP Error response for SOAP request or invalid content-type.; HTTP 200 OK
    Any idea how to fix this issue?
    Thanks,
    Sandeep Maurya.

    Hi Sandeep,
    Test the URL from your browser and check the proxy settings as well.
    Refer the below links
    SOAP: call failed: java.io.IOException: invalid content type for SOAP: TEXT
    SOAP: Call failed: java.io.IOException: Failed to get the input stream from socket: java.net.SocketException: Connection…
    Regards
    Bhargava Krishna

  • SOAP Receiver Success / HTTP Receiver Error

    Hello,
    we have to connect to a http server (HTTP with user authentication). I have tried both a HTTP receiver channel as well as a SOAP receiver channel (option "Do Not Use SOAP Envelope").
    Connection using the SOAP receiver works without problem. If we switch to plain HTTP receiver (same connection details) we get the following error:
    "HTTP client code 400 reason ICM_HTTP_CONNECTION_FAILED".
    What could the reason for this? Probably related to the ABAP Stack?
    Edited by: Florian Guppenberger on Jan 26, 2010 3:12 PM

    Hi,
    >>>What could the reason for this? Probably related to the ABAP Stack?
    check the log on ABAP for RFC dest from SM59
    there you might see some more info
    BTW
    does PI/XI have access to this http sever ? (no firewalls etc?)
    Regards,
    Michal Krawczyk

  • Getting error"invalid content type for SOAP: TEXT/PLAIN; HTTP 503 Not Ready

    Hi,
    I am getting the below error in Comminication channel
    'Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: invalid content type for SOAP: TEXT/PLAIN; HTTP 503 Not Ready: java.io.IOException: invalid content type for SOAP: TEXT/PLAIN; HTTP 503 Not Ready
    SOAP: call failed: java.io.IOException: invalid content type for SOAP: TEXT/PLAIN; HTTP 503 Not Ready

    Hello,
    Have you checked if you are passing the correct content type by validating the generated SOAP request against the format the receiver is expecting? You can try using an HTTP diagnostic tool to analyze the HTTP header e.g fiddler.
    Hope this helps,
    Mark

  • SOAP adapter Using XI 3.0 error: invalid content type for SOAP: TEXT/HTML

    Hi All,
      I have the scenario to send a message to proxy via SOAP adapter . My PI server is 7.3 and my BI application server also 7.3. I have created service interface in the ESR and created the ABAP proxy in the Application server. Im using the receiver SOAP adapter with message protocol as XI 3.0. Am running this scenario in the central adapter engine. (That is i didnt create integrated configuration). I am facing the issue in the receiver SOAP channel as 'invalid content type for SOAP: TEXT/HTML: 401 Unauthorized'. But i can able to login into the URL which is given in the channel using the username and password used in the channel.
    Can you please let me know if any addtional settings need to be done in PI side.
    Regards,
    Ramalakshmi.G

    Hi,
      Thanks for your reply. I have done my scenario with the integration configuration. Still i am facing the same issue " SOAP: TEXT/HTML; HTTP 401 Unauthorized". I have given the correct URL, username and password. Is this enough to connect to the receiver integration server from AE. Any settings need to be do in the receiver ABAP system and PI system. If so please share the corressponding note for the same.  What should be the role is assigned to the userid given in the channel.
    I have used sproxy to create the proxy in the receiver ABAP system. In PI i am using the SOAP adapter with XI 3.0 ,message protocol to call to this proxy. I have not done any settings in any of the servers. Do i need to do any settings.
    Regards,
    Ramalakshmi.G

  • Error while receiving by HTTP (error code: 400, error text: ICM_HTTP_CONNECTION_FAILED

    Hi experts,
    I have a big issue in production server,
    the Queues are stuking in smq2 " command to tRFC/qRFC: execute LUW again"
    if i am reprocess or press F6 it is going manually.
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <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="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>
      <SAP:P1>400</SAP:P1>
      <SAP:P2>ICM_HTTP_CONNECTION_FAILED</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText><html><head><title>Application Server Error</title> <style type="text/css"> body { font-family: arial, sans-serif;} </style> </head> <BODY text="#172972" link="#808080" vlink="#808080" alink="#8e236b" bgcolor=white leftmargin="0" topmargin="0" marginheight="0" marginwidth="0"> <table height="61" width="100%" border="0" cellspacing="0" cellpadding="0"><tr><td background="http://xidist:8000/sap/public/icman/img/bluebar_tile.gif" height="30"><table> <tr> <td width=5></td> <td width=20% nowrap><font face=arial size="-1" color=white>SAP NetWeaver Application Server </font></td><td width=75% align="right" nowrap><font face=arial size="-1" color="white"><a href="http://help.sap.com/">Help </font></td><td width=5% nowrap></font></td> </tr></table> </td><td rowspan=2 width=122 height=61 valign=top><img src= "http://xidist:8000/sap/public/icman/img/theme.jpg" width=122 height=61 border=0 alt="SAP"></td> </tr><tr><td background="http://xidist:8000/sap/public/icman/img/graybar_tile.jpg" height="31">  </td></tr> </table> <br><br> <table width=800> <tr><td width=50 nowrap> </td><td> <H2><b>404 Resource not found</b></H2><br>Partner not reached<br><br><hr> <table border="0"> <tr><td>Error:</td><td>-20</td></tr> <tr><td>Version:</td><td>7000</td></tr> <tr><td>Component:</td><td>ICM</td></tr> <tr><td>Date/Time:</td><td>Wed May 14 15:50:24 2014 </td></tr> <tr><td>Module:</td><td>icxxconn.c</td></tr> <tr><td>Line:</td><td>2341</td></tr> <tr><td>Server:</td><td>xidist_GXI_00</td></tr> <tr><td>Error Tag:</td><td>{004654a1}</td></tr> <tr><td>Detail:</td><td>Connection request from (110/28816/0) to host: xidist, service: 50000 failed (NIESERV_USED) EX-T110, U28816, 001 PIAFUSER, 10.1.57.50, 15:50:24, M0, W1, , 1/0</td></tr> </table> <p></p> </td></tr></table> <table><tr><td width=50 nowrap></td> <td nowrap><FONT SIZE=-1><a href="http://www.sap.com/">&copy; 2001-2009, SAP AG</a></FONT> </td></tr></table> </body></html></SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error while receiving by HTTP (error code: 400, error text: ICM_HTTP_CONNECTION_FAILED)</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
      </SAP:Error>
    Regards,
    Kiran polani

    Dear Sriram Ramani,
    in ths case some scenarios are working good. proxy to soap, idoc to soap and jdbc to proxy, proxy to jdbc all are working with out error.
    but my problem is in Soap to RFC case..
    for all RFC communication channels are working but some time it is throwing RFC_COMMUNICATION_ERROR and messages are stucks in smq2 with retry.
    when i check with retry error with in sxmb_moni log showing ICM_HTTP_CONNECTION_FAILED with error code 400.
    not for all signals for few signals for some time..
    Why it is happening i can't understand.
    in repository it is saying Repsitory object hmi failed and address already in use.
    is there any problem with loading IR objects.
    Please suggest me good suggestion for this type of issue what can do for this to resolve.
    Regards,
    Kiran Polani

  • Error while receiving by HTTP (error code: 110)  ?

    Hi Experts,
    I am working on IDOC to file Scenario.
    I am getting this error in SXMB_MONI. What may be the reason.
    <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>
      <SAP:P1>110</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error while receiving by HTTP (error code: 110, error text: )</SAP:Stack>
      <SAP:Retry>A</SAP:Retry>
      </SAP:Error>
    Best Regards,
    Anil

    Check these threaads:
    Re: XI Error when upgraded to SP14 (Error Code 110) CLIENT_RECEIVE_FAILED
    Regards,
    ravi

  • Getting the error: Error while receiving by HTTP error code: 110

    Hi,
    I have developed an interface which actually gets data from SCM system and in BPM to gets additional data from R/3. There are five synchronous call to this R/3 to get different sets of data. I am using only one communciation channle from BPM to R/3. The interface works perfectly OK in the development system. When the interface is migrated to the test system I found that the four calls work perfectly fine while the last call error out as below and the J2ee server goes down:
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <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="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>
      <SAP:P1>110</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error while receiving by HTTP (error code: 110, error text: )</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
      </SAP:Error>
    Any input/help will be appreciated. I have tried increasing timeout/connection alive time but still not get resolved.
    Thanks in advance,
    Sushma

    Hi Prateek,
    Thanks. But this note I have checked before and this seems not related. I actually found out the system logs in SM21 and saw the "Operating system call recv failed (error no. 10054)". What I did then is I seach notes related to this error and found a numebr of SAP notes. And I have informed the Basis guys to look into the notes and the system logs. They are working on this and they are deleting the old messages which have errored out. They are suspecting the system memory or too many old messages would have caused this issue.
    If you have any knowledge of why this error would have occurred please let me know.
    Thanks,
    Sushma

  • Error  :  Purchase Order  Response for Service items Different

    Hi ,
    We are getting Error  :  Purchase Order  Response for Service items Different  , when creating the PO in SRM 5.0.  what must be the reason ?
    Thanks & Regards,

    Problem solved

  • Error when creating files for transport request SAPK-700BGINPLMWUI

    Hello experts,
    We're upgrading our 46c System to ERP 6.0 EHP4.
    In Phase  EHP_INCLUSION we get the following error Message: Disassembling package queue failed, rc = "2", reason = "Error when creating files for transport request SAPK-700BGINPLMWUI"
    We've already checked the SAINT version; Upgrade Fix, SAPCAR version. We've checked our TMS as well and everything seems  O.K.
    Any help would be really appreciated!!!
    Complete Error message:
    EhP component PLMWUI, 700                                                                               
    Looking for SAINT package for 'PLMWUI' ...                                                                               
    R3upReadNewPackages:                                                                               
    patchType='U', langVect='DEC'                                                                               
    RFC Login to: System="X05", Nr="00", GwHost="sxt ", GwService="sapgw00"                                                 
    RFC Login succeeded                                                                               
    Calling function module "spda_read_new_packages" by RFC                                                                     
      ismovesVersion='0'                                                                               
    R3upReadNewPackages: exit: rc=0                                                                               
    ... No matching package found.                                                                               
    R3upReadNewPackages:                                                                               
    patchType='I', langVect='DEC'                                                                               
    RFC Login to: System="X05", Nr="00", GwHost="sxt ", GwService="sapgw00"                                                 
    RFC Login succeeded                                                                               
    Calling function module "spda_read_new_packages" by RFC                                                                     
      ismovesVersion='0'                                                                               
    R3upReadNewPackages: exit: rc=0                                                                               
    Found: name = 'PLMWUI', release = '700', package = 'SAPK-700BGINPLMWUI', type = 'AOI'                                  
    ... Matching package found: 'PLMWUI','700','SAPK-700BGINPLMWUI'                                                             
    (trc) R3upPatchDisassembleQueue: 1 package queue entries                                                                    
    (trc) R3upPatchDisassembleQueue: force=YES                                                                               
    (trc) R3upPatchDisassembleQueue: 1 packages will be disassembled                                                            
    Starting disassembling package queue                                                                               
    Date & Time: 20100319133139                                                                               
    Starting RFC Login to: System = "X05", GwHost = "sxt ", GwService = "sapgw00"                                           
    RFC Login to: System="X05", Nr="00", GwHost="sxt ", GwService="sapgw00"                                                 
    RFC Login succeeded                                                                               
    Calling function module "SPDA_DISASSEMBLE_QUEUE" by RFC                                                                     
    Input table IT_PATQ:                                                                               
    "SAPK-700BGINPLMWUI","000","AOI","PLMWUI","700","SAP PLM Web UI","00"                                                       
    Call of function module "SPDA_DISASSEMBLE_QUEUE" by RFC succeeded                                                           
    Logging off from SAP system                                                                               
    Date & Time: 20100319133139                                                                               
    Disassembling package queue failed, rc = "2", reason = "Error when creating files for transport request SAPK-700BGINPLMWUI"

    Hello Anthes,
    Please Check the things in following sequence :
    1.Use latest SAPehpi, R3trans and tp versions.
    2. users/group authorization issue and/or ownersip limitations (set 777) .Reboot the server to make sure, that the authorisations are updated and there is no lock on a file in the EHPI dir.Repeat the phase.
    Folders where permissions should be 777 are Upgrade directory, Data Directory, Cofile directory and .../EPS/in.
    3. Source file corruption can be ruled out by execution
    R3trans -l /usr/sap/<SID>/..../abap/data/R-700BGINPLMWUI.SAP (The data file corresponding to the Package which is giving error). Check if this ends fine.
    Note 2050
    4. Confirm that your transport tool is 'healthy' by testing it in STMS. In SPAM in client 000 use the function Disassemble package and enter the package <Package name>.
    5. Try to update the kernel if it not helps.
    Best Regards
    Niraj

  • Error: invalid content type for SOAP: TEXT/HTML; HTTP 400 Bad Request

    Hi Gurus,
    i am hardly fighting with this error in Communication Channel Monitoring:
    Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 400 Bad Request
    SOAP: call failed: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 400 Bad Request
    This is my scenario.
    I do a File to SOAP Scenario. in SXI_MONITOR everything is fine.
    My CommChan is a SOAP Receiver
    HTTP
    SOAP 1.1
    Central Adapter Engine
    Target URL is https --> i check url for correctness
    Configure User Authentication is checked and username and pw are given and are correct.
    Configure Certificate Authentication is checked are working
    Configure Proxy is checked and Host and port are povided.
    SOAP Action is provided
    In Tab Module
    if have this Processing Sequence
    1     localejbs/AF_Modules/MessageTransformBean     Local Enterprise Bean     transform
    2     sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean     Local Enterprise Bean     1
    and this Module configuration (and only this)
    transform     Transform.ContentType     text/xml;charset=utf-8
    (according to /people/sobhithalaxmi.kata/blog/2009/07/21/cost-free-edi-integration-using-message-transformation-bean)
    As far as i understand that my http header should have Content-Type: text/xml;charset=utf-8 now. I don't understand why Communication Channel Monitoring shows an error according to content TEXT/HTML.
    Can anyone help me with that?
    Is it possible that Transform.ContentType does not work for SOAP Receiver Adapter?
    is there any chance to view the HTTP-Header of the outgoing SOAP Request (with PI Transaction / Java Enironment) to convince myself that the HTTP Header is text/xml?
    Thank you in advance and Best Regards
    Udo

    Hi Thanks for your fast replies.
    The Provider of the Endpoint tells me that he needs text/xml as content-type. When I sent a message to the given Endpoint via SOAP UI I can see in the HTTP LOG of SOAP UI that the Endpoint is also sending text/xml back.
    Below you find the Details log out of the CommChan Monitoring.
    2011-04-29 11:37:45 Information The message status was set to TBDL.
    2011-04-29 11:37:45 Information Retrying to deliver message to the application. Retry: 3
    2011-04-29 11:37:45 Information The message was successfully retrieved from the receive queue.
    2011-04-29 11:37:45 Information The message status was set to DLNG.
    2011-04-29 11:37:45 Information Delivering to channel: getxxxxx_In  <---- name of my SOAP Receiver CommChan
    2011-04-29 11:37:45 Information Transform: using Transform.Class:  $identity
    2011-04-29 11:37:45 Information Transform: transforming the payload ...
    2011-04-29 11:37:45 Information Transform: successfully transformed
    2011-04-29 11:37:45 Information SOAP: request message entering the adapter with user J2EE_GUEST
    2011-04-29 11:37:46 Error SOAP: call failed: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 400 Bad Request
    2011-04-29 11:37:46 Information SOAP: sending a delivery error ack ...
    2011-04-29 11:37:46 Information SOAP: sent a delivery error ack
    2011-04-29 11:37:46 Error SOAP: error occured: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 400 Bad Request
    2011-04-29 11:37:46 Error Adapter Framework caught exception: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 400 Bad Request
    2011-04-29 11:37:46 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: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 400 Bad Request.
    2011-04-29 11:37:46 Error The message status was set to NDLV.
    What i am missing is a hint on the Message Transform Bean and a on a successfull sending process.
    What i also tried already:
    i also activated the checkbox "Do not use SOAP Envelop" in CommChan Configuration. The Result you see below (the last log entry is on first line - so read from bottom to top)
    Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 400 Bad Request
    error in response
    call completed
    request entering
    Message processing started
    As you can see there is a "call completed" and "error in response" log entry. This is missing in in the first Log. So i guess the error is still in the sending process.
    Installing additional Software on the PI and use them to find out what the HTTP Request is is not possible as system access is very strict and limited :/

  • 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

  • Soap Receiver adapter - 401 error

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

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

  • SOAP Receiver Channel: RW Error

    Hi experts!
    I have an error in my SOAP Receiver adapter at RW:
    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, 198). ---> Input string was not in a correct format.
    How can i know what field is causing the error?
    "There is an error in XML document (1, 198)." is not much instructive.
    Regards,
    Daniela

    hi,
    try calling the web service from altova or any other tool
    and when you succeed use this xml with SOAP adapter
    this way you will know for sure that it should work
    you can also try to take the xml from SXMB_MONI
    that caused the error and process it via altova etc
    maybe those tools will display more error info
    Regards,
    michal

Maybe you are looking for