Error calling SAP webservice

Hi,
I have created a ZBAPI that is published as webservice via SE37 --> using the wizard, and I have created a flex web that invoke this webservice. When I runs the web in my local the call to webservice works perfect, but when I deploy the web in my Composite Environment and I execute the web I get the following error:
[RPC Fault faultString="Security error accessing url" faultCode="Channel.Security.Error" faultDetail="Unable to load WSDL. If currently online, please verify the URI and/or format of the WSDL (http://xxxxxxxxxxxx:8000/sap/bc/srt/wsdl/bndg_4A02EE1AE83732C2E10000000AA51C62/wsdl11/allinone/standard/document?sap-client=330)"]
I have been searching the solution and only I have found to deploy in the server (Composite Environmentt) the crossdomain.xml in the root, but it doesn't work.
the crossdomain.xml content is:
<?xml version="1.0"?>
<!DOCTYPE cross-domain-policy SYSTEM
"http://www.adobe.com/xml/dtds/cross-domain-policy.dtd">
<cross-domain-policy>
     <site-control permitted-cross-domain-policies="all"/>
     <allow-access-from domain="*" secure="false"/>
     <allow-http-request-headers-from domain="" headers="" secure="false"/>
</cross-domain-policy>
and the route where is deployed is:
D:\usr\sap\XXXX\J00\j2ee\cluster\apps\sap.com\com.sap.engine.docs.examples\servlet_jsp\_default\root
any idea?
thanks in advance
Jose Manuel

Dear Vinay,
Does your other FM are also using arrays.?
Deserialization problem comes when xml parser is not able to convert XML schema or values to language specific elements.
And this problem normally comes if you are using complex data types.
Can you check once again and reply.
Regards,
Piyush

Similar Messages

How to call SAP Webservice in standalone java program

Hi,
In our Java application, we want to use the SAP Webservices. I dont know much about authentication mechanism used by SAP. Can any one please help me with any sample code how to Call SAP webservice in Standalone Jave Program. I searched alot on the web regarding this, but helpless. Please help me.
Thanks,
Mohan

Hi Mohan,
You need an account for the ES Workplace. I'm afraid this is not free, e.g. check [SAP NetWeaver, Composition Subscription|https://www.sdn.sap.com/irj/sdn/subscriptions/composition].
But I thought you wanted to play with a WSDL [you already had at hand|Sample code to access BAPI Web services from JAVA required;?

Call SAP WebService in Excel

Hello,
I want to call a WebService from a SAP-System in Excel. I created this WebService with the WebService Creation Wizard by using a RFC function. The WebService expects two parameters of string and it delivers a table.
I'm using the MS SOAP Type Library v3.0 to call the WebService.
Here's my code:
01 Dim SOAPClient As SoapClient30
02 Set SOAPClient = New SoapClient30
03
04 SOAPClient.mssoapinit "http://" & User & ":" & pswd & "@bcrsap27.de.emea.csc.com:8000/sap/bc/srt/wsdl/bndg_DE22AF411A745FF19F270014C25BCDE3/wsdl11/allinone/ws_policy/document?sap-client=800"
05
06 With SOAPClient
07         .ConnectorProperty("UseSSL") = True
08 End With
09
10 Dim ret() As ZETT_DEFECT_T
11
12 ret = SOAPClient.ZETT_WS_READ_DEFECT("2009-01-01", "2009-04-07")
At line 4 'User' and 'pswd' is needed to authenticate the user.
But on line 12 I allways get an error:
    Run-time error '5419'
    Client: unspecifiedclient erro. HRESULT=0x800A152B
I hope someone can help me.
Thank you,
Frank

Hi,
I have progressed upto a stage where it actully connects to R/3 and goes into class
"CL_HTTP_EXT_SOAPHANDLER_RFC"
but i always get a error
<i><b>"SoapMapper:Restoring data into SoapMapper <obj> failed"</b></i>
It looks like that it is to do with complex data type.
But the function which i am using is just reutrning a result of type string.
I will post more once i solve the issue.
Regards
Raja

Error calling a webservice from one server process of the cluster

Hi ,
I have a servlet which on startup makes a call to a webservice. I deploy this webapp on the cluster.
The cluster has two instances each instance having one server process.
So when the server restarts one server process on one instance calls the web service the other process on other instance fails with a 503 response code.
When I tried to reproduce the same problem using two server processes on the same instance both processes are able to call the webservice properly.
I am slightly confused as to how different the second scenario is from first one as both are individual server process and may or may not run on same instance.
Can anyone tell me the real cause.
Rgds
Shashank

Hi Rajat,
This is how the default trace looks
FATAL: Application Servlet failed to notify devices.
Caught java.rmi.RemoteException: Service call exception; nested exception is:
     com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (503) Service Unavailable. The requested URL was:"http://<<server>>:50000/ManagementService/ManagementService?style=document"
     at com.om.mws.standaloneproxy.ManagementServiceBindingStub.notifyDevice(ManagementServiceBindingStub.java:1289)
     at com.om.mws.standaloneproxy.ManagementServiceBindingStub.notifyDevice(ManagementServiceBindingStub.java:1298)
     at com.om.ApplicationServlet$NotifyDevices.run(ApplicationServlet.java:86)
Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (503) Service Unavailable. The requested URL was:"http://<<server>>:50000/ManagementService/ManagementService?style=document"
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.handleResponseMessage(MimeHttpBinding.java:980)
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1430)
     at com.om.mws.standaloneproxy.ManagementServiceBindingStub.notifyDevice(ManagementServiceBindingStub.java:1282)
     ... 2 more
