SOAP to SOAP / HTTP 200 error

Hi
I have the following scenario   SOAP to SOAP and am getting a HTTP 200 error.
com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: No SOAP Envelope but 1 definitions; HTTP 200
I have configured a sender SOAP channel with default values (Nothing is checked).   My receiver channel is configured in a similar manner. The SOAP action is specified. I have tested the receiver webservice in WSNavigator and successfully can get it to call.   The webservice was created from a function module that has used the create webservice functionality, and then endpoints created in SOAMANAGER.
There are no mappings in this scenario.
When I right click on the sender agreement and get the WSDL, I take that URL and place it into the WSNAVIGATOR tool. I supply the same values that I did when I called the service directly.   When I execute, the error above appears in SXMB_MONI.
Ideas?

Here is the error. There is no principle propagation and the user is setup in the BI system.
<?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>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: java.io.IOException: No SOAP Envelope but 1 definitions; HTTP 200 OK</SAP:AdditionalText>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Edited by: Mike Marowski on Feb 18, 2010 12:12 AM

Similar Messages

Java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 200 OK

hi all,
please help me to resolve the error. i am working on a proxy to soap scenario and in SXMB_moni i am getting the following error.
i had check my url,its working fine.
<?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>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: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 200 OK</SAP:AdditionalText>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>*
thanks
kasturika

Check this thread
Receiver SOAP Adapter Error: invalid content type for SOAP: TEXT/HTML
might give you some directions to look at.
Sameer

Invalid content type for SOAP: TEXT/PLAIN; HTTP 200 OK

Hi,
I am working on RFC - XI - WebService scenario. tested web service with soapUI and works fine. but while configured in XI getting below error.
<?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>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: invalid content type for SOAP: TEXT/PLAIN; HTTP 200 OK</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thanks,
Mahesh

Hi Stefan,
Imported webservice in external definition and the web service has 3 messages in it.
1. header
2. requestdoc
3. response.
while creating message interface, i can select only one input message (here i have to pass values for both Header & request doc). if i create 2 separate message interfaces one for header & one for requestdoc, how can i add both of them as target messages in meesage mapping? it gives me error if i add multiple target messages because the mode is synchronous.
How do we map when we have multiple messages (header & request) in a web service?
I created a new message type with header & requestdoc in it, and used in mapping. Do you think the above problem is occuring because of this?
My webservice structure looks like below.
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
 <soapenv:Header>
 <soap:RequestHeader>
 <soap:variable1></soap:variable1>
 <soap:variable2></soap:variable2>
 <soap:variable3></soap:variable3>
 </soap:RequestHeader>
 </soapenv:Header>
 <soapenv:Body>
 <soap:SOAPRequest>
 <RequestDoc></RequestDoc>
 </soap:SOAPRequest>
 </soapenv:Body>
</soapenv:Envelope>
Thanks,
Mahesh

Special characters in sender soap adapter provoke HTTP 500 error

