Unable to register External connector server on vApp

Document ID : KB000112265
Last Modified Date : 03/12/2018
Show Technical Document Details
Introduction:
To provision to a Windows-based endpoint (such as Active Directory, Exchange), you must install CA Connector Server on a Windows server.  To do this you need to follow the steps below:
 
  1. Log in to the Virtual Appliance.
     
  2. Select External Tools by clicking the Hamburger icon available on the upper left corner of the menu bar.
     
  3. Install the Connector Server by following the instructions that are provided under the Remote Connector Server (for Windows OS) section.
    Caution: As part of the installation, do not register the Connector Server with the Provisioning Server.
     
  4. After the installation succeeds, register the remote Connector Server with the Virtual Appliance. 
    In the given box, enter the IP Address or the Hostname of the remote Connector Server and click Add.
Question:
When registering the newly installed external connector server (ccs connector) with the vApp server, it fails to register and displays the following error message in the Web User Interface (webui) screen.

Error fetching list of registered connector servers: Script terminated due to SSH command timeout running command on host

Errors are captured in the logs similar to those below:

ca_vapp_main.log
-----------------------
yyyy MMM DD hh:mm:ss [hostname] ListRegisteredExternalConnectorServers Script started
yyyy MMM DD hh:mm:ss [hostname] ListRegisteredExternalConnectorServers [ERROR] Error fetching list of registered connector servers (error #124)
yyyy MMM DD hh:mm:ss [hostname] ListRegisteredExternalConnectorServers Script terminated due to SSH command timeout running command on host xxx.xxx.xxx.xxx

-----------------------

The JCS logs from the vApp will include errors similar to the one below:
-----------------------
2018-11-21 16:15:09,721 442248226 [ApacheDS Worker-thread-150] (com.ca.jcs.security.login:com.ca.jcs.security.JCSLoginModule:166) INFO - Authentication failed: Bad credentials It indicates that the login credentials on the JCS on that vApp are invalid.
Environment:
CA Identity Manage Suite Virtual Appliance (vAPP) 14.x
Answer:
This issue is can be a result of a couple of issue, either the use of  incorrect credentials to authenticate the Connector Server or the JCS service being blocked or stalled.

In the first instance retry the correct login credentials, however if the JCS service is stalled, simply restart the JCS service on the vApp machine by 'restart_jcs' command.
 
Additional Information:
The password on the JCS service is set at the time of deployment, if the credentials are not known you may need to reinstall the vAPP.