java.lang.NoSuchMethodError
at java.lang.Thread.destroy(Thread.java:779)
     at com.omApplicationServlet$NotifyDevices.run(ApplicationServlet.java:92)
Rgds
Shashank

Calling SAP Webservice from JAVA ME bad response time

Hello together,
I'm calling a SAP RFC as a Webservice from JAVA ME (Netbeans 6.8). The stub classes I've generated with the Sun Wireless Toolkit. The RFC function stores entries in a SAP database table. The call of the websevice with transmitting the data and the database update in SAP works fine, but I got the response message from SAP with a delay of 40 seconds.
Does anyone know why there is so a long delay in the response and how to fix it?

hi,
is this reproducible or was it just the first call to that service?
it usually occurs that once you call a webservice for the first time, some of the programs (be it your application programs or the even the SOAP runtime itself) required have not been compiled until that and so they are compiled during the webservice call.
This leads to slow response times even time-outs. The effect vanishes once all sources are compiled (i.e. depending on the complexity of your calls after one to a few calls to that service).
So, if the slow response times persist, you should turn on debugging in SICF and see where time is spent...
my 2 cents,
anton

Problem calling SAP webservice ECC_SRVCREQCRTRC1

Hi,
I want to call an SAP webservice to create a service notification from an Adobe Flex application.
For this I use a standard SAP enterprise web service "ECC_SRVCREQCRTRC1".
The web servce call is working and the notification is created.
Now I also want to fill the description in the webservice. This is not working in the same way as filling the notification type parameter.
Notification parameter tag is just a tag:
<TypeCode>?</TypeCode>
The description tag has an attribute:
<Description languageCode="?">?</Description>
In my code I fille the tag TypeCode like this:
serviceRequest.TypeCode = "AB";
Now my question is: "How can I fill the description tag including the language attribute"?
I hope someone can help me with this.
Thanks in advance and kind regards,
Bart Elshout

Hi Pradeep,
Type code is a input/importing field of the header structure of this webservice. Type Code stands for the notification type.
The description is also a subfield of the same header structure (but this field has an attribute "language").
I hope you can help me,
Thanks in advance and kind regards,
Bart

Error calling COM+ webservice

