Error Consuming Web Service:Unsupported xstream found:("HTTP Code 200:OK")

I am trying to consume a web service from an Outbound Proxy. I am getting the following error message:-
Unsupported xstream found: ("HTTP Code 200 : OK")
This is a System Exception generated while I call the Outbound Proxy.
Kindly let me know what could be the issue.
An early reply will be highly appreciated as I am getting this issue in my Production Server.

This doesn't appear to be a Web Dynpro related question. Please only post Web Dynpro ABAP related questions in this forum.

Similar Messages

"Unsupported xstream found: ("HTTP Code 200 : OK")

Hi,
I am trying to consume an webservice using ABAP (standrad web service provided by SAP). I am getting an error "Unsupported xstream found: ("HTTP Code 200 : OK")".
Has anybody faced this problem before ?
Regards
Goutam

Hey,
This is the description.along with the note.
1) Error: HTP 200 OK
Description: The request has succeeded. The information returned with the response is dependent on the method used in the request GET an entity corresponding to the requested resource is sent in the response; HEAD the entity-header fields corresponding to the requested resource are sent in the response without any message-body; POST an entity describing or containing the result of the action; TRACE an entity containing the request message as received by the end server.
Possible Tips: Have a look into SAP Note: 871959

SRT: Unsupported xstream found: ("HTTP Code 400 : Bad Request")

hi,
I get the error message
SRT: Unsupported xstream found: ("HTTP Code 400 : Bad Request")
what can cause that. I have created a RFC Connection have tested it, it workd well.
But when I call CALL METHOD r_user->MAP_R3USER i get this message.
Regards
sas

Thanks.
Kindly take note that the "Comment" field is not mandatory, so there is no need to bounce all 200 threads to the top again.
You can leave threads unanswered when you still hope or suspect that an answer might be searched be someone, but if it is a "dead duck" (like many cross-posted threads are - which often cause this problem) then please close them.
People who neglect following up on their threads, often neglect thanking those who put in an effort to help with helpfull answers. But many people notice this and stop answering. That does not apply in your case in posts since about July this year, so if you clean up then I am sure that you will further benefit from it.
Please take this in a positive way. Personally I enjoy reading some of your questions and learn from them as well.
Cheers,
Julius

SOAP:1,007 SRT: Unsupported xstream found: ("HTTP Code 404 : Not Found")

Dear expert,
When i run sap call .net web service ,it occurs error:
SOAP:1,008 SRT: Couldn't create Object: ("ICF Error when creating object for HTTP DESTINATION "tempuri.org": DESTINATION NOT FOUND")
Exception of class CX_AI_SYSTEM_FAULT
Could you please tell me how to do?
Looking forward to your reply.
Best Regards,
Merry

Hi Merry,
Did you create a logical port (using transaction code SOAMANAGER) for your client proxy & add the necessary configuration pointing to the .NET web service?
Also, if the logical port is configured, make sure that the URL ( for WSDL with endpoint) that you've specified for the logical port is correct. Error 404 generally means that you have made contact with the service provider but it can't find what you're looking for.
As a quick sanity test, you can run a test request to the service provider using a free tool SoapUI just to make sure that everything on the provider side is ok (i.e. they have provided correct WSDL with binding)
In future, please post this type of question in the SOA forum, see URL below, that's the correct forum for it. Thanks:
Service-Oriented Architecture (SOA) and SAP
Regards, Trevor

Error consuming Web service from an ABAP Program

