{"id":1405,"date":"2017-05-12T10:37:39","date_gmt":"2017-05-12T09:37:39","guid":{"rendered":"https:\/\/www.threesl.com\/blog\/?p=1405"},"modified":"2017-06-16T10:55:30","modified_gmt":"2017-06-16T09:55:30","slug":"cds-connection-errors","status":"publish","type":"post","link":"https:\/\/www.threesl.com\/blog\/cds-connection-errors\/","title":{"rendered":"How do I fix CDS connection errors?"},"content":{"rendered":"

Diagnosing CDS connection Errors<\/h2>\n

If you receive a CDS connection error when starting a Cradle tool, the following steps will help you diagnose the most common CDS connection errors and show you how to resolve them. These errors are highlighting a communication problem between the client tool (e.g. WorkBench, Document Loader or Document Publisher) and the Cradle Database Server (CDS). There are four main possible causes ;<\/p>\n

\"Error
Can not connect to CDS error dialog<\/figcaption><\/figure>\n

1 – The CDS is not running.<\/h3>\n
    \n
  1. The CDS is on the same machine as the client, (e.g. Single user products or Cytrix installations) . Run Project Manager<\/em><\/a> to see if the CDS is running or look in the process list (Task Manager on Windows, or ps<\/em> Process List on Linux)\u00a0 for\u00a0 crsvr.exe<\/em>.<\/li>\n
  2. The CDS is running on another machine\n
      \n
    1. In the same TCP\/IP subnet (e.g. usual client\/server Enterprise installation) . Start Project Manager<\/em> and look for the CDS.<\/li>\n
    2. Another subnet. Login to that machine and look for it in the process list or contact the administrator of that other machine.<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n

      Solution \u2013 Start the CDS<\/a> on the machine where it is to run,\u00a0 by starting Project Manager<\/em> and starting the CDS. Or at a Linux command prompt<\/p>\n

      c_start start<\/pre>\n
      If the CDS will not start and is not returning any messages then open a command prompt and perform the following dependant on platform<\/p>\n
      Windows<\/p>\n
      Type the following in a command prompt<\/p>\n
      cd %CRADLEHOME%\\bin\\exe\\windows\r\ncrsvr.exe<\/code><\/pre>\n
      Linux<\/p>\n
      Type the following in a command prompt on Linux 32 bit;<\/p>\n
      cd $CRADLEHOME\/bin\/exe\/linux-ia32\/\r\n.\/crsvr<\/code><\/pre>\n
      Type the following in a command prompt on Linux 64 bit;<\/p>\n
      cd $CRADLEHOME\/bin\/exe\/linux-x86_64\/\r\n.\/crsvr<\/code><\/pre>\n
      2 \u2013 CDS is running but the Cradle tool is not communicating with it.<\/h3>\n
      Check the CDS is running on a different PC but your Cradle system is set to standalone.<\/p>\n
      Look for an environment variable<\/a> called CRADLE_STANDALONE<\/strong> and if it exists either delete it or set its value to false<\/em>.<\/p>\n
      Then look in the startup file<\/a> for the variable STANDALONE<\/strong> and ensure that it is set to false<\/em>.<\/p>\n
      3 \u2013 The Cradle tool is trying to communicate with the CDS, but its communications do not reach the CDS.<\/h3>\n
      Check that there is evidence that the Cradle tool\u2019s messages are reaching the CDS. To do this, look at the file cds_access.log on the machine running the CDS. There is one multi-line entry in this file for every connection attempt that the CDS receives. If the Cradle tool\u2019s attempt to connect to the CDS reaches the CDS, it will be in this file. Make a note of the last entry in the file, then close it and attempt\u00a0 to start the Cradle tool. Look at the cds_access.log file again and see if a new entry has appeared at the bottom of it. If not, then the Cradle client\u2019s attempts to connect to the CDS are not being received by the CDS.<\/p>\n
      If the CDS runs on a machine in another TCP\/IP subnet to the PC where the tool is being run, define an environment variable called CRADLE_CDS_HOST<\/strong> whose value is the TCP\/IP address or hostname of the machine running the CDS. Run the tool again and look for an entry appearing at the bottom of the cds_access.log file. If the CDS runs on a machine in the same TCP\/IP subnet to the PC where the tool is being run, look for the CRADLE_CDS_HOST<\/strong> environment variable and check that its contents are correct. You can delete the variable if this CDS is the only CDS running in the subnet.<\/p>\n
      Ensure the correct ports are opened on your firewall, the specific ports can be edited from the ports file<\/a>.<\/p>\n
      4 \u2013 The Cradle tool can communicate with the CDS, but the CDS is ignoring it.<\/h3>\n
      O<\/em>n the machine running the CDS check the cds_hosts<\/a> file. This file has to either be empty ( all clients are allowed to be connected to the CDS) or it contains a list of IP address \/ machine names allowed\/disallowed to connect to the CDS.<\/p>\n