No such JCO destination is defined in the SLD

Hi All,
Following JCo are not available in Portal 7.0 for MSS configuration.
Already MSS Buss Pkg has been deployed in Portal.
u2022     SAP_R3_SelfServiceGenericsFIN
u2022     SAP_R3_SelfServiceGenerics_MetaDataFIN
u2022     SAP_cProjects
u2022     SAP_cProjects_MetaData
Getting mention error for MSS application:
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCO destination name 'SAP_R3_SelfServiceGenerics_MetaDataFIN' in the SLD. No such JCO destination is defined in the SLD.
Please suggest for resolution.
Regards,
SK

You have to get this fixed through BASIS / Web Dynpro Content Administrator.
Check under Content administrator -> Webdynpro whether all the JCO connections are working fine.
Setting Up JCo Connections for MSS - http://help.sap.com/erp2005_ehp_04/helpdata/EN/ef/15d2060e344c2fbf22e526104c24bb/frameset.htm
Once the ESS / MSS Business Packages are deployed, as a part of the post deployment steps JCO set up is to be completed
Below JCO are to be set up for MSS -
●      General connections:
○       SAP_R3_SelfServiceGenerics
○       SAP_R3_SelfServiceGenerics_MetaData
●       Connections for the Team area:
○       SAP_R3_HumanResources
○       SAP_R3_HumanResources_MetaData
●      Connections for the Budget area:
○       SAP_R3_Financials
○       SAP_R3_Financials_MetaData
○       SAP_R3_SelfServiceGenericsFIN
○       SAP_R3_SelfServiceGenerics_MetaDataFIN
Set up the following for branching to the details screen from Travel work items in the universal worklist:
○       SAP_R3_Travel
○       SAP_R3_Travel_MetaData
●      Connections for the Projects area:
○       SAP_cProjects
○       SAP_cProjects_MetaData