Hello guys,
I'm trying to consume a Web Service that is exposed in the internet. The conecction to the Web Service its via SSL.
I'm having a problem at the moment I call the web service from my abap program. But I'm able to test the same web service, from the SE80 tx with out trouble.
I have identify that there is a difference in the SOAP envelope, that its received in the Web service, when I call it from the test enviorment and when I call it from the program.
This is how it is received from the TEST tool (a succesfull call of th WS) :
<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
<soap-env:Header><n0:Trace xmlns:n0="http://www.sap.com/webas/630/soap/features/runtime/tracing/"><TraceLevel xmlns="http://www.sap.com/webas/630/soap/features/runtime/tracing/">Error</TraceLevel></n0:Trace></soap-env:Header><soap-env:Body><nr1:putXMLDocument xmlns:nr1="http://bel.bci.cl/WsBEL/services/Carga"><body><?xml version="1.0" encoding="ISO-8859-1"?><Mensaje><RutEmpresa><Numero>76555400</Numero><Digito>4</Digito></RutEmpresa><RutUsuario><Numero>12307972</Numero><Digito>8</Digito></RutUsuario><Convenio>58422</Convenio><Pin>aro79728</Pin><Archivo><Tipo>PPR</Tipo><Plantilla>2142970592</Plantilla><Nombre>cargatest174.txt</Nombre><Cuerpo><![CDATA[G126919727 JORGE CRISTIAN VARGAS ROMERO 0000VVC01600000000000000000000245FAC0000000089900032000021030000010000000000190000 2910200714082008Boletas honorarios|]]></Cuerpo></Archivo><Fecha>20080814</Fecha></Mensaje></body></nr1:putXMLDocument></soap-env:Body></soap-env:Envelope>
And this is how it is received when I consume the web service from the ABAP program.
<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
<soap-env:Header><n0:Trace xmlns:n0="http://www.sap.com/webas/630/soap/features/runtime/tracing/"><TraceLevel xmlns="http://www.sap.com/webas/630/soap/features/runtime/tracing/">Error</TraceLevel></n0:Trace></soap-env:Header><soap-env:Body><nr1:putXMLDocument xmlns:nr1="http://bel.bci.cl/WsBEL/services/Carga"><body><?xml version="1.0" encoding="utf-8" ?><nr1:putXMLDocument xmlns:nr1="http://bel.bci.cl/WsBEL/services/Carga"><body><?xml version="1.0" encoding="ISO-8859-1"?><Mensaje><RutEmpresa><Numero>76555400</Numero><Digito>4</Digito></RutEmpresa><RutUsuario><Numero>12307972</Numero><Digito>8</Digito></RutUsuario><Convenio>58422</Convenio><Pin>aro79728</Pin><Archivo><Tipo>PPR</Tipo><Plantilla>2142970592</Plantilla><Nombre>cargatest174.txt</Nombre><Cuerpo><![CDATA[G126919727 JORGE CRISTIAN VARGAS ROMERO 0000VVC01600000000000000000000245FAC0000000089900032000021030000010000000000190000 2910200714082008Boletas honorarios|]]></Cuerpo></Archivo><Fecha>20080814</Fecha></Mensaje></body></nr1:putXMLDocument></body></nr1:putXMLDocument></soap-env:Body></soap-env:Envelope>
As you can see, it is generating a nr1:putXMLDocument tag, that it should not go there.
Why do you think that this situation is happening? Please guys, this is very important, and need your help. Thanks in advance.
Samuel.

BSP a Developer's Journal Part XIV - Consuming WebServices with ABAP
Calling WebServices from ABAP via HTTPS
Consuming Web Service from ABAP by Durairaj Athavan Raja
Search on SDN wiki, and you will find above mentioned links.