Hey guys,
I am having problems to call COM+ webservices using Mediator.
My composite needs to call some legacy Delphi DLL that are published in a Windows 2003 COM+ SOAP services.
When I try to call the services using the HTTP Analyser tool, everything works fine. However, when I try to call it in my composite application using a Mediator component, I got the following exception:
javax.xml.ws.soap.SOAPFaultException: **** System.Runtime.Serialization.SerializationException - Parse Error, no assembly associated with Xml key wsa Action.
Have anybody faced problems like this to call COM+ SOAP services?
Here is my COM+ SOAP WSDL:
<?xml version="1.0" encoding="UTF-8" ?>
<wsdl:definitions
name="StringCon"
targetNamespace="http://oracle.com/sca/soapservice/InternaliazacaoApp/StringCon/StringCon"
xmlns:tns="http://oracle.com/sca/soapservice/InternaliazacaoApp/StringCon/StringCon"
xmlns:inp1="http://xmlns.oracle.com/singleString"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
<wsdl:documentation>
<abstractWSDL>http://anvisa-soa-dev:8001/soa-infra/services/default/StringCon!1.0/StringCon.wsdl</abstractWSDL>
</wsdl:documentation>
<wsdl:types>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:import namespace="http://xmlns.oracle.com/singleString" schemaLocation="http://anvisa-soa-dev:8001/soa-infra/services/default/StringCon/StringCon?XSD=xsd/singleString.xsd"/>
</xsd:schema>
</wsdl:types>
<wsdl:message name="requestMessage">
<wsdl:part name="input" element="inp1:singleString"/>
</wsdl:message>
<wsdl:message name="replyMessage">
<wsdl:part name="output" element="inp1:singleString"/>
</wsdl:message>
<wsdl:portType name="execute_ptt">
<wsdl:operation name="execute">
<wsdl:input message="tns:requestMessage"/>
<wsdl:output message="tns:replyMessage"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="execute_pttBinding" type="tns:execute_ptt">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="execute">
<soap:operation style="document" soapAction="execute"/>
<wsdl:input>
<soap:body use="literal" namespace="http://oracle.com/sca/soapservice/InternaliazacaoApp/StringCon/StringCon"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal" namespace="http://oracle.com/sca/soapservice/InternaliazacaoApp/StringCon/StringCon"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="StringCon">
<wsdl:port name="execute_pt" binding="tns:execute_pttBinding">
<soap:address location="http://anvisa-soa-dev:8001/soa-infra/services/default/StringCon/StringCon"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
Edited by: 904488 on Dec 26, 2011 5:56 AM

soa suite ws binding sends out wsa headers - that is what fails to be parsed on the .NET side ("Parse Error, no assembly associated with Xml key wsa Action.")
there is a flag on the outbound ws binding properties (omit.wsa.headers) that let's you turn this off.

#2170 error calling a webservice from Xcelsius having crossdomain.xml

Hello together,
we are facing a #2170 error indicating we don't have a proper policy file in place when executing a published Xcelsius flash in SAP BI application portal.
We created a WebService that is running an SAP BI System 7.01. The WebService is function module based and was generated following the wizzard. Afterwards we created a Xcelsius app that consumes data from this WebService (via data connection). The resulting flash from Xcelsius was pulished to SAP BI System (portal).
Since there are many entries in the SDN and the internet in general we finally also created an crossdomain.xml file on the BI system which can be accessed and is visible by using "https://<server>/crossdomain.xml".
Now the confusion begins: We exported the flash from Xcelsius to local desktop and executed the corresponding HTML-file. It's working and I can receive/see WebService data (after adjusting flash-security-settings). If we upload both exported files (html and swf) to the BI system (as MIME objects) and execute the html again we are also receiving WebServervice data. So far so good. But if we execute the link from the SAP BI Portal (Xcelsius menu > SAP > Start) we still get the error #2170 indicating we don't have a proper domain policy file in place. But for my understanding we do have. So currently I would assume the error message is somehow misleading.
During all the activities I found out that this error is also raised if the user has insufficient authorization. My user has SAP_ALL authorization for testing purpose.
In general I would say we are not that wrong with our Xcelsius/WebService if we are not coming from BI portal. So my questions are:
1.) Are there any authorization on portal side that might not fit and lead to this error? If insufficient authorizations produces such an error ...
2.) Did we miss any other stuff during our try/fail-operations?
Many thanks in advance for your hints.
Steffen

Hi Rajat,
This is how the default trace looks
FATAL: Application Servlet failed to notify devices.
Caught java.rmi.RemoteException: Service call exception; nested exception is:
     com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (503) Service Unavailable. The requested URL was:"http://<<server>>:50000/ManagementService/ManagementService?style=document"
     at com.om.mws.standaloneproxy.ManagementServiceBindingStub.notifyDevice(ManagementServiceBindingStub.java:1289)
     at com.om.mws.standaloneproxy.ManagementServiceBindingStub.notifyDevice(ManagementServiceBindingStub.java:1298)
     at com.om.ApplicationServlet$NotifyDevices.run(ApplicationServlet.java:86)
Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (503) Service Unavailable. The requested URL was:"http://<<server>>:50000/ManagementService/ManagementService?style=document"
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.handleResponseMessage(MimeHttpBinding.java:980)
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1430)
     at com.om.mws.standaloneproxy.ManagementServiceBindingStub.notifyDevice(ManagementServiceBindingStub.java:1282)
     ... 2 more