Similar Messages

  • Failed to resolve JCO destination name 'WD_RFC_METADATA_DEST' in the SLD

    Hi!!!
          I am facing a problem, when I run any application, I get the following error,
    *com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCO destination name 'WD_RFC_METADATA_DEST' in the SLD. No such JCO destination is defined in the SLD. *
    Can any one please give some suggestion, on how to overcome this problem.
    Cheers!!!
    Umang

    Hi Umang,
    It seems like you have not activated or Defined your JCO (Java Connectors) in the System Landscape Directory(SLD). Please Login to your SLD and check if you can find the JCO ('WD_RFC_METADATA_DEST'). If you manage to find the Specified JCO, then you need to activate the
    Java Connector.
    I hope this helps. Please let me know if you have any more issues. Dont forget to close the thread if it is answered.
    Best Wishes,
    PG.

  • Failed to resolve JCO destination name 'WD_ALV_METADATA_DEST' in the SLD

    Hello,
    I've got the following problem and hope anybody here could help me with this issue.
    There are two servers (CE 7.1). One DEV and one PROD system.
    At the DEV system "create print version" functionality of an alv-table in my visual composer app works fine.
    But not at the PROD system: There the following message comes up:
    failed to create or init instance of model ''com.sap.ip.bi.alv.service.persist.model.Persist'' in scope APPLICATION_SCOPE with instanceId ''<null>'': com.sap.tc.webdynpro.progmodel.model.api.WDModelException: failed to create instance of model 'com.sap.ip.bi.alv.service.persist.model.Persist'
    at com.sap.tc.webdynpro.progmodel.model.core.ModelFactory.getNewModelInstance(ModelFactory.java:336)
    at com.sap.tc.webdynpro.progmodel.model.core.ModelFactory.getOrCreateModelInstanceFromScopeMaintainer(ModelFactory.java:263)
    at com.sap.tc.webdynpro.progmodel.model.core.ModelFactory.getModelInstance(ModelFactory.java:70)
    at com.sap.tc.webdynpro.progmodel.model.api.WDModelFactory.getModelInstance(WDModelFactory.java:94)
    at com.sap.tc.webdynpro.progmodel.model.api.WDModelFactory.getModelInstance(WDModelFactory.java:73)
    at com.sap.ip.bi.alv.service.persist.PersistRFC.RFCInit(PersistRFC.java:317)
    at com.sap.ip.bi.alv.service.persist.PersistRFC.RFCGetHandle(PersistRFC.java:250)
    at com.sap.ip.bi.alv.service.persist.PersistRFC.setPersonalizationKey(PersistRFC.java:164)
    at com.sap.ip.bi.alv.service.persist.Persist.setPersonalizationKey(Persist.java:157)
    at com.sap.ip.bi.alv.ui.persist.dialog.PersistUI.onSetPersonalizationKey(PersistUI.java:107)
    at com.sap.ip.bi.alv.ui.persist.dialog.PersistUIComp.setPersonalizationKey(PersistUIComp.java:244)
    at com.sap.ip.bi.alv.ui.persist.dialog.wdp.InternalPersistUIComp.wdInvokeMethod(InternalPersistUIComp.java:244)
    at com.sap.tc.webdynpro.progmodel.generation.ExternalControllerPI$ExternalInterfaceInvocationHandler.invoke(ExternalControllerPI.java:339)
    at $Proxy650.setPersonalizationKey(Unknown Source)
    at com.sap.ip.bi.alv.ui.settings.SettingsComp.setPersonalizationKey(SettingsComp.java:545)
    at com.sap.ip.bi.alv.ui.settings.wdp.InternalSettingsComp.wdInvokeMethod(InternalSettingsComp.java:466)
    at com.sap.tc.webdynpro.progmodel.generation.ExternalControllerPI$ExternalInterfaceInvocationHandler.invoke(ExternalControllerPI.java:339)
    at $Proxy649.setPersonalizationKey(Unknown Source)
    at com.sap.ip.bi.alv.util.UISettingsComponent.setPersonalizationKey(UISettingsComponent.java:485)
    at com.sap.ip.bi.alv.ALVController.refreshListInternal(ALVController.java:2794)
    at com.sap.ip.bi.alv.ALVController.refreshServicesInternal(ALVController.java:2943)
    at com.sap.ip.bi.alv.ALVRefreshManager.refresh(ALVRefreshManager.java:510)
    at com.sap.ip.bi.alv.ALVController.refresh(ALVController.java:2235)
    at com.sap.ip.bi.alv.TableView.render(TableView.java:285)
    at com.sap.ip.bi.alv.wdp.InternalTableView.render(InternalTableView.java:329)
    at com.sap.ip.bi.alv.TableView.wdDoModifyView(TableView.java:189)
    at com.sap.ip.bi.alv.wdp.InternalTableView.wdDoModifyView(InternalTableView.java:554)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:89)
    at com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:569)
    at com.sap.tc.webdynpro.progmodel.window.ViewController.modifyView(ViewController.java:251)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:430)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:443)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:443)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:443)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:443)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:443)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:443)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:443)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:443)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:443)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:443)
    at com.sap.tc.webdynpro.clientserver.phases.ModifyViewPhase.execute(ModifyViewPhase.java:70)
    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.clientimpl.scxml.client.SmartClient.executeTasks(SmartClient.java:687)
    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.tc.webdynpro.services.exceptions.WDRuntimeException: Unable to create connection for RFC Metadata Repository WD_ALV_METADATA_DEST
    at com.sap.tc.webdynpro.modelimpl.dynamicrfc.RFCMetadataRepository.getSingleton(RFCMetadataRepository.java:180)
    at com.sap.tc.webdynpro.modelimpl.dynamicrfc.AiiModel.metadataRepository(AiiModel.java:106)
    at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModel.<init>(DynamicRFCModel.java:106)
    at com.sap.ip.bi.alv.service.persist.model.Persist.<init>(Persist.java:144)
    at com.sap.ip.bi.alv.service.persist.model.Persist.<init>(Persist.java:119)
    at sun.reflect.GeneratedConstructorAccessor2233.newInstance(Unknown Source)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
    at java.lang.Class.newInstance0(Class.java:350)
    at java.lang.Class.newInstance(Class.java:303)
    at com.sap.tc.webdynpro.progmodel.model.core.ModelFactory.getNewModelInstance(ModelFactory.java:330)
    ... 109 more
    Caused by: com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection.
    at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnectionUnMapped(SystemLandscapeFactory.java:153)
    at com.sap.tc.webdynpro.services.sal.sl.core.SystemLandscapeInternal.getJCOClientConnectionUnMapped(SystemLandscapeInternal.java:38)
    at com.sap.tc.webdynpro.modelimpl.dynamicrfc.RFCMetadataRepository.getSingleton(RFCMetadataRepository.java:174)
    ... 119 more
    Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCO destination name 'WD_ALV_METADATA_DEST' in the SLD. No such JCO destination is defined in the SLD.
    at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:420)
    at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:234)
    at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:219)
    at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:84)
    at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnectionUnMapped(SystemLandscapeFactory.java:151)
    ... 121 more

    Hi
    Check This Thread
    [Failed to resolve JCO destination name 'WD_RFC_METADATA_DEST']
    See this help
    [https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/user-interface-technology/wd%20java/7.0/portal%20integration/how%20to%20use%20the%20web%20dynpro%20content%20administrator.pdf]
    Kind Regards
    Mukesh

  • How do we import business systems defined in the SLD to IB:configuration...

    how do we import business systems defined in the SLD to IB:configuration...

    hi,
    go to Scenario tab, Object -> New , Select the configuration scenario enter the configuration scenario name then save.
      Expand Service without party ->Select the business system and right click click on next, next select your business systemd.
    IF business system not appeared in ID..go to Environment -> Clear SLD data cache.
      again try to assign the business system.
    Regards,
    Venu.

  • JCo destination error while executing the webservice model

    Hi,
    I have explained what I have done so far and whats my issue right now.
    My requirement is calling a PI interface (exposed as webservice) from webdynpro for java and setting some parameter value to the PI interface based on which our functional flow will continue.
    Done so Far :
    1. Created a webdynpro for java application using NWDI.
    2. received the WSDL file of the PI interface and imported as "Adaptive webservice model" into webdynpro.
    3. used the model and set the parameters to PI interface and executed the model.
    4. I have created JCO destinations in the source system (where the application runs) to communicate to the PI system. A special user has been created and assigned in the connection for communicating.
    5. Also I have created the "Dynamic Webseviceproxies" in visual admin with the same name as the JCO destinations. It had a property "URL" for which I have tested with providing both the PI server URL (Http://<Hostname>:<Port no>) and also the complete webservice URL (Which calls the WSDL file directly)
    when I run the application, I get the following error.
    1. Exception on creation of service metadata for WS metadata destination 'WD_RFC_METADATA_DEST' and WS interface '{<Interface Name>'. One possible reason is that the metadata destination 'WD_RFC_METADATA_DEST' has not been properly configured; check configuration.
    after some exception the next error follows
    2. Invalid Response Code 403 while accessing URL: <The URL which I have provided in the webservice proxy in Visual admin tool> Response Message: Forbidden.
    after some lines of exception from PI server the next error follows.
    3. Error: You are not authorized to view the requested resource
    My Question :
    1. Do I miss anything in Configuration?
    2. Is my way of approach wrong?
    3. Any additional authorization needed?
    Kindly provide some ideas and inputs.
    Regards,
    Mahendran B.

    Dear Mahendran
    JCO destination will not used for the Web Service Model. While creating the webservice model, you need to use the logical destination which you have created in the Visual Admin.
    Please refer to the Secured WebServices II and verify currently used webservice logical destination How To Reimport Web Service Models in Web Dynpro for Java
    You can also refer to
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/900bbf94-a7a8-2910-e298-a651b4706c1e?QuickLink=index&overridelayout=true
    Hope it will helps
    Best Regards
    Arun Jaiswal

  • Failed to resolve JCO destination name in the SLD

    I have installed the ESS/MSS business package, and configured all JCO connections. testing the JCO connections is successful. I can connect to the SLD from the WebDynpro administrator.
    when I run the ESS/MSS, I get the following error:
    "com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCO destination name 'SAP_R3_HumanResources_MetaData' in the SLD. No such JCO destination is defined in the SLD. "

    Hello,
    when I installed ESS/MSS there were two JCO Connections:
    SAP_R3_HumanResources_Metadata
    SAP_R3_HumanResources_MetaData
    Pay attention to the right spelling! I mean the second one is the right one.
    Regards, Michael

  • AS Java 7.10: Can't create JCO destination 'WD_RFC_METADATA_DEST' in SLD

    Hello,
    I registered my J2EE 7.10 in the central SLD (sldmain.wdf.sap.corp:53000) successfully and created JCO destinations WD_RF_METADATA_DEST + WD_MODELDATA_DEST there. But the deployment of a WD application using Adaptive RFC fails because the above JCO destinations are not found (or access to SLD fails at all?). I didn't find any documentaion on how exactly the 2 destinations must be configured. On the central SLD there's no test/ping function for JCO-destinations! Could it be that my WD-deployer still tries to access a local SLD?
    <b>Root Cause</b>
    The initial exception that caused the request to fail, was:
       <b>com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCO destination name 'WD_RFC_METADATA_DEST' in the SLD. No such JCO destination is defined in the SLD.</b>
        at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:442)
        at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:230)
        at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:215)
        at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:106)
        at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:138)
    Thanks and regards,
    Jens

    Jen,
    Edit your JCo destinations and make sure you have Metadata as data type.  I am guessing you are getting this error becuase you might have selected Application data as data type.
    Hope this helps

  • Failed to resolve JCO destination

    Dear support,
    Recently we have made conection from our portal system to 4.7 system and Now we successfully login to portal.But when we click on ' Employee self service ' button we get below errors:
    The initial exception that caused the request to fail, was:
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCO destination name 'SAP_R3_SelfServiceGenerics_MetaData' in the SLD. No such JCO destination is defined in the SLD.
        at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:467)
        at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:233)
        at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:218)
        at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:129)
        at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:149)
        ... 75 more
    I have checked SLD is running and is configured properly , i dont know anything about JCO destinations , this error is giving hint as
    Accessing the System Landsape Directory (SLD) failed. Depending on the concrete reason (see root cause) check the following:
    is the SLD Supplier in the J2EE engine configured correctly? See the SLD documentation for more details about the SLD and about how to configure it.
    are all JCO destinations maintained correctly? Use the preinstalled Web Dynpro Content Admin application to check/edit the destination. Use the Ping and Test functions of the Content Admin to
    I have gone through Blog
    Configuring SLD in Sneak Preview SAP NetWeaver '04 Sneak and all settings looks fine.
    Please make note this system has come recently under our maintainence and i am not much aware what exactly previous Administrator performed , But SLD is running fine.
    Can somebody help at earliest?
    Best Regards,
    AjitR

    Hi,
    Have you defined the JCO destinations in Web Dynpro Content Admin.
    If you havent, look at these link and configure the JCO Destinations required for ESS.
    http://help.sap.com/erp2005_ehp_01/helpdata/en/8c/cb3042366c0521e10000000a155106/frameset.htm
    http://help.sap.com/erp2005_ehp_01/helpdata/en/ca/115e4088dc0272e10000000a155106/frameset.htm
    Reward Points if helpful.
    Regards,
    Abhishek

  • Failed to resolve JCO destination name in SLD

    I have installed the ESS/MSS business package, and configured all JCO connections. testing the JCO connections is successful. I can connect to the SLD from the WebDynpro administrator.
    when I run the ESS/MSS, I get the following error:
    "com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCO destination name 'SAP_R3_HumanResources_MetaData' in the SLD. No such JCO destination is defined in the SLD. "

    The JCO's are case-sensitive so check that the name is spelled exactly: SAP_R3_HumanResources_MetaData
    otherwise it will not work.

  • Failed to resolve JCO destination name 'WD_RFC_METADATA_DEST'

    Hi Experts,
    I am using NWDS 7.1 ehp1 version and  i developed a sample application here to retreive the data from r/3.
    when i try to execute the application it's giving the following error..
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCO destination name 'WD_RFC_METADATA_DEST' in the SLD. No such JCO destination is defined in the SLD.
    can anybody help me to solve this issue..
    thanks,
    viswa

    Hi,
    First test your destination.
    'WD_RFC_METADATA_DEST'
    Login as an Administrator, then click on "Check SLD", Check if if in your System Landscape Directory Both the ABAP technical system and a Web AS JAVA. are created or not????
    If not create the two systems.
    If they are already created then,
    click on "Maintain JCo Destinations" and there you can see all the applications and their corrosponding metadatas. If JCo is already created then status comes in green color or else status comes in red color.
    Check if these JCos are created or not....
    If they are not created then create the JCo destinations.
    If they are already created then Ping them....
    But as per your error, it seems like you haven't maintained JCo destinations.
    Refer this link,
    http://YourPortalURL:50000/webdynpro/dispatcher/sap.com/tcwdtools/Explorer
    Regards,
    Sunaina Reddy T

  • URGENT:  Failed to resolve JCO destination name 'WD_GPMS_RFC_METADATA_DEST'

    Hi,
    when logging in am getting com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCO destination name 'WD_GPMS_RFC_METADATA_DEST' in the SLD.
    I had restarted the Server & and also System.
    Exception:
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCO destination name 'WD_GPMS_RFC_METADATA_DEST' in the SLD. No such JCO destination is defined in the SLD.
    Accessing the System Landsape Directory (SLD) failed. Depending on the concrete reason (see root cause) check the following:
    is the SLD Supplier in the J2EE engine configured correctly? See the SLD documentation for more details about the SLD and about how to configure it.
    are all JCO destinations maintained correctly? Use the preinstalled Web Dynpro Content Admin application to check/edit the destination. Use the Ping and Test functions of the
    Content Admin to verify that each destination is properly configured.
    Additional information about the System Landscape Directory and the Web Dynpro Content Admin can be found in the SAP Developer Network (SDN) and in the Online Help for the SAP Web Application Server (installed with SAP NetWeaver Developer Studio and available online).
    Note: the above hints are only a guess. They are automatically derived from the exception that occurred and therefore can't be guaranteed to address the original problem in all cases.
    Please help me resolving it.
    Thanks,
    Hussain

    Hello Hussain,
    It looks like your Basis team has added another JCO destination to your Landscape....just check with them and create the jco destination on the portal...to fix it.
    Let me know if it helps.

  • ESS/ MSS  JCO destination error...

    Hi All,
    I have created all JCO destinations and when i test them , the result is successful
    But once i click on ess/mss tab in portals, i get the error..
    <i>com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCO destination name 'SAP_R3_HumanResources_MetaData' in the SLD. No such JCO destination is defined in the SLD.</i>
    But i have maintained SAP_R3_HumanResources_MetaData in the SLD.. Actually i have two SAP_R3_HumanResources_MetaData services one is active and another is inactive..
    For SAP_R3_HumanResources -- i have used "Logon Ticket" and for SAP_R3_HumanResources_MetaData -- used userid & pwd.
    Actually i have to do UserMapping as my portal userid and R/3 userid are different.. Then in this case am i creating JCO destinations correctly.. If not how to do..
    Please throw some light into this problem by your valuable suggestions.
    Thanks & Regards,
    Mahesh.M.R

    Hi
    I am having the exact same problem (i think). I believe that the problem is caused by a failed connection to the SLD.
    In my case, if I scroll the bottom of the error page, the 'Detailed exception chain' has the error:
    TypeBroker failed to access SLD: Error while obtaining JCO connection.
    The same error can be found in the DefaultTrace.
    This ESS is on a nw2004s sandbox portal (trying to reach an ECC 6.0 sandbox), but being lazy I just reused the SLD in my Development environment.
    This is however a Java WAS 6.40 and according to Note 954820 (Compatibility of SLD in the system landscape)
    QUOTE
    In general, the connection of systems to the SLD is released for SLD client applications with releases earlier than or equal to the SLD release (to be more precise: the AS Java release on which the SLD runs). Within a release, all Support Packages are released.
    UNQUOTE
    So, i'll try activating the SLD on a nw2004s JAVA WAS and use that instead.
    Regards
    Stig

  • Jco destinations

    hi,
    i have a little problem configurating SLD for Web Dynpro.
    i run my web dynpro application which uses rfc model wd_rfc_flightlist_metadata_dest,
    i'm getting error:
    "com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCO destination name 'WD_RFC_FLIGHTLIST_METADATA_DEST' in the SLD. No such JCO destination is defined in the SLD."
    As I understand I have to create a new destination... can anybody tell me the exact parameters for it,
    destination name, type, url..?
    Thank you.
    MaryM

    Thank you for your answers.
    I still hae a littel doubt. I checked and both SLD and JCo are running.
    I was able to define JCo destination (ping ok), but testing it gives me an error:
    "com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Nombre o clave de acceso incorrectos (repita la entrada al sistema) "
    When defining a destination, what authentication info i must enter?
    And when I define the particular SAP system to receive data from?
    Thank you!
    MaryM

  • Failed to resolve JCO destination name 'SAP_R3_SelfServiceGenerics_MetaData

    Hi,
    Got the following error message after login to my portal to access the ESS/MSS page:
    The initial exception that caused the request to fail, was:
       com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCO destination name 'SAP_R3_SelfServiceGenerics_MetaData' in the SLD. No such JCO destination is defined in the SLD.
        at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:476)
        at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:241)
        at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:226)
        at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:129)
        at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnectionUnMapped(SystemLandscapeFactory.java:168)
        ... 75 more
    Any suggestion what is problem?

    Hi Wooi,
    Please create JCO destination 'SAP_R3_SelfServiceGenerics_MetaData' and 'SAP_R3_SelfServiceGenerics_MetaDataFIN' for Metadata. First check SLD working fine or not. if the SLD is fine then update SLD data supplier in the visual administrator.
    As you metioned the JCO are grayed out. then you need to update host and service file in server location. the do SLD and SLD data supplier test.
    Once JCO connection test will successful then your issue will resolved.
    Hope it will helps
    Regards
    Arun Jaiswal

  • Failed to resolve JCO destination name 'WD_FLIGHTLIST_RFC_METADATA_DEST' i

    Dear all,
    When i was running a Wec dynpro Application created with The abap Function Modul BAPI_FLIGHT_GETLIST, a error          "com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCO destination name 'WD_FLIGHTLIST_RFC_METADATA_DEST' in the SLD. No such JCO destination is defined in the SLD. "
    happened. Can someone tell me how to sole this error?Thanks .
    Rgds,
    Sweet.

    Hi,
    when you are creating Adaptive RFC Model .
    in the 2nd step it will ask for 2 things
    1.Define the logical system name for model instances
    2.Define the logical system name for RFC Metadata.
    what ever the names you give here you have to create JCO destinations for that.
    Logon to portal.
    navigate to content Administartion---->webdynpro
    there you have a button "Maintain JCO Destinations".
    click on that
    In the table you will find WD_FLIGHTLIST_RFC_METADATA_DEST
    with status with an icon in red color.
    That is indicating that you are JCO destination is not created.
    click on create button and follow the below link from page no 25-27
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/355b9c90-0201-0010-d2a8-89fece426526
    Thanks & regards,
    lokesh

Maybe you are looking for

  • Google calendar and iCal

    I have a  google calendar and all day events appear out of order in ical they are fine in iOS apps on the iPhone and the iPad, but on the desktop they are all messed up and it appears to random because every day they are ordered differently? Any advi

  • Errors during deploying EJB app

    Hello all, I am trying the develop an EJB app in eclipse juno with weblogic 9.1. I have installed the oracle tools and weblogic has been configured with the EJB project in eclipse. When I start weblogic from the servers tab within eclipse the followi

  • Getting contacts from my iphone to my mac

    I have been in the Apple Store today and they have advised that I need to delete all my phone history and set up as a new phone as having battery issues.  I am trying to transfer my numbers and contacts to my mac but I can't do it, it wont allow me a

  • From iPhoto 2 to iPhoto 6 in one leap?

    I've probably had iPhoto in my iMac for several years, but I've never tried to use it because of techphobia. Today, however, I decided to give it try, since I have always found David Pogue's books to be informative and easy to follow. Anyway, I soon

  • Workflow setting to launch applciation from portal UWL

    Hi, Do we require to make any settings if we are to launch our Dynpro application from the portal UWL. I have a parameter whose value keeps changing for each workitem generated. Do i need to make any settings on the backend side so that this value is