How to consume web service in WDP ABAP ---HTTP error (return code 404, mess

Hi,
Am trying to consume a web serivce in WDP where I got error HTTP error (return code 404, message "conn failed")in sdn i came to know that it could be resloved by giving the IP address of the host but in case it is not the web services am using are the external links.
kindly help me to sort it.
Regards
Raj

hi,
in addition to above thread
refer this too
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b0d4aa08-beed-2a10-fab2-ad975cead04a
bvr

Error Consuming Web Services

Hi All,
I'm using CFINVOKE to consume an enterprise web service. Now, I'm not well versed in web services. But, from reading the CF documentation on them, you're supposed to be able to use <CFINVOKE...> to access them. So, on my test page I have:
<cfinvoke webservice="http://domain.xxx/webservice/EnterpriseWebService?WSDL" method="neededMethod" returnVariable="theOutput"> <cfinvokeargument name="input1" value="#myInput#" />
</cfinvoke>
I'm trying to use a method called "neededMethod". When the <cfinvoke...> tag is reached, I get the following error: coldfusion.jsp.CompilationFailedException: Errors reported by Java compiler: Found 2 semantic errors compiling "/export/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/stubs/WS-147004589 /EnterpriseWebService/webservice/xxx/gov/us/EnterpriseWebService.java: 13. public EnterpriseWebService.webservice.xxx.gov.us.EnterpriseWebServicePort getEnterpriseWebServicePort() throws javax.xml.rpc.ServiceException; ^--------^ *** Semantic Error: Type "EnterpriseWebService.webservice.xxx.gov.us.EnterpriseWebService$webservice" was not found. 15. public EnterpriseWebService.webservice.xxx.gov.us.EnterpriseWebServicePort getEnterpriseWebServicePort(java.net.URLportAddress) throws javax.xml.rpc.ServiceException; ^--------^ *** Semantic Error: Type "EnterpriseWebService.webservice.xxx.gov.us.EnterpriseWebService$webservice" was not found 8 semantic errors compiling "/export/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/stubs/WS-147004589 /EnterpriseWebService....
I looked at the Java files in the referenced directories. They seem to be generated by something called Axis. But, compiling these fail. Is there something in the CF admin that I can tweak?

Place your wsdl on your URL browser, and at the bottom of the output, there should be a an http pointing to your webserver. Make sure that your server domain or IP address is listed on the http pointer. If not, then correct and run.
Try that, and see how it goes.
HTH.
Melvin T.

Error consuming Web service with object hierarchy

I am creating a Web reference to a Web service deployed on JBoss application server. Incidentally, I am able to consume this Web service and run a client against it in .NET. Sun Java Studio Creator has a problem with one of methods in my Web service.
As far as I can tell from my experimentation, the problem lies in the fact that the JavaBean returned from the Web service extends another JavaBean (rather than Object). When I flatten the value object in question, I am able to run the same Web service method in Studio Creator.
I encountered the following post on this forum: http://swforum.sun.com/jive/thread.jspa?forumID=123&threadID=49056. It appears to describe a similar problem. I tried to follow the instructions in that forum by upgrading the JWSDP version (to 1.5) to no avail. I continue to receive the following error when trying to test the Web Service method after creating a Web Service reference in Creator.
The relevant error appears to be
deserialization error: deserialization error: unexpected XML reader state. expected: END but found: START: entityID (where entityID is one of the attributes of the object being returned by the Web Service, which is defined in that object's parent class).
InvocationTargetException com.sun.rave.websvc.ui.ReflectionHelper.callMethodWithParams(Unknown Source) com.sun.rave.websvc.ui.TestWebServiceMethodDlg.invokeMethod(Unknown Source) com.sun.rave.websvc.ui.TestWebServiceMethodDlg.access$500(Unknown Source) com.sun.rave.websvc.ui.TestWebServiceMethodDlg$4.run(Unknown Source) java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:178) java.awt.EventQueue.dispatchEvent(EventQueue.java:454) java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201) java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151) java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145) java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137) java.awt.EventDispatchThread.run(EventDispatchThread.java:100) null sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:324) com.sun.rave.websvc.ui.ReflectionHelper.callMethodWithParams(Unknown Source) com.sun.rave.websvc.ui.TestWebServiceMethodDlg.invokeMethod(Unknown Source) com.sun.rave.websvc.ui.TestWebServiceMethodDlg.access$500(Unknown Source) com.sun.rave.websvc.ui.TestWebServiceMethodDlg$4.run(Unknown Source) java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:178) java.awt.EventQueue.dispatchEvent(EventQueue.java:454) java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201) java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151) java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145) java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137) java.awt.EventDispatchThread.run(EventDispatchThread.java:100) Runtime exception; nested exception is: deserialization error: deserialization error: unexpected XML reader state. expected: END but found: START: entityID com.sun.xml.rpc.client.StreamingSender._handleRuntimeExceptionInSend(StreamingSender.java:248) com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:230) webservice.carmanagerservice.CarManager_Stub.findAllAsArray(CarManager_Stub.java:358) webservice.carmanagerservice.CarManagerServiceClient.carmanagerserviceFindAllAsArray(CarManagerServiceClient.java:35) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:324) com.sun.rave.websvc.ui.ReflectionHelper.callMethodWithParams(Unknown Source) com.sun.rave.websvc.ui.TestWebServiceMethodDlg.invokeMethod(Unknown Source) com.sun.rave.websvc.ui.TestWebServiceMethodDlg.access$500(Unknown Source) com.sun.rave.websvc.ui.TestWebServiceMethodDlg$4.run(Unknown Source) java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:178) java.awt.EventQueue.dispatchEvent(EventQueue.java:454) java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201) java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151) java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145) java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137) java.awt.EventDispatchThread.run(EventDispatchThread.java:100) deserialization error: deserialization error: unexpected XML reader state. expected: END but found: START: entityID com.sun.xml.rpc.encoding.SOAPDeserializationContext.deserializeMultiRefObjects(SOAPDeserializationContext.java:82) com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:163) webservice.carmanagerservice.CarManager_Stub.findAllAsArray(CarManager_Stub.java:358) webservice.carmanagerservice.CarManagerServiceClient.carmanagerserviceFindAllAsArray(CarManagerServiceClient.java:35) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:324) com.sun.rave.websvc.ui.ReflectionHelper.callMethodWithParams(Unknown Source) com.sun.rave.websvc.ui.TestWebServiceMethodDlg.invokeMethod(Unknown Source) com.sun.rave.websvc.ui.TestWebServiceMethodDlg.access$500(Unknown Source) com.sun.rave.websvc.ui.TestWebServiceMethodDlg$4.run(Unknown Source) java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:178) java.awt.EventQueue.dispatchEvent(EventQueue.java:454) java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201) java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151) java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145) java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137) java.awt.EventDispatchThread.run(EventDispatchThread.java:100)