java.lang.NoSuchMethodError
at java.lang.Thread.destroy(Thread.java:779)
     at com.omApplicationServlet$NotifyDevices.run(ApplicationServlet.java:92)
Rgds
Shashank

Soa 11g - error calling SAP adapter

Hello
I'm installing a SAP adapter on SOA suite 11g following this tutorial http://download.oracle.com/docs/cd/E15523_01/doc.1111/e17057/bpel_pm.htm#CHDIDHHI
Using Application Explorer i can connect to SAP server , test services and export wsdls, but when I use this wsdls (Inbound JCA Service) in a simple composite application a got this error :
Error during deployment: Deployment Failed: [JCABinding] [OlaMundoSAP.Service1/1.0]Unable to complete load due
Cause: Unable to find suitable outbound binding.
My composite is very simple, only one Bpel calling a third party adapter, error occurs in deploy time.
Any suggest guys ?

Helder,
in case you still phase this problem, please have a look at the following note and check the prerequisite patches to apply SOA composites:
Oracle Fusion Middleware Application Adapter Best Practices Guide for Oracle WebLogic Server 11g (Doc ID 1080041.1)
Patch 9563280 should solve your problem.
Best Regards
Thorsten

Error calling SPML webservice in OIM11g

Hi
I am getting the below error when I try to create user using SPML webservice.
User xelsysadm does not have access to create the request using Create User With Callback Policy request template
I was able to create user earlier using the same code. Not sure why I am getting this error suddenly.
Any pointers?

Hi
I am getting the below error when I try to create user using SPML webservice.
User xelsysadm does not have access to create the request using Create User With Callback Policy request template
I was able to create user earlier using the same code. Not sure why I am getting this error suddenly.
Any pointers?

Deserialization Failed error when calling a SAP Webservice

Hello,
I'm trying to call an SAP Webservice from a .NET Mobile application, this particular BAPI expects an array of objects and when I make the call I get a deserialization problems. I have tried make the array size to 0 but no luck, I have couple of other function modules which are working fine but have a problem with this BAPI BAPI_ALM_ORDEROPER_GET_LIST.
any help is greatly appriciated.
Thanks
Vinay

Dear Vinay,
Does your other FM are also using arrays.?
Deserialization problem comes when xml parser is not able to convert XML schema or values to language specific elements.
And this problem normally comes if you are using complex data types.
Can you check once again and reply.
Regards,
Piyush

Errors calling webservice of SAP from javascript

Hi Friends,
When i call a webservice from javascript using the XMLHttpRequest,i get a
crediantals error,I alos pass the login details
var oReq = new XMLHttpRequest();
oReq.open("GET", url, async, loginname, password);
oReq.send();
any help please.
regards
kaushik

Providing HTTP Basic Auth username and password as part of the URL is a common practice, however it is discouraged for security reasons. If possible, try to avoid it.
Also, it may not work because your friendly browser developer might already took care of this. In the address bar, MS disallowed (by default) this usage three years ago, Firefox does warn (and prompt) the user. I haven't tried für AJAX, though - it might work, but it might break in the future.
Assuming you are calling the service from the host you came from, is the page delivering the JavaScript password-free, but the service needs a password?
:Frederic:

Error while calling PI webservice from EJB

