PeopleSoft Agent fails to start with U02000313 and "No subject alternative names matching IP address" error
search cancel

PeopleSoft Agent fails to start with U02000313 and "No subject alternative names matching IP address" error

book

Article ID: 434862

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine CA Automic One Automation

Issue/Introduction

When attempting to start the PeopleSoft agent, the agent fails to establish a connection to the Automation Engine. The agent log contains the following error:

U02000313 communication error with partner '{IP address}/<unresolve>:8443', error: 'No subject alternative names matching IP address {IP Address} found' Initial connection with endpoint not possible. Please check your configuration

Environment

Product: CA Automic Workload Automation - Automation Engine 

Version: 21.0.x and higher

Cause

This error occurs because the agent is configured to connect to the Java Communication Process (JCP) using an IP address, but the SSL certificate loaded by the JCP does not include that IP address in its Subject Alternative Name (SAN) field. Security validation fails because the certificate only recognizes the Fully Qualified Domain Name (FQDN).

Resolution

To resolve this issue, the agent must be updated to use the exact FQDN or hostname that the JCP is using to identify itself in the certificate.

Step 1: Identify the correct JCP FQDN

Before modifying the agent, verify how the JCP is registered in the system:

  1. Access the Automation Engine server and open the most recent JCP log file.
  2. Search for the section that lists the active Automation Engine processes.
  3. Look for the JCP process entries and identify the hostname/FQDN associated with them.

Example JCP log entry:

20260316/144047.894 - 1      AUTOMIC#CP001     JCP * servername.example.com             58015 
20260316/144047.895 - 1      AUTOMIC#CP003     JCP 0 servername.example.com             61068 

In this example, the hostname to use is servername.example.com.

Step 2: Update the Agent Configuration

  1. Log into Client 0 of the Automic Web Interface.
  2. Go to the Administration perspective > Agents.
  3. Right-click the affected PeopleSoft agent and select Reset Agent Public Key.
  4. On the PeopleSoft agent server, navigate to the /bin/security directory and delete all files (this ensures a clean key exchange).
  5. Open the agent.ini file for the PeopleSoft agent.
  6. Locate the connection= parameter in the [TCP/IP] section.
  7. Update the value to match the hostname/FQDN identified in Step 1:
    • Change from: connection={IP Address}:8443
    • Change to: connection=servername.example.com:8443
  8. Save the file and restart the agent.