<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions targetNamespace="http://w2k3-vs-msmolyak:7223/jetson-axis/services/CarManagerService" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://w2k3-vs-msmolyak:7223/jetson-axis/services/CarManagerService" xmlns:intf="http://w2k3-vs-msmolyak:7223/jetson-axis/services/CarManagerService" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns1="urn:CarManager" xmlns:tns2="http://common.ejb.application.jetson.datasourceinc.com" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><wsdl:types><schema targetNamespace="http://common.ejb.application.jetson.datasourceinc.com" xmlns="http://www.w3.org/2001/XMLSchema"><import namespace="http://schemas.xmlsoap.org/soap/encoding/"/><complexType abstract="true" name="InfoBase"><sequence><element name="primaryKey" nillable="true" type="xsd:long"/><element name="filterType" nillable="true" type="xsd:short"/><element name="userID" nillable="true" type="xsd:string"/><element name="lastUpdateDate" nillable="true" type="xsd:dateTime"/><element name="entityID" nillable="true" type="xsd:long"/></sequence></complexType><complexType name="BusinessException"><sequence><element name="scriptMessage" nillable="true" type="xsd:string"/><element name="errorCode" type="xsd:int"/></sequence></complexType></schema><schema targetNamespace="urn:CarManager" xmlns="http://www.w3.org/2001/XMLSchema"><import namespace="http://schemas.xmlsoap.org/soap/encoding/"/><complexType name="CarInfo"><complexContent><extension base="tns2:InfoBase"><sequence><element name="year" nillable="true" type="xsd:int"/><element name="make" nillable="true" type="xsd:string"/><element name="model" nillable="true" type="xsd:string"/></sequence></extension></complexContent></complexType><complexType abstract="true" name="List"><sequence><element name="empty" type="xsd:boolean"/></sequence></complexType></schema><schema targetNamespace="http://w2k3-vs-msmolyak:7223/jetson-axis/services/CarManagerService" xmlns="http://www.w3.org/2001/XMLSchema"><import namespace="http://schemas.xmlsoap.org/soap/encoding/"/><complexType name="ArrayOf_tns1_CarInfo"><complexContent><restriction base="soapenc:Array"><attribute ref="soapenc:arrayType" wsdl:arrayType="tns1:CarInfo[]"/></restriction></complexContent></complexType></schema></wsdl:types>
<wsdl:message name="createRequest">
<wsdl:part name="in0" type="tns1:CarInfo"/>
</wsdl:message>
<wsdl:message name="findByPrimaryKeyResponse">
<wsdl:part name="findByPrimaryKeyReturn" type="tns1:CarInfo"/>
</wsdl:message>
<wsdl:message name="removeRequest">
<wsdl:part name="in0" type="tns1:CarInfo"/>
</wsdl:message>
<wsdl:message name="findByPrimaryKeyRequest">
<wsdl:part name="in0" type="xsd:long"/>
</wsdl:message>
<wsdl:message name="updateRequest">
<wsdl:part name="in0" type="tns1:CarInfo"/>
</wsdl:message>
<wsdl:message name="createResponse">
<wsdl:part name="createReturn" type="tns1:CarInfo"/>
</wsdl:message>
<wsdl:message name="removeResponse">
</wsdl:message>
<wsdl:message name="findAllAsArrayResponse">
<wsdl:part name="findAllAsArrayReturn" type="impl:ArrayOf_tns1_CarInfo"/>
</wsdl:message>
<wsdl:message name="findAllAsArrayRequest">
</wsdl:message>
<wsdl:message name="updateResponse">
<wsdl:part name="updateReturn" type="tns1:CarInfo"/>
</wsdl:message>
<wsdl:message name="BusinessException">
<wsdl:part name="fault" type="tns2:BusinessException"/>
</wsdl:message>
<wsdl:portType name="CarManager">
<wsdl:operation name="remove" parameterOrder="in0">
<wsdl:input message="impl:removeRequest" name="removeRequest"/>
<wsdl:output message="impl:removeResponse" name="removeResponse"/>
<wsdl:fault message="impl:BusinessException" name="BusinessException"/>
</wsdl:operation>
<wsdl:operation name="create" parameterOrder="in0">
<wsdl:input message="impl:createRequest" name="createRequest"/>
<wsdl:output message="impl:createResponse" name="createResponse"/>
<wsdl:fault message="impl:BusinessException" name="BusinessException"/>
</wsdl:operation>
<wsdl:operation name="update" parameterOrder="in0">
<wsdl:input message="impl:updateRequest" name="updateRequest"/>
<wsdl:output message="impl:updateResponse" name="updateResponse"/>
<wsdl:fault message="impl:BusinessException" name="BusinessException"/>
</wsdl:operation>
<wsdl:operation name="findByPrimaryKey" parameterOrder="in0">
<wsdl:input message="impl:findByPrimaryKeyRequest" name="findByPrimaryKeyRequest"/>
<wsdl:output message="impl:findByPrimaryKeyResponse" name="findByPrimaryKeyResponse"/>
<wsdl:fault message="impl:BusinessException" name="BusinessException"/>
</wsdl:operation>
<wsdl:operation name="findAllAsArray">
<wsdl:input message="impl:findAllAsArrayRequest" name="findAllAsArrayRequest"/>
<wsdl:output message="impl:findAllAsArrayResponse" name="findAllAsArrayResponse"/>
<wsdl:fault message="impl:BusinessException" name="BusinessException"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="CarManagerServiceSoapBinding" type="impl:CarManager">
<wsdlsoap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="remove">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="removeRequest">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://w2k3-vs-msmolyak:7223/jetson-axis/services/CarManagerService" use="encoded"/>
</wsdl:input>
<wsdl:output name="removeResponse">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://w2k3-vs-msmolyak:7223/jetson-axis/services/CarManagerService" use="encoded"/>
</wsdl:output>
<wsdl:fault name="BusinessException">
<wsdlsoap:fault encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://w2k3-vs-msmolyak:7223/jetson-axis/services/CarManagerService" use="encoded"/>
</wsdl:fault>
</wsdl:operation>
<wsdl:operation name="create">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="createRequest">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://w2k3-vs-msmolyak:7223/jetson-axis/services/CarManagerService" use="encoded"/>
</wsdl:input>
<wsdl:output name="createResponse">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://w2k3-vs-msmolyak:7223/jetson-axis/services/CarManagerService" use="encoded"/>
</wsdl:output>
<wsdl:fault name="BusinessException">
<wsdlsoap:fault encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://w2k3-vs-msmolyak:7223/jetson-axis/services/CarManagerService" use="encoded"/>
</wsdl:fault>
</wsdl:operation>
<wsdl:operation name="update">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="updateRequest">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://w2k3-vs-msmolyak:7223/jetson-axis/services/CarManagerService" use="encoded"/>
</wsdl:input>
<wsdl:output name="updateResponse">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://w2k3-vs-msmolyak:7223/jetson-axis/services/CarManagerService" use="encoded"/>
</wsdl:output>
<wsdl:fault name="BusinessException">
<wsdlsoap:fault encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://w2k3-vs-msmolyak:7223/jetson-axis/services/CarManagerService" use="encoded"/>
</wsdl:fault>
</wsdl:operation>
<wsdl:operation name="findByPrimaryKey">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="findByPrimaryKeyRequest">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://w2k3-vs-msmolyak:7223/jetson-axis/services/CarManagerService" use="encoded"/>
</wsdl:input>
<wsdl:output name="findByPrimaryKeyResponse">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://w2k3-vs-msmolyak:7223/jetson-axis/services/CarManagerService" use="encoded"/>
</wsdl:output>
<wsdl:fault name="BusinessException">
<wsdlsoap:fault encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://w2k3-vs-msmolyak:7223/jetson-axis/services/CarManagerService" use="encoded"/>
</wsdl:fault>
</wsdl:operation>
<wsdl:operation name="findAllAsArray">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="findAllAsArrayRequest">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://w2k3-vs-msmolyak:7223/jetson-axis/services/CarManagerService" use="encoded"/>
</wsdl:input>
<wsdl:output name="findAllAsArrayResponse">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://w2k3-vs-msmolyak:7223/jetson-axis/services/CarManagerService" use="encoded"/>
</wsdl:output>
<wsdl:fault name="BusinessException">
<wsdlsoap:fault encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://w2k3-vs-msmolyak:7223/jetson-axis/services/CarManagerService" use="encoded"/>
</wsdl:fault>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="CarManagerService">
<wsdl:port binding="impl:CarManagerServiceSoapBinding" name="CarManagerService">
<wsdlsoap:address location="http://w2k3-vs-msmolyak:7223/jetson-axis/services/CarManagerService"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>

