Couldn't create jco client connection for logical system

Dear Experts,
we are facing a strange issue in our custom webdynpro java application, few of our portal users are getting the "couldn't create jco client connection for logical system" for Model Data JCO Destination. below are details
1. portal version 7.02 SP14 (we have recently updated to SP14 from SP02-- is this is causing the issue ?)
     1.1. updated the NWDI track with SP14 SCA files as well as added latest WD Runtime SCA file deployed the applications to Production also.
2. above said exception is inconsistent and happening for only few users
3. ping and test of jco destinations are successfull in content administration as well as in SLD, destinations were added in the SLD system.
4. cleared the JCO ARFC meta data cache in webdynpro console
5. jco destinations are configured using uid/pwd, configured user is not locked active and tested in the backend by logging in with the same user.
6. restarted the portal server
even though, we are getting the above said exception for few of portal users randomly.
Please help me on this ASAP, as i am not getting any further help on this.
Thanks,
Ram.

Hello Ram,
Check the JCo Pool Configuration settings of your JCO Destination. This message normally comes when the maximum connections has been reached. Increase the "Maximum Connections" to some number depending on the usage. A good habit is to disconnect the jco connection after executing the same in your webdynpro code if you don't want it to be synchronous.
<ModelName>.modelInstance().disconnectIfAlive()
Hope this helps.
Regards
Vijay

