Error: SRT: Invalid settings in Web Service Registry detected

Hello All,
I am trying to call a webservice from ABAP in SAP ECC 5  but it is throwing an exception when trying to execute a test run.
<CX_AI_SYSTEM_FAULT>
<CODECONTEXT>Local</CODECONTEXT>
<CODE>ERROR_WEBSERVICE_RUNTIME_INIT</CODE>
<ERRORTEXT>Error when instantiating WebService runtime (Error when initializing SOAP client application )</ERRORTEXT>
<LANGUAGE />
When I debugged the program i got this error message
SRT: Invalid settings in Web Service Registry detected
message Class : ESRT_LPREG
Meesage No. :043
Any pointer to this error message..What am I missing here..I guess there seems to be setting missing in one of the config tcode..
~kris

Hello Krishnaraj,
                        The equivalent T-Codes for SOAMANAGER in ECC are
wsconfig
wsadmin
wspublish
Please also make sure from se80 that your web service is activated.
In wsconfig check out whether a service exists for the service definition or not.

Similar Messages

  • How to retrieve error message(s) after failed web service call

    Hi!
    I tried to create an item using the web service ego_item_pub.process_item and it worked ok (version 12.1.1). Sending the same request again, I got an error which should be ok since the item id already exists. The thing is, that I only get an "E" as return status:
    <X_RETURN_STATUS>E</X_RETURN_STATUS>
    <X_MSG_COUNT>1</X_MSG_COUNT>
    As described in the integration repository, there should be a parameter called msg_data which should contain the message if there is exactly 1 message, but I cannot find it.
    So, I tried to get the message using fnd_message.get, but the response of my web service call is:
    AuthorizationFailure : User not authorized to execute service. (I use sysadmin/sysadmin as ws security user).
    I use the following grant details:
    All Users     Direct     GLOBAL     Revoke Action Enabled
    SYSADMIN SYSADMIN     Direct     USER
    What else can I do or how can I retrieve error messages for a failed web service call?
    Thanks a lot,
    Konrad

    Hi Konrad,
    As we've found out, search the Integration Repository for internal name ERROR_HANDLER and use that. Letting the general public know the answer for this one!
    Regards,
    Gareth
    http://garethroberts.blogspot.com

  • "The client version is invalid." error when calling TemplateMgr.asmx web service of AD-RMS SDK 2.1

    - In a WinForm application, trying to get a template from template GUID (AdminServiceRightsTemplateManager)
    System.Web.Services.Protocols.SoapException: The client version  is invalid. ---> Microsoft.RightsManagementServices.Admin.ClientInvalidVersionException: The client version  is invalid.
       at Microsoft.RightsManagementServices.Admin.WebServiceBase.CheckClientVersion(String serverFunctionalVersion)
    Do we need to manually pass the ClientVersion into the service? Or some issues I didn't aware of?
    Much appreciated for any suggestion and comments.
    Thanks,
    Raymond,
    mengruts

    After I read the notes written by Michael Lehmann (Title: How can I setup a soap server for use in JDeveloper 9i), I realized I need to turn off the proxy from JDeveloper. After that everything works.
    Thank you, Michael!
    - Hao

  • Error while testing the endpoints in Service Registry

    Hi,
    I am getting the following error while testing the endpoint in the Service Registry
    Invalid Response Code: (404) Not Found. The request URL was:"http://<server>:8000/sap/bc/srt/wsdl/bndg_DD73518A3AD471F18558001D0910D3CA/wsdl11/binding/ws_policy/document?sap-client=800". Check, whether the URL is correct, and the Web Service that you are requesting is up and running.
    I have created an Enterprise Service at the backend and have published to the Service Registry of the CE server , but while testing the endpoint in service registry i am getting error.
    Can any one please help me to solve this issue.
    Thanks & Regards,
    Hamsa Shree

    Hi hamsa,
    Have you tested the service? If It works, maybe there's something wrong with your destination configuration.
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/705459a3-bf1c-2b10-8a9d-d300ada5f0fc
    You may find a solution in the above article.
    Good luck!
    Wenhao

  • Error while creating MBO with web service data source

    Hi All,
         I am trying to create MBO by selecting web service as a data source type in SMP 2.3. I am providing sharepoint webservice url of type wsdl with HTTP basic authentication. However, I am getting following error can anyone help me in that. Looking for detail explaination as this is new for me...
    (For "define XSLT manually" I am using sample .xsl file)
    Regards,
    Harshada

    Harshada Karane
    Are you using any proxy in your browser? If yes, please set the proxy in workspace and then trHow to bypass proxy settings in SMP workspace for connecting any public Web Service within corporate Network
    Rgrds
    JK

  • Certificate error while connecting to multiple web service

    I am having a web service test client through which I can connects and get reports from multiple web services.
    In Development unix box, we are using "self-signed certificate" using keystore type JKS. In Production server, we are using certificate from CA.
    The web service is running in Development and in Production.
    Now I have developed single test client with a drop down selection for different web services. For example, if we select "Development", the request will go the development web service and if we select "Production", the request will go to Production web service.
    Now while connecting to Develpment service, we are settings the below certificates details Because we are using the self signed certificate.
    System.setProperty("javax.net.ssl.keyStore",keyStoreFileLocation);
    System.setProperty("javax.net.ssl.keyStorePassword",keyStorePassword);
    System.setProperty("javax.net.ssl.keyStoreType", keyStoreType);
    System.setProperty("javax.net.ssl.trustStoreType",trustStoreType);
    System.setProperty("javax.net.ssl.trustStore",trustStoreFileLocation);
    System.setProperty("javax.net.ssl.trustStorePassword",trustStorePassword);
    I am clearing the System properties using the System.clearProperty() while pointing to Production service. because in Production we are using the CA certificate from Thawte so these details are not required at all and our JRE (java 5) is pre configured to support that CA certificate.
    I am using Resin-2.1.12, axis1.2 and java5.
    Now the problem is
    (1) for the first time, when I send the request to Production Service URL, the report gets generated. For the next time when we are running against Development, it's giving below certificate error.
    sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
    (2) Now restart resin and run the test client against Developemnt service URL, here report gets generated and for the next time, run the test client against Production, it's giving the certificate error.
    So for the 2nd request, it always gives the error irrespective of the web service instance selected.
    Please suggest ....thanks in advance.

    Hi  ,
    No, due to the issue is happening only on one computer.
    The error "(401) Unauthorized" usually indicates that the connection has been established but the permission check fails.  InfoPath Form Services uses the application pool identity of the web
    application to connect to resources.
    Does the account  which login the computer have permission to connect to User Profile Service Application?
    For a workaround, you can go to IIS Manager , set the User Profile Application Pool to Anonymous Access and try again.
    Also you can have a look at the blog:
    http://sharepointconnoisseur.blogspot.in/2011/04/how-to-resolve-401-unauthorized-error.html
    Best Regards,
    Eric
    Eric Tao
    TechNet Community Support

  • User authentication error with Proxy Java Calling web Service in XI

    Hello,
    I have deploy a Web Service in SAP XI 3.0. within a SOAP sender adapter.
    I have also created the Proxy Java Class to access the webservice in the Developer Studio and a Plain Java Class (only with a method main) which uses the proxy classes to consume the web service.
    But when I launch the program a get the next error message:
    java.rmi.RemoteException: Service call exception; nested exception is:
         com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (401) Unauthorized.
         at com.everis.serviciosweb.xi.MI_OUT_STATUSBindingStub.MI_OUT_STATUS(MI_OUT_STATUSBindingStub.java:73)
         at com.everis.llamadas.invocacionWSStatus.main(invocacionWSStatus.java:76)
    Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (401) Unauthorized.
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.handleResponseMessage
    Where MI_OUT_STATUSBindingStub is my Stub Class.
    I have tried to set USERNAME_PROPERTY and PASSWORD_PROPERTY at runtime from my Stub class to the values that I use to access SAP XI (Integration Repository & Integration Directory) but it still doesn't´t work.
    Have anyone a solution?
    Thanks.

    Hi,
        finally I have fixed it.
    The root of the problem was on the way that I proceed with the generation of wsdl in Integration Directory.
    The second step in the wizard for generation of wsdl ask for a url to call the web service and gives you an option to complete the url automatic. I have use this option and it have proposed my an url of type http://<host>:<port>/sap/xi/engine?entry=.......
    But the SOAP adapter call is in the form http://<host>:<port>/XISOAPAdapter/MessageServlet?channel=<party>:<business service>:<channel>
    So using this type of url in the generation of wsld solves all the problems.
    Regards,
    Antonio.

  • Finding configuration settings for web service??

    Hi Experts,
    I have found that a particular web service that I am using is running from sr2.esworkplace.sap.com is there any way to find the settings of how to set this up in the Destination Template Manager of my server in order for the app to work. I would appreciate any help that can be offered. Thanks

    Hi,
    You cannot configure the services residing on ES workplace, but can connect your WebDynrpo to the ESR or the Services Registry to access the services. The services listed in ESR will not have endpoint information, and since you cannot access the configuration, you won't be able to call them. So access the services from the services registry, the WSDL files will have the endpoints as well as the security configurations, and your dynpro will generate all relevant classes and set the endpoint for you as well. Since you will have the endpoint info, you can also create your own logical port in NWA for your client application manually afterwards too.
    Check out the simple sample applications and ES Workplace Handbook at:
    (Link Removed)
    Regards,
    Gökhan
    Edited by: Jason Lax on Apr 12, 2011 3:28 PM as content behind link deleted.

  • Serialization error while invoking a Java web service

    Hi,
    I've a requirement where I need to create a Java web service, which returns a collection (a set of records).
    The way I've created a web service is by having a Java Class, which internally calls a Pl/sql package returning Ref cursors and a bean Class, which wraps the method of the Java Class, to return the collection. I could create the web service successfully and could invoke the end point. The end point looks like this: http://localhost:8988/MyJavaWebService-New_JWS-context-root/MyWebService_finalSoapHttpPort
    The method exposed for the web service in my Java class is of type ArrayList, to fetch the collection element.
    After giving the input at the end point, while I say invoke, for the web service, I get the following error:
    <env:Envelope
    xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:ns0="http://mypkg/types/"
    xmlns:ns1="http://www.oracle.com/webservices/internal/literal">
    <env:Body>
    <env:Fault>
    <faultcode>env:Server</faultcode>
    <faultstring>Internal Server Error (serialization error: no serializer is registered for (class mypkg.EmpBean, null))</faultstring>
    </env:Fault>
    </env:Body>
    </env:Envelope>
    I've tried making my exposed method of type Vector as well and re-generated the web service. But still I face the same issue at invocation.
    Can anybody help me out and hint me on how I should proceed? I'm not sure if my approach is correct and so please correct me if I'm wrong.
    Thanks in Advance,
    Gayathri

    Hi,
    do you use 10.1.2 or 10.1.3?
    Take a look at:
    Re: How to create a web service with ArrayList or Collection

  • Error while invoking a external Web service

    Hi all,
    I am getting a error while invoking the webservice.
    I have tested in soapUI its working there but in BPEL it gives me error.
    Soap request:
    <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
    <soap:Header>
    <wsa:Action xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" bpel:priority="" bpel:completionPersistPolicy="" xmlns:bpel="http://schemas.oracle.com/bpel">http://www.lodestarcorp.com/ProcessPayloadString</wsa:Action>
    <wsa:MessageID xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" bpel:priority="" bpel:completionPersistPolicy="" xmlns:bpel="http://schemas.oracle.com/bpel">uuid:058a8965-3bd3-4e29-8c2b-f96f74ccef7d</wsa:MessageID>
    <wsa:To xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" bpel:priority="" bpel:completionPersistPolicy="" xmlns:bpel="http://schemas.oracle.com/bpel">http://mngktr51623/lodestar/platform/webservices/AdapterWS.asmx</wsa:To>
    <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" soap:mustUnderstand="1">
    <wsse:UsernameToken xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
    <wsse:Username>Divya_V</wsse:Username>
    <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">password1</wsse:Password>
    </wsse:UsernameToken>
    </wsse:Security>
    </soap:Header>
    <soap:Body xmlns:ns1="http://www.lodestarcorp.com/">
    <ns1:ProcessPayloadString>
    <ns1:serviceID>WS_MDM_AVAILABILITY</ns1:serviceID>
    <ns1:payload><![CDATA[<MDMREQUEST><METERACTIVE METERID="CON_METER_00"/></MDMREQUEST>]]></ns1:payload>
    </ns1:ProcessPayloadString>
    </soap:Body>
    </soap:Envelope>
    Error Message:
    <remoteFault xmlns="http://schemas.oracle.com/bpel/extension">
    -<part name="code">
    <code>Security
    </code>
    </part>
    -<part name="summary">
    <summary>
    Header http://schemas.xmlsoap.org/ws/2004/08/addressing:Action for ultimate recipient is required but not present in the message.
    </summary>
    </part>
    -<part name="detail">
    <detail>null
    </detail>
    </part>
    </remoteFault>
    I have provided the Action header but still the same error message.
    Kindly assist.
    With Regards,
    Divz

    Hi,
    do you use 10.1.2 or 10.1.3?
    Take a look at:
    Re: How to create a web service with ArrayList or Collection

  • Error when invoking pl/sql web service from bpel

    Hi!
    I have a simple 'Hello World' pl/sql web service. When i invoke it in asynchronous BPEL process, a local WSDL file is automatically generated for the parterlink used. The process even gets successfully deployed without any warning or error. But in the BPEL console when I create an instance, its alwaya being faulted and the audit give the following error at invoke:
    "{http://schemas.oracle.com/bpel/extension}remoteFault" has been thrown. less
    <remoteFault>
    <part name="code" >
    <code>Server.userException</code>
    </part>
    <part name="summary" >
    <summary>when invoking endpointAddress 'null', java.net.UnknownHostException: www.proxy.us.oracle.com</summary>
    </part>
    <part name="detail" >
    <detail>AxisFault faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException faultSubcode: faultString: java.net.UnknownHostException: www.proxy.us.oracle.com faultActor: faultNode: faultDetail: {http://xml.apache.org/axis/}stackTrace:java.net.UnknownHostException: www.proxy.us.oracle.com at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:153) at java.net.Socket.connect(Socket.java:452) 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:324) at org.collaxa.thirdparty.apache.axis.components.net.DefaultSocketFactory.create(DefaultSocketFactory.java:155) at org.collaxa.thirdparty.apache.axis.components.net.DefaultSocketFactory.create(DefaultSocketFactory.java:117) at org.collaxa.thirdparty.apache.axis.transport.http.HTTPSender.getSocket(HTTPSender.java:158) at org.collaxa.thirdparty.apache.axis.transport.http.HTTPSender.writeToSocket(HTTPSender.java:450) at org.collaxa.thirdparty.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:94) at org.collaxa.thirdparty.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32) at org.collaxa.thirdparty.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118) at org.collaxa.thirdparty.apache.axis.SimpleChain.invoke(SimpleChain.java:83) at org.collaxa.thirdparty.apache.axis.client.AxisClient.invoke(AxisClient.java:147) at org.collaxa.thirdparty.apache.axis.client.Call.invokeEngine(Call.java:2732) at org.collaxa.thirdparty.apache.axis.client.Call.invoke(Call.java:2715) at org.collaxa.thirdparty.apache.axis.client.Call.invoke(Call.java:1737) at com.collaxa.cube.ws.wsif.providers.axis.WSIFOperation_ApacheAxis.invokeAXISMessaging(WSIFOperation_ApacheAxis.java:2113) at com.collaxa.cube.ws.wsif.providers.axis.WSIFOperation_ApacheAxis.invokeRequestResponseOperation(WSIFOperation_ApacheAxis.java:1611) at com.collaxa.cube.ws.wsif.providers.axis.WSIFOperation_ApacheAxis.executeRequestResponseOperation(WSIFOperation_ApacheAxis.java:1083) at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:452) at com.collaxa.cube.ws.WSInvocationManager.invoke2(WSInvocationManager.java:327) at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:189) at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:601) at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:317) at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:188) at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3408) at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1836) at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75) at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:166) at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:252) at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5438) at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1217) at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:511) at com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(CubeDeliveryBean.java:335) at ICubeDeliveryLocalBean_StatelessSessionBeanWrapper16.handleInvoke(ICubeDeliveryLocalBean_StatelessSessionBeanWrapper16.java:1796) at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:37) at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:125) at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70) at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86) at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123) at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:755) at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:928) at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186) at java.lang.Thread.run(Thread.java:534) {http://xml.apache.org/axis/}hostname:NewUser-lap </detail>
    </part>
    </remoteFault>
    Can anybody please tell what could be the problem,
    Thanking in advance,
    Deepika.

    www.proxy.us.oracle.com -> www-proxy.us.oracle.com - looks like set in the obsetenv.bat file

  • Getting error while deploying a simple web services

    Hi
    i am new to web services when i am deploying the web service using
    deployment descriptor(WSDD) file using admin client i am getting the follwing error can any body help regarding this.
    Mydeployment descriptor is
    deploy.wsdd
    <deployment xmlns="http://xml.apache.org/axis/wsdd/"
    xmlns:java="http://xml.apache.org/axis/wsdd/providers/java">
    <service name="MyService" provider="java:RPC">
    <parameter name="className" value="samples.userguide.example3.MyService"/>
    <parameter name="allowedMethods" value="*"/>
    </service>
    </deployment>
    I am getting exception as
    C:\Program Files\Apache Software Foundation\Tomcat 5.5\webapps\axis\WEB-INF\clas
    ses>java org.apache.axis.client.AdminClient deploy.wsdd
    Feb 5, 2008 2:34:54 PM org.apache.axis.utils.JavaUtils isAttachmentSupported
    WARNING: Unable to find required classes (javax.activation.DataHandler and javax
    .mail.internet.MimeMultipart). Attachment support is disabled.
    Processing file deploy.wsdd
    Exception: AxisFault
    faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
    faultSubcode:
    faultString: java.net.ConnectException: Connection refused: connect
    faultActor:
    faultNode:
    faultDetail:
    {http://xml.apache.org/axis/}stackTrace:java.net.ConnectException: Conne
    ction refused: connect
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
    at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
    at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
    at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:364)
    at java.net.Socket.connect(Socket.java:507)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
    java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.apache.axis.components.net.DefaultSocketFactory.create(DefaultSoc
    ketFactory.java:153)
    at org.apache.axis.components.net.DefaultSocketFactory.create(DefaultSoc
    ketFactory.java:120)
    at org.apache.axis.transport.http.HTTPSender.getSocket(HTTPSender.java:1
    91)
    at org.apache.axis.transport.http.HTTPSender.writeToSocket(HTTPSender.ja
    va:404)
    at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:138)
    at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrateg
    y.java:32)
    at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
    at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
    at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
    at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
    at org.apache.axis.client.Call.invoke(Call.java:2767)
    at org.apache.axis.client.Call.invoke(Call.java:1792)
    at org.apache.axis.client.AdminClient.process(AdminClient.java:439)
    at org.apache.axis.client.AdminClient.process(AdminClient.java:404)
    at org.apache.axis.client.AdminClient.process(AdminClient.java:410)
    at org.apache.axis.client.AdminClient.process(AdminClient.java:320)
    at org.apache.axis.client.AdminClient.main(AdminClient.java:463)
    {http://xml.apache.org/axis/}hostname:MUM-12016RS

    Hi Jhansi,
    Whether u create HRconnDS in ur Weblogic server
    If not create it ...
    If yes just check it out whether u gave a correct connection string for it......
    Regards,
    Suganth.G

  • 401:Unauthorized error while consuming a MOSS web service

    Hi, We are trying to cosume a Web Service from MOSS using Spring and Axis. The WSDL requires user name and password. We are passing the right credentials however we are getting the 401 error. The exact exception is provided below. Could any one advise how this can be resolved?
    java.io.FileNotFoundException: Response: '401: Unauthorized' for url: 'https://ts2amr.accenture.com/_vti_bin/Search.asmx?wsdl'.
    org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'spWSClient' defined in ServletContext resource [WEB-INF/applicationContext.xml]: Cannot resolve reference to bean 'spWebService' while setting bean property 'service'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'spWebService' defined in ServletContext resource [WEB-INF/applicationContext.xml]: Invocation of init method failed; nested exception is org.springframework.remoting.RemoteLookupFailureException: Failed to initialize service for JAX-RPC port [{urn:Microsoft.Search}QueryServiceSoap]; nested exception is javax.xml.rpc.ServiceException: Error processing WSDL document:
    java.io.FileNotFoundException: Response: '401: Unauthorized' for url: 'https://ts2amr.accenture.com/_vti_bin/Search.asmx?wsdl'

    I can't speak for MOSS for sure, but other Microsoft services such as MapPoint used to require Digest Authentication, which isn't quite as pervasive as Basic Authentication. You should doublecheck with the MOSS administrator about the proper credentials and access. You might even try a utility like SoapUI to see if things work from a test client before trying it on the application server.

  • Error: BLS is exposed as Web Service

    Hi All,
    I have one small BLS which will get two integers as input params and yield their Sum as output param with Integer Data type. This BLS itself is working fine. Now while generating WSDL file on this BLS, I have use the URL like following
    http://<server>/XMII/WSDLGen/<trasnactionpathname>/<transactionname> which is running fine in browser session itself
    But when Iu2019m trying to test the same WSDL in WSNavigator from Netweaver, this is giving error  as follow
    The markup in the document following the root element must be well-formed
    And while checking the log in NW this is saying as follows
    An error occurred while loading WSDL: http://<Host>:<Port>/XMII/WSDLGen/Default/<Package>/<BLS>
    [EXCEPTION]
    com.sap.engine.services.webservices.jaxrpc.exceptions.WebserviceClientException: GenericServiceFactory initialization problem. [Problem with WSDL file parsing. See nested message.]
    at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService_NewInstance(GenericServiceFactory.java:667)
    at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService_NewInstance(GenericServiceFactory.java:130)
    at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:119)
    at com.sap.esi.esp.wsnavigator.ManualTestView.createServiceByWSDL(ManualTestView.java:414)
    at com.sap.esi.esp.wsnavigator.ManualTestView.onEventWSDLSelected(ManualTestView.java:1531)
    at com.sap.esi.esp.wsnavigator.wdp.InternalManualTestView.wdInvokeEventHandler(InternalManualTestView.java:526)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:131)
    at com.sap.tc.webdynpro.progmodel.components.Component.fireEvent(Component.java:488)
    at com.sap.esi.esp.wsquery.ui.wsquerycomp.wdp.InternalWSQueryComp.wdFireEventWSDLSelected(InternalWSQueryComp.java:571)
    at com.sap.esi.esp.wsquery.ui.wsquerycomp.WSQueryComp.searchByWSDL(WSQueryComp.java:826)
    at com.sap.esi.esp.wsquery.ui.wsquerycomp.WSQueryComp.getSelectedService(WSQueryComp.java:459)
    at com.sap.esi.esp.wsquery.ui.wsquerycomp.wdp.InternalWSQueryComp.wdInvokeMethod(InternalWSQueryComp.java:455)
    at com.sap.tc.webdynpro.progmodel.generation.ExternalControllerPI$ExternalInterfaceInvocationHandler.invoke(ExternalControllerPI.java:339)
    at $Proxy1834.getSelectedService(Unknown Source)
    at com.sap.esi.esp.wsnavigator.ManualTestView.onActionStepChanged(ManualTestView.java:1314)
    at com.sap.esi.esp.wsnavigator.ManualTestView.onActionNext(ManualTestView.java:1277)
    at com.sap.esi.esp.wsnavigator.wdp.InternalManualTestView.wdInvokeEventHandler(InternalManualTestView.java:486)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:131)
    at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:72)
    at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.doHandleActionEvent(ProcessingEventPhase.java:156)
    at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.execute(ProcessingEventPhase.java:91)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:162)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:110)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:97)
    at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:512)
    at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:52)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1549)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1363)
    at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToApplicationDoProcessing(AbstractExecutionContextDispatcher.java:154)
    at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForAppProcessing.doService(DispatchHandlerForAppProcessing.java:35)
    at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:127)
    at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:95)
    at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToApplicationDoProcessing(ExecutionContextDispatcher.java:114)
    at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:80)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:618)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:649)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingStandalone(ApplicationSession.java:570)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:309)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:743)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:258)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:259)
    at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToRequestManager(AbstractExecutionContextDispatcher.java:202)
    at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.doService(DispatchHandlerForRequestManager.java:38)
    at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:127)
    at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:95)
    at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToDispatcherContext(ExecutionContextDispatcher.java:146)
    at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:92)
    at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:104)
    at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
    at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:61)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140)
    at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:37)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:486)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:298)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:396)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:385)
    at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:76)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:243)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
    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:43)
    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:428)
    at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:247)
    at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
    at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
    Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.ProxyGeneratorException: Problem with WSDL file parsing. See nested message.
    at com.sap.engine.services.webservices.espbase.client.ProxyGeneratorNew.loadWSDLapi(ProxyGeneratorNew.java:638)
    at com.sap.engine.services.webservices.espbase.client.ProxyGeneratorNew.generateAll(ProxyGeneratorNew.java:400)
    at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.loadProxy(DGenericServiceImpl.java:231)
    at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.<init>(DGenericServiceImpl.java:69)
    at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService_NewInstance(GenericServiceFactory.java:617)
    ... 87 more
    Caused by: com.sap.engine.services.webservices.espbase.wsdl.exceptions.WSDLException: The markup in the document following the root element must be well-formed.
    at com.sap.engine.services.webservices.espbase.wsdl.WSDLLoader.loadDOMDocument(WSDLLoader.java:145)
    at com.sap.engine.services.webservices.espbase.wsdl.WSDLLoader.load(WSDLLoader.java:90)
    at com.sap.engine.services.webservices.espbase.wsdl.WSDLLoader.load(WSDLLoader.java:79)
    at com.sap.engine.services.webservices.espbase.client.ProxyGeneratorNew.loadWSDLapi(ProxyGeneratorNew.java:632)
    ... 91 more
    Caused by: org.xml.sax.SAXParseException: The markup in the document following the root element must be well-formed.
    at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:264)
    at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
    at com.sap.engine.services.webservices.espbase.wsdl.WSDLLoader.loadDOMDocument(WSDLLoader.java:131)
    ... 94 more
    So is there anything Iu2019m missing or is there anything to be configured at NW server side? Please help
    Our MII version : 12.1.5
    Regards
    Chandan
    Edited by: Chandan Jash on Jun 8, 2011 6:47 PM

    Hi Jeremy,
    Thanks for your help. I am able to test it from WSnavigator but at the time of execution within XacuteRequest: two field are coming always.
    XacuteRequest: 1) LoginName 2) LoginPassword:
    Eithere I need to put the value there or I need to put the value within a popup when I click on next button.
    But if I consume the Web Service from other place like as SAP ECC and trying to execute it then again I need to put the value for XacuteRequest: 1) LoginName 2) LoginPassword: as hardcode.
    Is there any solution that I can avoid these two fields.
    Thanks
    Chandan

  • Getting an error while building a sample web service

    Hi,
    I am beginner in web services and started working on a sample application in a web service tutorial.
    Build is failing in build.xml file while building sample web service using ant tool.
    antBuildfile: build.xml
    clean:
    setup:
    [mkdir] Created dir: /tmp/output/WEB-INF/classes
    [mkdir] Created dir: /tmp/client_classes
    compile.server:
    [javac] Compiling 1 source file to /tmp/output/WEB-INF/classes
    webservice.build:
    webss.build:
    BUILD FAILED
    Z:/JAVA-COBOL/sample1/tutorial/sample1/build.xml:43: The following error occurred while executing this line:
    Z:/JAVA-COBOL/sample1/tutorial/sample1/build-webss.xml:10: Problem: failed to create task or type source2wsdd*_
    Cause: The name is undefined.
    Action: Check the spelling.
    Action: Check that any custom tasks/types have been declared.
    Action: Check that any <presetdef>/<macrodef> declarations have taken place.
    Can anyone look into this and let me know if you have any idea on this?
    Thanks,
    SRoop.
    Edited by: SRoop on Jun 20, 2008 9:11 AM
    Edited by: SRoop on Jun 20, 2008 9:14 AM
    Edited by: SRoop on Jun 21, 2008 5:51 AM

    Hi,
    I am beginner in web services and started working on a sample application in a web service tutorial.
    Build is failing in build.xml file while building sample web service using ant tool.
    antBuildfile: build.xml
    clean:
    setup:
    [mkdir] Created dir: /tmp/output/WEB-INF/classes
    [mkdir] Created dir: /tmp/client_classes
    compile.server:
    [javac] Compiling 1 source file to /tmp/output/WEB-INF/classes
    webservice.build:
    webss.build:
    BUILD FAILED
    Z:/JAVA-COBOL/sample1/tutorial/sample1/build.xml:43: The following error occurred while executing this line:
    Z:/JAVA-COBOL/sample1/tutorial/sample1/build-webss.xml:10: Problem: failed to create task or type source2wsdd*_
    Cause: The name is undefined.
    Action: Check the spelling.
    Action: Check that any custom tasks/types have been declared.
    Action: Check that any <presetdef>/<macrodef> declarations have taken place.
    Can anyone look into this and let me know if you have any idea on this?
    Thanks,
    SRoop.
    Edited by: SRoop on Jun 20, 2008 9:11 AM
    Edited by: SRoop on Jun 20, 2008 9:14 AM
    Edited by: SRoop on Jun 21, 2008 5:51 AM

Maybe you are looking for