Error consuming web service in web dynpro

Im looking up https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c0d9336b-b4cf-2910-bdbf-b00d89bd2929 to consume a webservice in web dynpro.
I deployed the ear file containing the web service.
Now when I create an adaptive web service model in web dynpro project i get an error:
Error in loading wsdl file. Check the error log for more details.

It seems to work well with just "Import web service model" - but its deprecated...
What can we do about the adaptive option?

Data Services - Error Consuming Web Service from SAP CE

Hello all,
I developed a very quick sample real-time job in Data Services just to test the web services and connectivity between BoBJ DS and SAP CE. The real-time job doesn't do anything fancy, just converts characters from lower case to upper case. In SAP CE I am attempting to use the web service navigator to test the WSDL (http://localhost:28080/DataServices/servlet/webservices?ver=2.0&wsdlxml). SAP CE correctly connects to the WSDL and gives me a selection list where I can drill down to Real-Time Services -> my real time job. I put in some test data and execute the web service and I get the following error:
Invalid transport binding settingsDocument is not well-formed: Expected End-tag 'MAIN', received:a, on position: 0 (:main:, row:1, col:0)
The strange thing is that the HTTP response message shows that the service actually executed, because the data has been converted to upper case as it was supposed to. Also, if I go into the Data Services Management Console it shows the service was executed with no errors. The strange thing is that I notice something wrong when I look at the response message vs. the source message:
Source:
<?xml version="1.0" encoding="utf-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SOAP-ENV:Body>
    <pns:MAIN xmlns:pns="private">
      <pns:RECORD>
        <pns:NAME>Test Name</pns:NAME>
        <pns:NUMBER>Test1234</pns:NUMBER>
        <pns:ADDRESS>123 Testing Lane</pns:ADDRESS>
        <pns:CITY>Santa Clara</pns:CITY>
        <pns:STATE>CA</pns:STATE>
        <pns:POSTAL>95057</pns:POSTAL>
      </pns:RECORD>
    </pns:MAIN>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Target:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><MAIN xmlns="private" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="C:\Documents%20and%20Settings\TEMP\Desktop\Schema.xsd">
