Troubleshooting connection problems

Use the information on this page to troubleshoot connection issues with Development Studio.

Some content is unavailable due to permissions.

Development Studio stuck in a pre-connection state

If the Development Studio disconnects from the CDP and then gets stuck in the pre-connection state when you try to reconnect it, complete the following steps to fix the problem.

  1. Close the Development Studio.
  2. Navigate to the <DEV_STUDIO_HOME>/server/.jms/disco directory (where <DEV_STUDIO_HOME> is the location where you installed the Development Studio).
  3. Delete the files in that directory.
  4. Restart the Development Studio.

Some content is unavailable due to permissions.

Development Studio does not connect if CDP and HACDP peers are running

If CDP and HACDP peers are running, the user is unable to connect to Development Studio and DevStudio gets stuck in log-in state. To complete the connection, do the following:

  1. Keep the CDP peer running and stop the server component peers which are running, such as  HA-CDP and Activity Peer.
  1. Restart the Development Studio connection. For more information, see Starting-TrueSight-Orchestration-Development-Studio.
  2. Connect to the server component peers.

Reconnecting to the peer if the

Some content is unavailable due to permissions.

Development Studio is idle for a long time

If the Development Studio is idle for a long time, when you try to reconnect it, an exception occurs and the following message is displayed:

The attempt to clear the existing grid configuration failed. The existing configuration may have been partially removed. Directories or files which couldn't be removed may need to be manually removed. To resolve the issue, restart the Development Studio. 

Resolution: 

  • Restart the Development Studio. 
    For more information, see Starting-TrueSight-Orchestration-Development-Studio.
  • If you still get the message, do this: 
    1. Close the Development Studio.
    2. Navigate to the <DEV_STUDIO_HOME>/server/grids/<gridName>/library/adapters directory. 
    3. Delete the files in the implementations and staging folders. 
    4. Restart the Development Studio. 

General troubleshooting steps

The troubleshooting steps that follow can help you resolve connections issues between the

Some content is unavailable due to permissions.

Development Studio application and the grid.

  • Verify the host name or IP address.
  • Verify that the authentication service is running.
  • Verify that the CDP service is running.
  • Verify that the computer that is running

    Some content is unavailable due to permissions.

    Development Studio can access the server. For example, ping the server.
  • Ensure that

    Some content is unavailable due to permissions.

    Development Studio and the CDP are running the same version of

    Some content is unavailable due to permissions.

    .
  • Ensure that

    Some content is unavailable due to permissions.

    Development Studio is running on a supported platform.
  • Ensure that clocks on the computer that is running

    Some content is unavailable due to permissions.

    Development Studio and the computer that is running the CDP are in sync. If they are out of sync by several minutes, the connection does not work.
  • Verify that you are using the correct settings for user name, password, peer context, port, and protocol.
    To review the connection settings, open the bao.options file located in the root folder of the CDP. 
  • A connection problem could occur as a result of some file corruption during a

    Some content is unavailable due to permissions.

    Platform or Development Studio upgrade. 
    If Development Studio has connection problems after an upgrade, uninstall Development Studio and reinstall it, pointing to the same workplace used in the previous installation. You should not lose any data (workflows that you developed).

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*