Unsupported content This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

Troubleshooting connection problems

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

Development Studio stuck in pre-connection state

If 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 Development Studio.
  2. Navigate to the <DEV_STUDIO_HOME>/server/.jms/disco directory (where <DEV_STUDIO_HOME> is the location where you installed Development Studio).
  3. Delete the files in that directory.
  4. Restart Development Studio.

General troubleshooting steps

The troubleshooting steps that follow can help you resolve connections issues between the BMC Atrium Orchestrator 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 BMC Atrium Orchestrator Development Studio can access the server. For example, ping the server.
  • Ensure that BMC Atrium Orchestrator Development Studio and the CDP are running the same version of BMC Atrium Orchestrator.
  • Ensure that BMC Atrium Orchestrator Development Studio is running on a supported platform.
  • Ensure that clocks on the computer that is running BMC Atrium Orchestrator 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.  See Sample-platform-options-file-templates.
  • A connection problem could occur as a result of some file corruption during a BMC Atrium Orchestrator 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*