<RECORD><NAME>TEST NAME</NAME>
<NUMBER>TEST1234</NUMBER>
<ADDRESS>123 TESTING LANE</ADDRESS>
<CITY>SANTA CLARA</CITY>
<STATE>CA</STATE>
<POSTAL>95057</POSTAL>
</RECORD>
</aw:MAIN></soapenv:Body></soapenv:Envelope>
If you notice in the target message the closing <MAIN> tag is preceded by "aw". I'm not sure what this means, and I'm not sure where it's coming from, but I think it could have something to do with the error because it doesn't match the opening tag.
I'm not sure if this is something that is set in Data Services? I've checked around quite a bit but I am stumped! Can anyone help?

what is the version of dataServices you are using ? there was a bug that was fixed related to this issue, if you are on 12.1 (DS XI 3.1) then use the latest 12.1 Fix Pack 12.1.1.7
if you are on 12.2 (DS XI 3.2) then use the latest SP and FP 12.2.2.1

Error consuming Web service - content type text/xml;charset=utf-8 of the response message does not match the content type of the binding

Hi all,
We are trying to interact with Documentum server through DFS exposed WCF which communicates through port 9443 and we are provided with documentum issued Public Key certificates. We have successfully imported the certificates in client machine and configured
the bindings as below in our .Net web application config file.
<system.serviceModel>
<bindings>
<wsHttpBinding>
<binding
name="ObjectServicePortBinding1">
<security
mode="Transport">
<transport
clientCredentialType="None"
proxyCredentialType="None"
realm=""
/>
<message
clientCredentialType="Certificate"
algorithmSuite="Default"
/>
</security>
</binding>
<binding
name="QueryServicePortBinding">
<security
mode="Transport">
<transport
clientCredentialType="None"
proxyCredentialType="None"
realm=""
/>
<message
clientCredentialType="Certificate"
algorithmSuite="Default"
/>
</security>
</binding>
</wsHttpBinding>
</bindings>
Also, we set the message encoding as MTOM and the wcf client object initialization code snippet is as below,
ObjectServicePortClient
serviceClient = new
ObjectServicePortClient(new
WSHttpBinding("ObjectServicePortBinding1"),
new
EndpointAddress(UriUtil.ObjectServiceUri));
if (serviceClient.Endpoint.Binding
is
WSHttpBinding)
   WSHttpBinding
