JCo Destination Failing With RFC_Error_COMMUNICATION

Hi Gurus,
We installed a new Bi system with ABAP and JAVA stacks on different hardware and SIDs, now we have problem in integration where JCO BI Meta Data connection is giving following error if I test it. Ping is also failing.
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM  TYPE=B MSHOST=host.domain.com GROUP=PUBLIC R3NAME=<SID> MSSERV=sapms<SID> PCS=1 LOCATION    CPIC (TCP/IP) on local host with Unicode ERROR       service 'sapms<SID>' unknown TIME        Tue Aug 10 05:26:09 201 RELEASE     701 COMPONENT   NI (network interface) VERSION     38 RC          -3 MODULE      nixxhsl.cpp LINE        776 DETAIL      NiHsLGetServNo: service name cached as unknown COUNTER     2
I checked sapms<SID> in etc -> services on ABAP host it is defined to message server port, I have added sapms<SID> as 8100 in SLD connection.
All three connections from portal as successful, still JCo destinations are not working.
Note:I have initally added message server port as 3600 in SLD connection where I replaced it to 8100 now, not sure whether this has any impact.
Kindly help.
Thanks
Gopal

Hi,
Please add the sapmsSID entries for both systems (java and abap) in the /etc/services file of BOTH SERVERS. This means that each server should have entries for every system in your landscape.
Additionally, please ensure that this is set to 36<NN> and not 8100 as you mentioned. The reason is that 8100 is ABAP HTTP port, but 36<NN> is message server port. These two are different.
Try this.
Regards,
Shitij