Hi Experts,
We are getting exception while calling PI webservice from EJB which is deployed in CE 7.2. Earlier we used to call the same webservice but from different PI system at that it worked fine. Now we have changed the consumer proxies required in CE and tried to call from CE and it is throwing error. We have checked usernames and passwords that we are using to call the service and that is working fine. PI team tested from their side and li is also fine. We have also restarted the CE system but invain. Can somebody help on this. The below is the trace that we got.
Location: com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding
Text: Connection IO Exception. Check nested exception for details. (Connection reset).
[EXCEPTION]
com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Connection IO Exception. Check nested exception for details. (Connection reset).
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.outputSOAPMessage(SOAPTransportBinding.java:419)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1364)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:990)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:944)
at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:168)
at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEISyncMethod(WSInvocationHandler.java:121)
at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEIMethod(WSInvocationHandler.java:84)
at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invoke(WSInvocationHandler.java:65)
at $Proxy780.mioaRDMDataDistribution(Unknown Source)
at com.MDMEventListener.callToPIWS(MDMEventListener.java:100)
at com.MDMEventListener.ListenerMethod(MDMEventListener.java:173)
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:597)
at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:47)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_WS.invoke(Interceptors_WS.java:31)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
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:39)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:23)
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:25)
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:17)
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:138)
at com.sap.engine.services.ejb3.webservice.impl.DefaultImplementationContainer.invokeMethod(DefaultImplementationContainer.java:203)
at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.process0(RuntimeProcessingEnvironment.java:730)
at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.preProcess(RuntimeProcessingEnvironment.java:682)
at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.process(RuntimeProcessingEnvironment.java:324)
at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPostWOLogging(ServletDispatcherImpl.java:199)
at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:65)
at com.sap.engine.services.webservices.servlet.SoapServlet.doPost(SoapServlet.java:61)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:404)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:204)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:440)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:429)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:82)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:268)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:54)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:447)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:264)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
Caused by: java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:168)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read(BufferedInputStream.java:237)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.readLine(HTTPSocket.java:950)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getInputStream(HTTPSocket.java:414)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getResponseCode(HTTPSocket.java:319)
at com.sap.engine.services.webservices.espbase.client.bindings.ClientHTTPTransport.getResponseCode(ClientHTTPTransport.java:209)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.outputSOAPMessage(SOAPTransportBinding.java:385)
... 78 more
Regards,
Pradeep

Hi Pradeep,
this looks like if the server is not reachable. Have you checked if both server are able to communicate? Maybe firewall rules block the request.
Regards,
Tobias

Error getting while calling a webService from XI

Hi
We are getting the follwoing error while calling a webservice from XI. We Could call the same webservice from XML spy. Have checked the SOAP adapter it was running fine and the communication channel parameters too.
<?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.MessagingException: SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault</SAP:AdditionalText><SAP:ApplicationFaultMessage namespace=""/><SAP:Stack/><SAP:Retry>M</SAP:Retry></SAP:Error>
Please try to help.
Thanks
Ramesh

Hi
Thanks a lot for your kind support.
Hi Moorthy
We have created one Asyn MI and wrapped the external definition into that, Haven't done any mapping for responce. Please find the trace below.
Hi Bhavesh
It was great helpful link but the payload days is not visible for this message it was containing details about sending. For some other message i could see payload.
I Could see one differnce in the XML Spy and "XI payload before entering SOAP Adapter"
The following line doesnt appear in the XI payload.
<m:StatusUpdate xmlns:m="http://localhost/StatusUpdate" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
</m:StatusUpdate>
Is this line would be embeded in the SOAP Adapter??? Please find the trace below. Please help me if you have any additional info.
The message was successfully received by the messaging system. Profile: XI URL: Using connection AFW. Trying to put the message into the receive queue.
Message successfully put into the queue.
The message was successfully retrieved from the receive queue.
The message status set to DLNG.
Delivering to channel: CC_SOAP_Rcvr_D_Pick_ZALEAUD
SOAP: request message entering the adapter
SOAP: completed the processing
SOAP: response message received 4cb3fab0-7fc5-11db-8c5a-000f203c93e0
SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault
SOAP: sending a delivery error ack ...
SOAP: sent a delivery error ack
Exception caught by adapter framework: SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault
Delivery of the message to the application using connection AFW failed, due to: SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault.
The asynchronous message was successfully scheduled to be delivered at Wed Nov 29 16:23:51 GMT 2006.
The message status set to WAIT.
Retrying to deliver message to the application. Retry: 1
Kind Regards
Ramesh
Message was edited by:
Ramesh Reddy Pothireddy

Calling HTTPS Webservice error

Hello friends,
I am trying to call https Webservice SSL on ADS. However, it still did not work. I am getting error like "Error attempting to read from file".
If you have experience on configuring Webservice SSL, please advise. Your advice is much appreciated.
Best Regards,
Fatih

Hello,
I am no basis guy, but maybe one of these could help:
ADS Installation and configuration:
http://help.sap.com/saphelp_nwmobile71/helpdata/en/37/504b8cbc2848a494facfdc09a359b1/frameset.htm
Troubleshooting for ADS configuration:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/30ec0508-9438-2c10-f393-a41fb255698d?quicklink=index&overridelayout=true
ADS tests
http://help.sap.com/saphelp_nwmobile71/helpdata/en/43/f31e3082221595e10000000a1553f7/content.htm
Regards Otto

Error calling SAP webservice

Similar Messages

Maybe you are looking for