wsBinding = serviceClient.Endpoint.Binding as
WSHttpBinding;
wsBinding.MessageEncoding =
"MTOM".Equals(transferMode) ?
WSMessageEncoding.Mtom :
WSMessageEncoding.Text;
serviceClient.Endpoint.Behaviors.Add(new
ServiceContextBehavior(Config.RepositoryName,
Config.DocumentumUserName,
Config.DocumentumPassword));
When we execute the above code, we are getting error message as below,
Exception: The content type text/xml;charset=utf-8 of the response message does not match the content type of the binding (multipart/related; type="application/xop+xml"). If using a custom encoder, be sure that the IsContentTypeSupported
method is implemented properly. The first 407 bytes of the response were: '<?xml version="1.0" ?><S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"><S:Body><S:Fault xmlns:ns4="http://www.w3.org/2003/05/soap-envelope"><faultcode>S:VersionMismatch</faultcode><faultstring>Couldn't
create SOAP message. Expecting Envelope in namespace http://schemas.xmlsoap.org/soap/envelope/, but got http://www.w3.org/2003/05/soap-envelope </faultstring></S:Fault></S:Body></S:Envelope>'
Then, we changed the bindings as below
<system.serviceModel>
<bindings>
<wsHttpBinding>
<binding
name="ObjectServicePortBinding1">
<security
mode="Transport">
<transport
clientCredentialType="Certificate"
proxyCredentialType="None"
realm=""
/>
<message
clientCredentialType="Certificate"
algorithmSuite="Default"
/>
</security>
</binding>
<binding
name="QueryServicePortBinding">
<security
mode="Transport">
<transport
clientCredentialType="
Certificate"
proxyCredentialType="None"
realm=""
/>
<message
clientCredentialType="Certificate"
algorithmSuite="Default"
/>
</security>
</binding>
</wsHttpBinding>
</bindings>
We are getting another error message,
Exception: The client certificate is not provided. Specify a client certificate in ClientCredentials.
Any pointers on resolving this issue would be highly helpful.
Thanks

Hi Dhanasegaran,
As per your case, the corresponding details which may guide you to resolve this issue:
1. First of all, you can try to call the wcf service directly from the browser & check where it will point out the correct location.
2. In config file ,Set IncludeExceptionDetailInFaults to true to enable exception information to flow to clients for debugging purposes .
Set this to true only during development to troubleshoot a service like below :
<serviceBehaviors>
<behavior name="metadataAndDebugEnabled">
    <serviceDebug
      includeExceptionDetailInFaults="true"
/>
    <serviceMetadata
      httpGetEnabled="true"
      httpGetUrl=""
/>
</behavior>
</serviceBehaviors>
3. I suggest you to change that <security mode ="TransportWithMessageCredential"> instead of <security mode ="Transport">
for more information, refer the following link :
https://msdn.microsoft.com/en-us/library/aa354508(v=vs.110).aspx

SAP consume external web service - HTTP Code 200 : OK

Hi
We are integrating UPS Shipping Ground Web service with SAP system and we have the settings in place on our side and did a blank request test today and we are getting a " HTTP Code 200 : OK " error instead of a response.
The SAP SOAManager shows the below detail for the error:
A SOAP Runtime Core Exception occurred in method get_http_headers of class CL_SOAP_HTTP_TPBND_ROOT at position id 3 with internal error id 1007 and error text SRT: Unsupported xstream found: ("HTTP Code 200 : OK") (fault location is 1 ).
One thing we noted but not sure about it is that the response content type is showing text/plain while the request shows content type accept text/xml in SOAManager trace functionality. (screen shot )
I see several discussion on this but could not figure out what needs to be changed in SE80 consumer proxy or the SOAManager port level. Please advice.
Regards,
Prabaharan G

