Geneos - how to solve connectivity issues in Control-M plugin

Prerequisites

Users should review Control-M plugin documentation and Geneos Compatibility Matrix. The Netprobe version needs to be up-to-date and compatible with Java requirements.

Active Console output

The Control-M plugin should return OK at the samplingStatus headline, or otherwise Failed to connect to Control-M server with additional error messages.

We have collected common error message with the solutions.

Error 1

Connection timed out: connect
Connection refused
Connection reset
Remote host closed connection during handshake
Unsupported or unrecognized SSL message
Unrecognised SSL message, plaintext connection

These are generic network errors which indicate that the port configured at the Control-M plugin is down or probably incorrect. Please check that the port is pointing to the correct Control-M Automation API, which should be port 8443 with SSL by default. Users can try using a web browser or "curl" command to verify that the port is accessible.

Error 2

 sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

The target port may be configured with a self-signed SSL certificate. User may check if the certificate has been imported to the Java TrustStore, or try to untick the Verify Server option at the Advanced tab.

Error 3

Login responded with 401

This error means that the user configured at the Control-M plugin is not authorized. We have provided link to Control-M Automation API Session Service below as a reference. Please check the user permissions with your internal Control-M administrators.

Further Reading

• Geneos - Control-M plugin documentation
• Geneos Compatibility Matrix
• Control-M Automation API - Session service (link to BMC documentation)