Some of causes are summarized below, and each includes a tests you can perform to verify whether it is your root cause:
Possible Causes and Tests for Failure to Connect Development Studio to a BAO Grid| Incorrect IP/hostname specified in the connection details | Open a browser with the Grid Manager URL on the Studio host. Make sure you can log in and view repository content |
| Incorrect HTTP port specified in the connection details | Open a browser with the Grid Manager URL on the Studio host. Make sure you can log in and view repository content |
| Another application is already using the communications port (by default, 8501 or 8083). This can occur if the CDP and Studio are on the same machine, which is not supported. | Open a command window and use the 'netstat -na' utility to check port conflicts |
| The two hosts are unable to see each other on the network. | Open a browser with the Grid Manager URL on the Studio host. Make sure you can log in and view repository content
OR
Run the command "telnet <IP> <port>" from the Studio host to the Configuration Distribution Peer's (CDP's) IP and port |
| A firewall has blocked the application | Open a browser with the Grid Manager URL on the Studio host. Make sure you can log in and view repository content
OR
Run the command "telnet <IP> <port>" from the Studio host to the Configuration Distribution Peer's (CDP's) IP and port |
| Antivirus software has blocked the application | Temporarily disable antivirus software |
| System clocks between the Studio host and the CDP's host must be synchronized to within 5 sec. | Force the Studio host to the same time zone and time as the Configuration Distribution Peer's (CDP's) host. |
| A web server proxy prevents the proper redirect. | Connect from a machine that does not require the proxy. |
| Another user is accessing the same instance of Studio. | Verify that no other instances of Studio are running on the same machine at the same time. |
| Studio is using incorrect user information | Verify that the account you use to log in with Development Studio is valid |
| Studio is using stale connection information. | Delete the contents of the directories $STUDIO_HOME\server\.jxta\cm\ and $STUDIO_HOME\server\.jxta\ro-pipe-advertisements\ |
In some situations, Development Studio will write more information to the file $STUDIO_HOME\logs\grid.log about the root cause:
Possible Error Messages when Connecting Development Studio to a Grid| SSL peer shut down incorrectly | KA385797 |
| Connection timed out: connect | KA346482 |
| java.io.FileNotFoundException: C:\Program Files\BMC Software\TSO\Studio\server\grids\management\peer.xml (The system cannot find the path specified) | KA365554 |
| Software caused connection abort: recv failed | KA351706 |
| No grid communication discovery URIs are currently configured. It may be possible to repair this by re-connecting or establishing a fresh connection to the environment. | KA346307 |