Hi,
SAP R3 is sending a SOAP message to PI through SOAP adapter.
When the payload does NOT contain german characters like ü, it works fine.
However, when the payload DOES contain special characters, the SOAP adapter replies with an HTTP 500 code error.
If I use SoapUI to send the soap message, and setting UTF-8 as the encoding in the program options, it will go through fine. If I change to ISO-8859-1 it will fail.
I'm thinking in two options:
- Make sure that SAP R3 sends the message in UTF-8 format (I think this is happening currently), as if SoapUI works, then probably R3 is not using UTF-8.
- Force the adapter to use UTF-8. Is this possible? In the sender SOAP adapter I've added AF_Modules/MessageTransformBean (type local EB), and then Transform.ContentType for parameter name and --> text/plain;charset=utf-8 for parameter value. The sender adapter will fail then for every message, with or without special characters.
Anyway, in this link (http://help.sap.com/saphelp_nwpi71/helpdata/EN/a4/f13341771b4c0de10000000a1550b0/frameset.htm) it seems to say that the sender soap adapter cannot be extended with modules, so maybe that's the reason why it fails when trying to add a module.
Thanks

If I use SoapUI to send the soap message, and setting UTF-8 as the encoding in the program options, it will go through fine. If I change to ISO-8859-1 it will fail.
I'm thinking in two options:
Check the use of option 1 ..... the URL which SAP is using to send the data can containe the encoding information.
Check this SAP note: https://service.sap.com/sap/support/notes/856597
From the above note:
Q: What character encoding is supported by the SOAP sender adapter?
+you can supply the encoding information with the xmlenc variable in the request URL as in+
Regards,
Abhishek.

SOAP-IDOC scenario- HTTP 500 error

Hi All,
We are working on SOAP- IDOC scenario.
We are getting a request from Sender which should come via Reverse Proxy server to PI.
We generated WebService on PI and the URL(X) is shared with Proxy team, wherein they mapped that URL (X)with other URL(Y). This URL (Y)is shared to sender and he is trying to send some requests now.But below is the error message.
[09/02/13 15:26:12] ID=app01 (trace) Delivered HTTP Direct outbound message, containing details...
        Destination URL=https://XXXXXXXXXXXXXXXXXXXXXXXXXXXXX
        User=ZZZZZZZ
        Status Code=500
        [req]Content-Length=7148
        [req]X-HTTPS-ClientAuthCertificate=/AAAAAAAAAAAAAAAA
        [req]X-HTTPS-ClientAuthCertificateForm=PKCS12
        [req]Authorization=Basic RjRGSU5GWEQxMDA6c3luZ2VudGEx
        [req]X-HTTPS-CACertificatePath=/BBBBBBBBBBBB
        [req]X-HTTPS-PrivateKey=/CCCCCCCCCCCCCCCCC
        [req]JMSReplyTo=sga.ws.test.response
        [req]messageuniqueid=6d65d89f-ffff-ffc0-00ee-3aa7032c3299
        [req]adpnextmlemarkersequence=3
        [req]X-HTTPS-PrivateKeyPassword=ZZZZZ[maid
        [req]Content-Type=text/plain
        [resp]content-type=text/xml; charset=utf-8
        [resp]set-cookie=saplb_*=(SERVERNAME)226695750; version=1; path=/
        [resp]set-cookie=saplb_*=(SERVERNAME)226695750; version=1; path=/
Any Clue

Hi,
Check this
HTTP 500
o Internal error in J2EE
o Check SAP Note 807000 - Http requests are not fully read
after timeout
Regards,
Sreenivas

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

SOAP Response change from http 200 to http 204

Hello
I must change for a application, that call a webservice on the pi, change the
SOAP Response from HTTP 200 OK to HTTP 204. I think that must chnage on the SOAP Adapter and wei can't change in the messages or mapping. Also wit a Fault Messages is this not runnig.
What is with BPM, have any body do somthing with that.
Regards Tom

Hello Stefan
This thrid Application need this response. We cann't change this. We spaek with this product manager, but he want change this. He want this when the interface is async, that application now no conntent come back.
Regards Tom

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

Error SOAP: call failed: java.io.IOException: Read timed out; HTTP 200 OK

Hi PI gurus,
Need some suggestions on one issue below -
Scenario - proxy (SAP) to SOAP (Web based system)
In the RWB Communication Channel Monitirong we are receiving the below error
" Error SOAP: call failed: java.io.IOException: Read timed out; HTTP 200 OK"
the request from XI system is going to target system and printing the lables (as per the functionality) with no issues but the comminication channel is giving the above error and this is causing the repeated sending the same request to target sytem and the data is printing repeateadly. This issues is occuring in Quality environment.
Strangley the same Interface with the same connectivity details is working fine in Development environment. But not working in Quality environment. Checked the firewalls settings on both in XI and Target system side and confirmed that everything is fine.
Below are the Logs both from Quality and developement are as follows
Quality ( Failure Case)
17.03.2011 07:19:59 Success SOAP: request message entering the adapter with user J2EE_GUEST
17.03.2011 07:25:03 Error SOAP: call failed: java.io.IOException: Read timed out; HTTP 200 OK
Development (Success ful)
17.03.2011 07:27:55 Success SOAP: request message entering the adapter with user J2EE_GUEST
17.03.2011 07:27:58 Success SOAP: completed the processing
When we checked with basis team on user id J2EE_GUEST, they confirmed that they are same in Development and Quality.
I repeat,, that the same target url and everthing is same in XI Configuration
Thanks in Advance. Points would be rewared for the best solution.
Thanks,
Jitender

HI Jitender,
If your scenariois working in DEV and if it is not working in QAS.Could you please check if both the systems are at same patch levels..
Please refer below notes :1551161,817894,952402.
Cheers!!!
Naveen.

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

SOAP Adapter XI 3.0 - HTTP 200 response fails

We have a scenario where a request message is sent successfully to a URL by the SOAP Adapter.
However, the response message has an HTTP response of 200 (meaning ok) which is not handled correctly by the
SOAP Adapter.
The error text shown in SXMB_MONI is:
com.sap.aii.af.ra.ms.api.DeliveryException: Failed to call the endpoint HTTP 200 OK
Is there something I am missing in the configuration to allow HTTP responses in the SOAP Adapter ? It is very odd that the SOAP Request works fine, but the SOAP Response does not.
Any ideas anyone ?
Kind regards
Colin.

Hi Bill
1. synchronous out / in
2. yes
3. working fine
following the way out to the elocateserver system is working fine.
The soap is working and the responce from the elocteserver is fine . But when the message is pick put the Timeout show up.
below is the Responce from elocateserver to xi
Hope this will help you
thanks olaf
Help
!http://sapnt09:50200/sap/public/icman/img/theme.jpg|alt=SAP|width=122 height=61 border=0 |src=http://sapnt09:50200/sap/public/icman/img/theme.jpg!
500 Connection timed out
Connection timed out (-5)
Error:
-5
Version:
6040
Component:
ICM
Date/Time:
Sat Oct 16 06:13:25 2004
Module:
icxxthr.c
Line:
2556
Server:
sapnt09_M64_02
Detail:
Connection to partner timed out
© 2001-2003, SAP AG

No SOAP Envelope but 1 {'}Values; HTTP 200 OK

Hi Experts,
I am configuring a scneario IDOC to SOAP , Asynchronous call to an https url that is available through internet.
When I try to post message to this url. I am getting following error:
SOAP: call failed: java.io.IOException: No SOAP Envelope but 1 {'}Values; HTTP 200 OK
in SOAP Adapter Log. Due to this error the message is set to NDLV.
I am using PI7.1
My Receiver Channel configurations are as contain
the third party url https://target with username password authentication. I have also imported client certificates.
Webservice host says its a problem with PI system and SAP says that its issue with Webservice.
Please let me know how can I resolve this issue. Am I missing something in my configuration. This is kind of a burning issue currently any help will be appreciated.
Regards,
Raj

Hi Raj,
This looks strange. If the error text is telling the truth, your SSL connection was working and you could even reach some service that returned HTTP 200 OK. But this service didn't return a SOAP response. I don't know what 1 {*} Values means. It sounds broken to me. You can open a ticket.
But the reason why you didn't get a valid SOAP response (either a good one or a fault) is probably that your target URL is incorrect. Verify the URL and run the scenario with the relevant components (refer to the SOAP adapter FAQ note) on DEBUG. The default trace file should give you more information about this apparently corrupted response.
Best regards, Yza

Exception on JaxRpc invoke: HTTP transport error: javax.xml.soap.SOAPExcept

Hi all,
I am getting below error while invoking Siebel web service from BPEL service,
<fault>
-<remoteFault xmlns="http://schemas.oracle.com/bpel/extension">
-<part name="summary">
<summary>
exception on JaxRpc invoke: HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: oracle.j2ee.ws.saaj.ContentTypeException: Not a valid SOAP Content-Type: text/html; charset=UTF-8
</summary>
</part>
</remoteFault>
</fault
Please help me to resolve this issue.
Thanks,
Santosh M E

Resolved, I was invoking an external Web service which is an Asynchronous 2 way.
Didn't capture the reply back from the Async service.

SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPT

Hi there,
I am trying to publish a file from SAP as web service using XI and SOAP Adapter.
I am using ABAP proxy to get the data into XI.
Designing and Configuration in XI has no problems because when i use File adapter the data is trasmitted to FTP server.
But when I used SOAP Reciever adapter I am getting following error in RWB
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 500 Error during parsing of SOAP header.
Scenario: SAP ABAP Proxy -> XI -> WebService. Asynchronous.
SOAP Receiver adaptor.
Target URL http://<host>:<port number >/sap/xi/engine?type=entry&version=3.0&Sender.Service=SAPDC2653&Interface=urn:bzttest:00:hsa:test%5EOB_MI_BZT_TEST&QualityOfService=ExactlyOnce
Do not use SOAP Envelop is checked.
SOAP Action http://sap.com/xi/WebService/soap1.1
What i am missing here? How should I solve this problem?
Any help is appreciated,
Thx,
Yogi

Say there's a bapi/rfc that you want to call on an R/3 backend (e.g. 4.6c). On it's own, the R/3 system cannot expose the rfc/bapi as a web service, but XI can. So in this case, the scenario would be:
WS client -> XI -> R/3
When XI "exposes" a web service, it is exposing a service for a receiving system (in the above example, the R/3 system). XI itself does not provide or contain the service implementation. When XI exposes a web service, it is always done via the sender soap adapter (i.e. if soap adapter is used). Receiver soap adapter is used to call or consume an actual web service from an external application.
Regards,
Jin

Invalid content type for SOAP: TEXT/HTML; HTTP 500 Internal Server Error

Hi,
I have this error on a SOAP Receiver Channel: invalid content type for SOAP: TEXT/HTML; HTTP 500 Internal Server Error
I've found several threads on SDN Forums about similar errors, but I did not find a solution for my problem yet.
I checked this blog: /people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009 Pt.6 applies to my situation, but the proposed solution doesn't solve the problem.
TRACE Messaging System
u2026
2011-06-06 10:59:41.822 Success Delivering to channel: CC_SOAP_RCV_XXX
2011-06-06 10:59:41.823 Success MP: entering1
2011-06-06 10:59:41.825 Success MP: processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
2011-06-06 10:59:41.828 Success SOAP: request message entering the adapter with user J2EE_GUEST
2011-06-06 10:59:42.012 Error SOAP: call failed: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 500 Internal Server Error
2011-06-06 10:59:42.014 Success SOAP: sending a delivery error ack ...
2011-06-06 10:59:42.014 Success SOAP: sent a delivery error ack
u2026
Message Details
Address   http://aaa.bbb.be:54000/MessagingSystem/receive/AFW/XI
Credential   PasswordCredential(PIISUSER):password=********
Transport Headers   accept-encoding=gzip sap-xi-messageid=4DEA11FE90003094E10000000AE908B4 content-length=7520 http=POST host= aaa.bbb.be:54000 user-agent=SAP NetWeaver Application Server (1.0;711) content-type=multipart/related;boundary=SAP_4DEA47CEAD3A5138E10000000AE908B4_END;type="text/xml";start="" soapaction="http://sap.com/xi/XI/Message/30"
Configuration Details SOAP Communication Channel
SOAP Receiver Channel
No modules configured
Do not use SOAP Envelope -> NOT checked
If I type the target URL in browser it opens (no login required) and I see the available web services.
Anyone any idea what's the reason for this error?
Thanks in advance
Kind Regards
Edmond Paulussen

Hi Edmond,
We faced similar problem & found alternative.
Try out, if it works for u as well.
1) Use HTTP Adapter instead of SOAP.
Transport Protocol : HTTP 1.0
Message Protocol : XI Payload in HTTP Body
Adapter Engine : Integration Server
Addressing type : URL Address.
Target Host:
Service Number :
Path Prefix:
Authentication type : we hv used Ananymus login, as our login details in payload header.
Content Type : application/soap+xml;charset=UTF-8( this is IMP).
Header Fields.
Name         value
Host           target host
XI Payload Manipulation
XML Code : UTF-8
Hope, this helps...
-santosh.

SOAP to SOAP / HTTP 200 error

Similar Messages

Maybe you are looking for