Similar Messages

  • Creates  JCO Destination Fails with Error

    Hello
    I am trying to create a JCO Connection in our EP6-SP9 (Menu Content Administration -> Web Dynpro -> Create JCO Connection). I have not installed a SLD for EP6 but have configured the EP6 to use the SLD of the XI 3.0 SP9. The test connection works OK. The creation of the JCO fails with the message below
    An error has occurred:
    "Failed to process the request."
    Please contact your system administrator.
    Web Dynpro client:
    HTML Client
    Web Dynpro client capabilities:
    User agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0), version: null, DOM version: null, client type: msie6, client type profile: ie6, ActiveX: enabled, Cookies: enabled, Frames: enabled, Java applets: enabled, JavaScript: enabled, Tables: enabled, VB Script: enabled
    Web Dynpro runtime:
    Vendor: SAP, Build ID: 6.4009.00.0000.20041011171310.0000 (release=630_VAL_REL, buildtime=2004-10-19:21:48:59[UTC], changelist=290362, host=PWDFM026)
    Web Dynpro code generators of DC sap.com/tcwdtools:
    No information available
    Web Dynpro code generators of DC sap.com/tcwddispwda:
    No information available
    Web Dynpro code generators of DC sap.com/tcwdcorecomp:
    No information available
    J2EE Engine:
    No information available
    Java VM:
    Java HotSpot(TM) Server VM, version: 1.4.2_06-b03, vendor: Sun Microsystems Inc.
    Operating system:
    Windows 2000, version: 5.0, architecture: x86
    Error stacktrace:
    java.lang.NullPointerException
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:871)
         at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)
         at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateJCODestinations(NameDefinition.java:272)
         at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateNavigation(NameDefinition.java:237)
         at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:144)
         at com.sap.tc.webdynpro.tools.sld.wdp.InternalNameDefinition.wdDoInit(InternalNameDefinition.java:223)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
         at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:274)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:540)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:398)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:555)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:422)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:130)
         at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:43)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:540)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:398)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.makeVisible(ViewManager.java:620)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.performNavigation(ViewManager.java:263)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:737)
         at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:350)
         at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:635)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
         at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:249)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
         at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
    I request help in resolving the above error
    Thanks & regards
    S Lahiri

    Hi Subhabrata, I get the same error. Let me know the solution if you already solved it. Maulin

  • JCo APIs fail with Message Server

    Hi Experts,
    I use JCo 2.0 to interact with SAP System via Message Server.
    When My application try to connect, it's generated this error:
    Connect_PM  MSHOST=HOST, R3NAME=XYZ, GROUP=GROUP
    ERROR       service 'sapmsXYZ' unknown
    TIME        Tue May 19 15:09:28 2009
    RELEASE     620
    COMPONENT   NI (network interface)
    VERSION     36
    RC          -3
    MODULE      nixxi_r.c
    LINE        2606
    DETAIL      NiIServToAddr
    COUNTER     7
    .^.
    What is the problem?
    Thanks.
    Marco Genova
    Edited by: m.genova on May 19, 2009 4:23 PM

    Hello,
    The services mapping (name vs. TCPor UDP port number) are specified in /etc/services or the corrsponding file for your OS.
    Obviously "sapmsXYZ" is missing there. sapmsXYZ should match the TCP port of the message server.
    Kind regards,
    Tsvetomir

  • 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 Alias

    Hi,
    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 Kalluri

    Hi 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

  • 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.

  • 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

  • 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

  • SSIS 2012 is intermittently failing with below "Invalid date format" while importing data from a source table into a Destination table with same exact schema.

    We migrated Packages from SSIS 2008 to 2012. The Package is working fine in all the environments except in one of our environment.
    SSIS 2012 is intermittently failing with below error while importing data from a source table into a Destination table with same exact schema.
    Error: 2014-01-28 15:52:05.19
       Code: 0x80004005
       Source: xxxxxxxx SSIS.Pipeline
       Description: Unspecified error
    End Error
    Error: 2014-01-28 15:52:05.19
       Code: 0xC0202009
       Source: Process xxxxxx Load TableName [48]
       Description: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80004005.
    An OLE DB record is available.  Source: "Microsoft SQL Server Native Client 11.0"  Hresult: 0x80004005  Description: "Invalid date format".
    End Error
    Error: 2014-01-28 15:52:05.19
       Code: 0xC020901C
       Source: Process xxxxxxxx Load TableName [48]
       Description: There was an error with Load TableName.Inputs[OLE DB Destination Input].Columns[Updated] on Load TableName.Inputs[OLE DB Destination Input]. The column status returned was: "Conversion failed because the data value overflowed
    the specified type.".
    End Error
    But when we reorder the column in "Updated" in Destination table, the package is importing data successfully.
    This looks like bug to me, Any suggestion?

    Hi Mohideen,
    Based on my research, the issue might be related to one of the following factors:
    Memory pressure. Check there is a memory challenge when the issue occurs. In addition, if the package runs in 32-bit runtime on the specific server, use the 64-bit runtime instead.
    A known issue with SQL Native Client. As a workaround, use .NET data provider instead of SNAC.
    Hope this helps.
    Regards,
    Mike Yin
    If you have any feedback on our support, please click
    here
    Mike Yin
    TechNet Community Support

  • [svn] 1013: Bug: LCDS-180 - [WebLogic 10.1 on Suse9] MxUnit Dynamic destination "SecurityEmployeeUser" test fails with a NullPointerException

    Revision: 1013
    Author: [email protected]
    Date: 2008-03-28 17:24:25 -0700 (Fri, 28 Mar 2008)
    Log Message:
    Bug: LCDS-180 - [WebLogic 10.1 on Suse9] MxUnit Dynamic destination "SecurityEmployeeUser" test fails with a NullPointerException
    QA: Yes
    Doc: No
    Details:
    This prevents the NPE but for non-servlet endpoints you need to be sure to define your users/roles in Weblogic's default security realm. The test was failing because login was failing, most likely because the regression server wasn't fully configured.
    Ticket Links:
    http://bugs.adobe.com/jira/browse/LCDS-180
    Modified Paths:
    blazeds/branches/3.0.x/modules/opt/src/weblogic/flex/messaging/security/WeblogicLoginComm and.java

  • 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 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,
    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

  • 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

Maybe you are looking for