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
Similar Messages
-
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 -
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,
viswaHi,
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 -
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,
HussainHello 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. -
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 -
Failed to resolve JCO destination name
I am using RFC model to post form data to backend. This is the error I got when I tried to run the application.
<i>Failed to resolve JCO destination name 'MI2_APPLICATIONDATA' in the SLD. No such JCO destination is defined in the SLD</i>
I have JCO destination configured in my SLD. I can see them in green when I go to Deployed Content --> System Defined Content. I was able to successfully test and ping them.
One thing I observed is my application does not show up in the Deployed Content --> Local. Other earlier applications which I deployed before are showing up, but not the current one. I restarted J2EE server, rebuilt, redeployed. No luck !!Thats exactly the problem. I figured it out myself and thought of editing this thread. But you have replied by then. Thanks for the quick reply and awarded you the points you deserve.
-
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!!!
UmangHi 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. -
Hi All,
In the webdynpro content administrator.
All the 'create ,the other links like 'test', 'preview','edit','ping','remove' are all disabled.
when i am trying to access the webdynpro application i am getting the following error. can any body tell me what is the reason behind this.
For your reference, i have uploaded the screen shot of the webydnproContentAdministator , please look in to the wiki in the following path
My Home > Web Dynpro Java > Main > Attachments
comments : Webdynpro content administrator sceen shot
Thanks,
vijay
Failed to resolve JCO destination name 'WD_SO_INTERNAL_RFC_METADATA_DEST' i
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:150)
... 65 moreVishal,
Yes, tha't's it. The SLD isn't configurated. You have to configurate the SLD before to use JCO Destinations.
Have a look at this forum thread: Configure SLD for Web Dynpro -
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 moreHi
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 -
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,
AjitRHi,
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 ping JCo destination 'WD_RSDAS_RFC_METADATA_DEST'.
Hello SDNers,
I have Netweaver ABAP trial SPS12 and Netweaver Java Trial SPS14 installed in my laptop. I have also configured SLD and successfully run transaction RZ70. I'm stucked at configuring JCo.
From Web Dynpro Content Administrator, when I ping, it gives me:
Failed to ping JCo destination 'WD_RSDAS_RFC_METADATA_DEST'.
From Web Dynpro Content Administrator, when I test, it gives me:
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=hapizorr GROUP=NETWEAVER R3NAME=NSP MSSERV=sapmsNSP PCS=1 ERROR Group NETWEAVER not found TIME Thu Oct 16 23:59:36 2008 RELEASE 700 COMPONENT LG VERSION 5 RC -6 MODULE lgxx.c LINE 4299 DETAIL LgIGroupX COUNTER 1
I have created group NETWEAVER via transaction SMLG at the backend system. I have entered sapmsNSP 3600/tcp in the service file. I have also successfully pinged to the hostname. I have also successfully telnetted to hostname 3600.
What's wrong with my config? Help, pls!
Rgds,
Hapizorr Rozi AliasHi,
Just to test, try to connect using SPACE LOGON GROUP
Another tip, verify the property rdisp/autoabaptime on profile of your ABAP Installation.
Try to change it from 0 to 300.
Best regards -
Failed JCO destination name 'WD_RFC_METADATA_DEST' and MODEL DATA
Hi Friends
I am created "WD_RFC_METADATA_DEST". this meta data.When i am created this metadata i was called message server as technical system of CRM server.
means i am created metadata for CRM System
Once metadata had complted then i was cheing click on "Text"
Here it display this error message
Model Data test
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=ecc15 GROUP=PUBLIC R3NAME=E15 MSSERV=sapmsE15 PCS=1 ERROR Group PUBLIC not found TIME Fri Feb 19 01:12:26 2010 RELEASE 700 COMPONENT LG VERSION 5 RC -6 MODULE lgxx.c LINE 4299 DETAIL LgIGroupX COUNTER 1
Meta data test
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=ecc15 GROUP=PUBLIC R3NAME=E15 MSSERV=sapmsE15 PCS=1 ERROR Group PUBLIC not found TIME Fri Feb 19 01:13:19 2010 RELEASE 700 COMPONENT LG VERSION 5 RC -6 MODULE lgxx.c LINE 4299 DETAIL LgIGroupX COUNTER 1
What is problem. i m not getting can u tell me how slove this problem.
Regards
Vijay KalluriHi Vijay,
You need check following thing to resolve this issue.
1. Check the your host file entries for CRM System (Start>Run>enter 'drivers'>etc>hosts)
2. Check SLD test is successfull or not.
3. As per your error message group PUBLIC not found. Check in the CRM system (T-code : SMLG) whether PUBLIC group is available or not.
Then check JCO destination parameter again and test it.
Hope this will helps you.
Thanks
Arun -
Failed JCO destination name 'WD_RFC_METADATA_DEST'
Hi Friends
I am created "WD_RFC_METADATA_DEST". this meta data.When i am created this metadata i was called message server as technical system of CRM server.
means i am created metadata for CRM System
Once metadata had complted then i was cheing click on "Text"
Here it display this error message
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=bxecc6 GROUP=SPACE R3NAME=BX6 MSSERV=sapmsBX6 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR service 'sapmsBX6' unknown TIME Wed Dec 30 07:25:44 2009 RELEASE 701 COMPONENT NI (network interface) VERSION 38 RC -3 MODULE nixxhsl.cpp LINE 776 DETAIL NiHsLGetServNo: service name cached as unknown COUNTER 1
What is problem. i m not getting can u tell me how slove this problem.
Regards
Vijay KalluriThe error is - service 'sapmsBX6' unknown
you need to add the entry
sapmsBX6 36XX/tcp (where XX is your system number - usually 00)
to your windows services file (on the server) which is located in
<windows dir>\system32\drivers\etc -
Failed to ping JCo destination 'WD_RFC_METADATA_DEST'.
please help me
i am getting the following error
my r3 system name is eccr3dev(Version Ecc6)
frontend id EP6.0
i have done the entry in sld and the hosts and services file of my eptest server
on testing the jco i am getting the foll error message
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=eccr3dev GROUP=PUBLIC R3NAME=TU1 MSSERV=sapmsTU1 PCS=1 ERROR partner not reached (host eccr3dev, service sapmsTU1) TIME Fri Feb 29 11:58:59 2008 RELEASE 640 COMPONENT NI (network interface) VERSION 37 RC -10 MODULE nixxi_r.cpp LINE 8663 DETAIL NiPConnect2 SYSTEM CALL SiPeekPendConn ERRNO 10061 ERRNO TEXT WSAECONNREFUSED: Connection refused COUNTER 2
please guide meHi Nitesh
I am facing the same problem
please help me to solve this issue..
i have completed all the task as discussed in this discussion earlier.
Thanks and regards
Parmod Kumar
if u have any docs so please send me @ [email protected]
Maybe you are looking for
-
Invoice showing as archieved.
Dear friends, I got a typical issue related to VFX3. I got a document no. from the users, When I see in FB03 that document is present. Reference has to be my invoice no. that is showing archieved and the transaction showing VFX3. What could have hap
-
All of a sudden I cannot import
Aperture will not import photos. When I try and do it from the card reader, it imports nothing even though I select all. I tried copying the photos to a folder and importing from there but that does not work. I get a message that aperture imported wi
-
how to solve this problem? '' can not activate cellular data network failure'' authenticating PDP from already thank you
-
The "+" icon that opens new tabs does not open a tab.
-
Determining in which tablespace the indexes are imported to
Hello all, Often, the tables are in one tablespace and the indexes of these tables are on another tablespace. If we have a DMP file done on a schema-level. Is there a way to import this DMP by specifying in the IMP that the tables of the exported sch