Similar Messages

  • Exception while creating JCo client connection Failed to create

    Hello all -
       I am trying to create JCo metadata connections and I am getting the below error trace.
    Exception while creating JCo client connection Failed to create new JCO client connection SAP_R3_HumanResources_Metadata: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to change password for key SAP_R3_HumanResources_Metadata in secure storage at com.sap.tc.webdynpro.serverimpl.wdc.sl.SecureStorageWrapper.changePassword(SecureStorageWrapper.java:149) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection(SystemLandscapeFactory.java:299) at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.createJCOClientConnection(WDSystemLandscape.java:107) at com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionFinish(ButtonBar.java:265) at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:265) at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132) at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250) at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53) 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:401) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) 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:104) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176) Caused by: com.sap.security.core.server.securestorage.exception.ObjectStorageException at com.sap.security.core.server.securestorage.remote.RemoteSecureStorageClientContextImpl.storeObject(RemoteSecureStorageClientContextImpl.java:600) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SecureStorageWrapper.changePassword(SecureStorageWrapper.java:137) ... 33 more
    Could anybody please suggest what is wrong with this creation?
    Thanks much!!

    Hi Maria,
    Please update the host and sevice file first then check the SLD test and SLD Data supplier in visual admin.
    Also check and verify the data using in the Jco destination creation.
    Hope it will helps
    Regards
    Arun Jaiswal

  • Unable to create SASL client connection for authentication mechanism [PLAIN

    I have problem to use dscc to admin my ds/dps servers, since I the dscc can't contact dscc agent. Though the agent is running on the default port number with network-bind-port of 0.0.0.0, there is nothing I can do to fix it.
    I debug the problem, and found following errors in server.log under dscc (deployed on SUN AS 8.2):
    Message: Unable to create SASL client connection for authentication mechanism [PLAIN]|#]
    [#|2007-08-21T15:28:40.252-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.stream.out|_ThreadID=11;|
    15:28:40 | httpWorkerThread-8080-0 | com.sun.web.admin.directory.dcc.util.ViewBeanUtils:appendDebugLine | com.sun.jmx.remote.opt.security.SASLClientHandler.initialize(SASLClientHandler.java:124)|#]
    [#|2007-08-21T15:28:40.253-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.stream.out|_ThreadID=11;|
    15:28:40 | httpWorkerThread-8080-0 | com.sun.web.admin.directory.dcc.util.ViewBeanUtils:appendDebugLine | com.sun.jmx.remote.opt.security.AdminClient.connectionOpen(AdminClient.java:131)|#]
    [#|2007-08-21T15:28:40.254-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.stream.out|_ThreadID=11;|
    15:28:40 | httpWorkerThread-8080-0 | com.sun.web.admin.directory.dcc.util.ViewBeanUtils:appendDebugLine | com.sun.jmx.remote.generic.ClientSynchroMessageConnectionImpl.connect(ClientSynchroMessageConnectionImpl.java:71)|#]
    [#|2007-08-21T15:28:40.256-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.stream.out|_ThreadID=11;|
    15:28:40 | httpWorkerThread-8080-0 | com.sun.web.admin.directory.dcc.util.ViewBeanUtils:appendDebugLine | javax.management.remote.generic.GenericConnector.connect(GenericConnector.java:177)|#]
    [#|2007-08-21T15:28:40.257-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.stream.out|_ThreadID=11;|
    15:28:40 | httpWorkerThread-8080-0 | com.sun.web.admin.directory.dcc.util.ViewBeanUtils:appendDebugLine | javax.management.remote.jmxmp.JMXMPConnector.connect(JMXMPConnector.java:119)|#]
    [#|2007-08-21T15:28:40.258-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.stream.out|_ThreadID=11;|
    15:28:40 | httpWorkerThread-8080-0 | com.sun.web.admin.directory.dcc.util.ViewBeanUtils:appendDebugLine | javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)|#]
    [#|2007-08-21T15:28:40.260-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.stream.out|_ThreadID=11;|
    15:28:40 | httpWorkerThread-8080-0 | com.sun.web.admin.directory.dcc.util.ViewBeanUtils:appendDebugLine | com.sun.directory.nquickclient.NquickClient.getJmxConnector(NquickClient.java:816)|#]
    [#|2007-08-21T15:28:40.261-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.stream.out|_ThreadID=11;|
    15:28:40 | httpWorkerThread-8080-0 | com.sun.web.admin.directory.dcc.util.ViewBeanUtils:appendDebugLine | com.sun.directory.nquickclient.NquickClient.getConnector(NquickClient.java:519)|#]
    [#|2007-08-21T15:28:40.262-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.stream.out|_ThreadID=11;|
    15:28:40 | httpWorkerThread-8080-0 | com.sun.web.admin.directory.dcc.util.ViewBeanUtils:appendDebugLine | com.sun.directory.nquickclient.NquickClient.getConnectorSystemAuthentication(NquickClient.java:314)|#]
    [#|2007-08-21T15:28:40.263-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.stream.out|_ThreadID=11;|
    15:28:40 | httpWorkerThread-8080-0 | com.sun.web.admin.directory.dcc.util.ViewBeanUtils:appendDebugLine | com.sun.directory.dcc.core.NquickPool.getSyncServerMBean(NquickPool.java:435)|#]
    [#|2007-08-21T15:28:40.264-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.stream.out|_ThreadID=11;|
    15:28:40 | httpWorkerThread-8080-0 | com.sun.web.admin.directory.dcc.util.ViewBeanUtils:appendDebugLine | com.sun.directory.dcc.core.NquickPool$1.run(NquickPool.java:320)|#]
    [#|2007-08-21T15:28:40.271-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.stream.out|_ThreadID=11;|
    15:28:40 | httpWorkerThread-8080-0 | com.sun.web.admin.directory.dcc.util.ViewBeanUtils:appendDebugLine | java.lang.Thread.run(Thread.java:534)|#]
    [#|2007-08-21T15:28:40.289-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.stream.out|_ThreadID=11;|
    15:28:40 | httpWorkerThread-8080-0 | com.sun.web.ui.taglib.pagetitle.CCPageTitleTag:appendPageTitleAlertAndText | Node has no attributes.|#]
    [#|2007-08-21T15:28:40.293-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.stream.out|_ThreadID=11;|
    15:28:40 | httpWorkerThread-8080-0 | com.sun.web.ui.taglib.pagetitle.CCPageTitleTag:appendPageActions | Could not obtain pageactions element.|#]
    [#|2007-08-21T15:28:40.295-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.stream.out|_ThreadID=11;|
    15:28:40 | httpWorkerThread-8080-0 | com.sun.web.ui.taglib.pagetitle.CCPageTitleTag:appendPageViewsMenu | Could not obtain pageviews element.|#]
    Please help if you could figure out what's going on. Thanks!

    Bug ID: 6551672
    Synopsis: SunAS claims "Unable to create SASL client conn for auth mechanism" and do not talk to Cacao
    Work Around:
    Work arround:
    Change the JVM of used by App Server.
    Edit the file:
         /usr/appserver/config/asenv.conf
    and replace
         AS_JAVA="/usr/j2se"
    by
         AS_JAVA="/usr/java"
    Then restart your AS domain.

  • JCo client connection Failed to create new JCO client connection

    hi All
    I am trying to create a new JCO destination ion CE7.1 webdynpro content Admin. but I am getting following error.
    Exception while creating JCo client connection Failed to create new JCO client connection weter: com.sap.lcr.api.cimclient.LcrException: CIM_ERR_ACCESS_DENIED: User is not in role LcrInstanceWriterLD at com.sap.lcr.api.cimclient.SimpleResponseAnalyser.raiseExceptionOnError(SimpleResponseAnalyser.java:120) at com.sap.lcr.api.cimclient.SimpleResponseAnalyser.getIResult(SimpleResponseAnalyser.java:53) at com.sap.lcr.api.cimclient.CIMOMClient.sendImpl(CIMOMClient.java:220) at com.sap.lcr.api.cimclient.CIMOMClient.send(CIMOMClient.java:148) at com.sap.lcr.api.cimclient.CIMOMClient.createInstanceImpl(CIMOMClient.java:669) at ......
    SLD is Up and running
    CIM data is imported
    Solution tried :
    1) As no role wtih name LcrInstanceWriterLD was existing in the server ,hence created a new role with same name and assigned the LCR related action . Assigned the role to the user through which we are creating JCOs.
    But we still getting the same error.
    regards
    Poonam

    Hi Poonam!
    Got to dig in the past a bit, I remember Users being able to create SLD object have to have certain permissions set in the J2EE UME. Simple Admin rights do not suffer, if I recall right.
    Unfortunately I cannot go further in detail because this issue has been solved by a long gone collegue of mine.
    Good luck anyway!
    Jürgen

  • JCO connection error:Couldn't create JCOClientConnection for logical System

    Hi All,
    We are facing a production outage issue.
      We have a Federated Portal Network setup where one of our producer goes down automatically (seems on heavy load).
      On this Producer server we have 3 Web Dynpro applications deployed and default trace is full with JCO connection error   saying Could   not create JCOClientConnection for logical System: CSVMR_WD_MODELDATA_DEST.
    We had issue with max allowed JCO connections so we changed the below mentioned parameters for JCO connection settings in portal:
    u2022     Minimum value of JCo Pool Size in total = 80
    u2022     Minimum value for CPIC_MAX_CONV per SAP Web AS = 320
    u2022     Maximum Number JCo Connections = 160
    Please let us know if we are missing on some settings, any help in this regard is appreciated.
    Regards,
    Priyanka

    Hi,
    As you have already increased the maximum number of connections/pool size but still you are facing this problem. I would suggest you to check the web dynpro application which might not be able to release/disconnect the JCO connection.
    Please check this [Thread|How to close a model object connection for Adaptive RFC?; for more details.
    Regards
    Puneet

  • Failed to create new JCO client connection WD_FLIGHTLIST_RFC_METADATA_DEST:

    I tried the demo in SDN, but failed .
    Why?

    Sorry I forget posting the msg:
    for WD_FLIGHTLIST_MODELDATA_DEST:
    nnection for 'WD_FLIGHTLIST_MODELDATA_DEST' was sucessfully tested with user 'ZZHZHU'
    But :
    for WD_FLIGHTLIST_RFC_METADATA_DEST:
    Failed to create new JCO client connection WD_FLIGHTLIST_RFC_METADATA_DEST: com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection. at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:140) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection(SystemLandscapeFactory.java:286) at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.createJCOClientConnection(WDSystemLandscape.java:107) at com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionFinish(ButtonBar.java:224) at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:252) at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:100) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:299) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:640) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59) at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251) 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:391) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:265) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:345) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:323) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:865) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:240) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148) 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.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java:321) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162) Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve connection parameter for WD_FLIGHTLIST_RFC_METADATA_DEST at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestinaton(JCOClientConnection.java:664) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:508) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:247) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:221) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:101) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:138) ... 31 more Caused by: java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:474) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestinaton(JCOClientConnection.java:558) ... 36 more

  • Could not create JCOClientConnection for logical System:

    Hi,
    I am facing a wierd problem in using the JCO destinations.
    I created a page where it is using some JCO destinations say SAP_R3_HumanResources.
    when i open the page it is working for the first time .without closing the page if i open the same page again it is giving the following error
    Error connecting using JCO.Client: null
    Error connecting using JCO.Client: null
    Pernr:Could not create JCOClientConnection for logical System: SAP_R3_HumanResources - Model: class com.swissre.CustomData. Please assure that you have configured the RFC connections and/or logical system name properly for this model!
    Please let me know how to solve this issue
    Thanks
    Bala Duvvuri

    Hi Bala,
    It seems that this is a custom webdynpro application which when executed causes such problem.  This might be due to JCO connection not released back to the pool.
    Please refer to the following threads and that might be helpful. 
    Re: JCO Connection close
    How to close a model object connection for Adaptive RFC?
    You might have to call disconnectIfAlive method on your model.
    Regards,
    Jigar

  • Could not create JCOClientConnection for logical System: MUSA_MODEL_DATA

    Hi,
    I am facing a big problem...I have created WebDynpro Application & when I am running that application from WebDynpro, it's showing the page but giving me the error message as:-
    Could not create JCOClientConnection for logical System: MUSA_MODEL_DATA - Model: class com.bcone.bcool.musa.model.MUSABAPI. Please assure that you have configured the RFC connections and/or logical system name properly for this model!
    What do I do? what connections I have to check?
    pls help.

    Hey if you are connecting to SAP system making use of adaptive RFC model you hav to create logical systems(JCOs).So while creating the model you have to specify 2 logical system names(one for model data or on for the meta data).If you have not created the JCOs or if the JCOs are not active  then you are going to get this type of error.To activate those JCOs ask your administrator to activate the JCO for metadata of your application.If you are having proper credentials then log on to portal
    System administration>webdynpro>expand the local directory>select your project>click on maintain JCOs and activate the JCO for the metadata.
    Or else change the logical system in your application.

  • Could not create JCOClientConnection for logical System: SAP_R3_HumanResour

    Hi,
    For all the standard ESS (sap.com) the JCo connection used is SAP_R3_HumanResources .
    All the applications are working fine.
    I am trying to add a test Component in one of the (sap.com~eepro) for testing a standard BAPI call for getting user details.
    I have used the same Model and the same SAP_R3_HumanResources destination name.
    But i get the following error when i try to execute the standard BAPI_USER_GETDetails (non - HR).The other applications for standard components (Vc ) work when i run the application.
    My question here is why a custom , local webdynpro when try to make a RFC call using the running already existing JCO connection throws such error.
    How could this be solved.Note the connection is running and working fine for all the ESS webdynpros!!
    Error:
    Could not create JCOClientConnection for logical System: SAP_R3_HumanResources - Model: class com.test.hr.model.Test. Please assure that you have configured the RFC connections and/or logical system name properly for this model!
    Your experience would be worthy enough.
    Regards,
    Swathi

    Hi Swathi,
    Here are some suggestions to trace down to the actual problem.
    1) First check if all users are having this issue. (All other applications working and only one application giving problem)
    2) If no, then take list of users having this problem and check their portal and SAP accounts
    3) If yes, then concentrate on testing the JCo connections and the user account mapped in JCo settings
    Possible things u can check is user's portal account (locked or not), SAP account (lock or validity), pernr mapped (validity), JCo user (check for lock), ping and test JCo connections
    If none of them are issue, check the logs if there are any trace for this issue. I believe there must be certainly one. That can help u going further.
    Regards,
    Harini S

  • OATS: Error Creating datasource client connection

    Hi All
    When i try to add montiors in the OATS controller machine i am getting the following error .
    Error while creating datasource client connection.
    i am trying to monitor a linux machine. I am able to ping that machine from controller.
    when i tried to do
    plink.exe username@hostname i am getting the following error ...
    FATAL error : Network error : Connection timed out..
    Can anyone please help me on this??
    Thanks

    I'm not sure if this is the same problem but the following thread may help (mentioning the ports that may need opening on your firewalls)...
    Re: What are the various ports used by OLT?
    oracle.port.rmi=4444
    oracle.port.http=8088
    oracle.port.empstart=9001
    oracle.port.uil2=7071
    oracle.port.dataCollector=7073
    oracle.port.webservice=8083
    oracle.port.jndi.rmi=1098
    oracle.port.jndi=1099
    oracle.port.https=8433
    * 9001 (Agent Comunication Port)
    * 1099 (Datacollector Comunication Port)
    * 8088 (for running OpenScript scripts)

  • Can't Create the ODBC connection for Oracle 10g

    Hi,
         I am working with Oracle 10g Database Release 2 in windows XP professional. I am trying to create an ODBC connection for oracle but become failure because its generating the following errors:
    system error code 998
    could not locate the setup or translator library
    Please help me how can I solve this problem and create the ODBC connection for oracle 10g database.
    Best Regards,

    mwz wrote:
    I am trying to create an ODBC connection for oracle but become failure because its generating the following errors:
    system error code 998
    could not locate the setup or translator libraryThe symptom described is typical of an incorrect system env PATH setting (used by the data source admin tool), compared to that of the Oracle Home (specifically, path $OH/bin). The odbc driver config routine will search directories listed in PATH variable for necessary libraries (Client dll's). If some library fails to load (from e.g. oraoci*.dll or oraclient10.dll) it will probably error out, as in your case.
    Are you creating the odbc dsn on the databse server host or on some other machine? I.e. are you using the db host as a client or not?

  • Error: "Couldn't create Crystal Reports Engine for report format version 10.0"

    Post Author: mkubala
    CA Forum: Crystal Reports
    I created several reports in ClearQuest v2003.6.15 using Crystal Reports v10. When a user tries to run these reports from his machine he gets the following error:"Problems executing ReportContact your ClearQuest administrator to verify that a supported version of Crystal Reports has been installed.Couldn't create Crystal Reports Engine for report format version 10.0"My version of CR is compatible with this version of CQ and he shouldn't need CR installed to run the reports so I'm not sure what the issue is?

    Post Author: nschindler
    CA Forum: Crystal Reports
    I have the same problem with ClearQuest 7.0.1.1, except the error contains 'version 11.0' instead of 10.0.This happened when I installed Crystal Reports XI Pro designer.  I followed the procedure to manually uninstall and re-install CR, which allowed me to to author report formats, but I still get this error when trying to view report in the ClearQuest for Windows client.  I tried to re-register all the CR viewer DLLs I could find, but still no luck.Any suggestions?  Thanks,Nate

  • Could not create JCOClientConnection for logical System: WD_MODELDATA_DEST

    Hi ,
    I am getting the below error:
    Could not create JCOClientConnection for logical System: WD_MODELDATA_DEST - Model: class com.eligibilitymodel1.EligibilityModel1. The SSO ticket needed for authentication to WD_MODELDATA_DEST has expired. Close all applications and logon anew!
    Regards
    Anumit

    Anumit,
    when will you get this error?
    if you are getting this while using adaptive rfc model follow this link Could not create JCOClientConnection for logical System:
    if it doesnot work
    try to reimport the certificate or restart the server
    Thanks
    Bala Duvvuri

  • Couldn't create a postscript file for the devnagri script from indesign

    Hi,
    Couldn't create the postscript file for the indesign devnagri script. Its throughing error saying offending fonts.
    I have added a link where u can download the rar file which contains indesign file and required fonts.
    http://wikisend.com/download/278714/Devnagri Script.rar

    @Raghugada – I tested with your new font (no license restriction) and could print to PostScript and distill to PDF without problems. Something else is wrong on your side. Could you provide an IDML file instead of the inDesign file? I will test this as well.
    And: How do you print to PostScript?
    Do you do it with the right PPD? The "Adobe PDF 9.0" ? (PPD => PostScript Printer Description File)
    Do you do it with the right setting in the print dialog of InDesign?
    PostScript Level 3, binary, all fonts fully embedded?
    Here a screenshot of a sample PDF from Acrobat Pro with SHREE-DEV-7-0715 font:
    Uwe

  • BI Publisher creating two database connection for scheduler configurations

    Hi ,
    please tell me how to create two database connection for scheduler configurations in BI Publisher
    ADMIN -> scheduler configurations
    Kind Regards,
    Mohan

    Hi Saichand,
    thank you for your Kind reply !!!!
    Already i configured the scheduler configuration(DB) details for project1.Now i want to configure one more scheduler configuration(DB) for project2.
    i want to maintain two scheduler config details for two DB.
    Kind regards,
    Mohan

Maybe you are looking for