hi Prabaharan! thanx for answer!
i do integration with document scanning/recognitioning system (ABBYY FlexiCapture). It interact as SOAP services over MS IIS server in local network.
what i`ve done:
- drop everething at first.
- create proxy in se80 using wsdl file. created ok.
- create logical port in soamanager using "Create WSDL based configuration". created ok.
- go to sm59. there are some connections but nothing like my connection. i have check all sections, not only type G(HTTP).
AND HERE HAPPEN GREAT THING!
Test "ping" fail but my test code start to work!
All I have change is "url access path". So i think that was my problem. (I was confused by ping fail early and have trying to change all settings)
you bring me luck - thank you very much!

Error in Web Service SOAP Calling HTTP Code 200

Hi Gurus,
I'm new of this forums, I hope you can help me in my realy strange problem.
I' ve create a Web Service ( SAP ) and my job it's to create a Adobe Interactive Forms with LiveCycle,
that connect to WS and recive some Binding values.
When I import the WSDL in my LiveCycle and create the form, all works fine.
When I preview the pdf generated, I have this kind of error in the xml returned:
soap-env:Server sap SRT: Unsupported xstream found: ("HTTP Code 200 : OK")
When I change button type from Submit to Execute, the preview pdf generated don't works...
I press the button more times and don't works too.
Reguards
Nicola Bisinella

Hi to all,
I have resolved my problem installing Adobe Acrobat Pro and creating the pdf with it...
Thanks
Nicola Bisinella

("HTTP Code 200 : OK") SRT: Unsupported xstream found

Hi,
when I am trying send a request to an external webservice
I am getting this message. Do you have an idea what can cause this error.
Regards
ilhan
Server: SAP Web Application Server (ICM)
HTTP/1.1 500 Internal Server Error
set-cookie: MYSAPSSO2=AjQxMDMBABhBAFIAQwBIAEkAQgBVAFMAIAAgACAAIAACAAYyADgAMQADAB
BFAFMAUgAgACAAIAAgACAABAAYMgAwADAAOQAwADUAMgA2ADAAOQAwADcABQAEAAAACAYAAlgACQACRA
D%2fAPswgfgGCSqGSIb3DQEHAqCB6jCB5wIBATELMAkGBSsOAwIaBQAwCwYJKoZIhvcNAQcBMYHHMIHE
AgEBMBkwDjEMMAoGA1UEAxMDRVNSAgcgCAYQFiMnMAkGBSsOAwIaBQCgXTAYBgkqhkiG9w0BCQMxCwYJ
KoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wOTA1MjYwOTA3NDNaMCMGCSqGSIb3DQEJBDEWBBThnsmT
%2f90RLKhrO%2fWjjbrvDvw%21czAJBgcqhkjOOAQDBC8wLQIUTDMZiy9E9buJoePGCdCDg5BwYvsCFQ
DQGyevsV2OfRgF9ol%2fQJKRj9l%214Q%3d%3d; path=/; domain=apslidl
content-type: text/xml; charset=utf-8
content-length: 675
accept: text/xml
sap-srt_id: 20090526/110743/v1.00_final_6.40/DE49D4AA07D6C6F1BC1E000C29A9F676
server: SAP Web Application Server (1.0;700)
<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/"><s oap-env:Header></soap-env:Header><soap-env:Body><soap-env:Fault><faultcode>soap-
env:Server</faultcode><faultstring xml:lang="en">SRT: Unsupported xstream found:
("HTTP Code 200 : OK")</faultstring><detail><ns:SystemFault xmlns:ns="http://w
ww.sap.com/webas/710/soap/runtime/abap/fault/system/"><Host>undefined</Host><Com
ponent>COREMSG</Component><ChainedException><Exception_Name>CX_SOAP_CORE</Except
ion_Name><Exception_Text>SRT: Unsupported xstream found: ("HTTP Code 200 : OK")
</Exception_Text></ChainedException></ns:SystemFault></detail></soap-env:Fault><
/soap-env:Body></soap-env:Envelope>

hi
the error message comes if I use this tool http://curl.haxx.se/
When I use this tool I dont get an error. http://www.eviware.com/
To sum up:
What do you thing what the error causes ?
- the wsdl format is not correct
- you are saying "just compare the two clients"
what can I compare with them
Regards
ertas

Consuming Web Service from ABAP Web Dynpro

I have written program to consume KM Web Service through ABAP as well as ABAP Dynpro in SAP R/3 by calling Consumer Proxy.
When I run the program from SE38, it prompts me for user-id & password. If I pass KM Server user-id and password I am able to execute the web service successfully.
However, while I execute the same code through Web Dyn-pro , it does not ask for user-id and password & terminates with CX_AI_SYSTEM_FAULT : SOAP:1,007 SRT: Unsupported xstream found: ("HTTP Code 401 : Unauthorized")
I have created a Logical Port in R/3 & I am using this Logical Port while creating an Object of Consumer Proxy.
Kindly let me know how to resolve this issue.

The dialog that is produced by HTTP Destination object of the logical port is designed only for use within Classic Dynpro applications. There is no prompt produced when running in Web Dynpro. If possible assign a generic user within the logical port definition and this will be used automatically by all users.

Error Consuming Web Service:Unsupported xstream found:("HTTP Code 200:OK")

Similar Messages

Maybe you are looking for