Error "Exception: Key not available for node" in dSeries Tracelog and Errors.txt

Products

• DSERIES- SERVER
• ESP dSeries Workload Automation - System Agent (dSeries)
• ESP dSeries Workload Automation
• ESP dSeries Workload Automation - Business Agents (dSeries)
• ESP dSeries Workload Automation - Scheduler (dSeries)
• Workload Automation Agent

Issue/Introduction

The tracelog and errors.txt on the dSeries (DE) Manager contain the following error message referencing a specific agent: Exception: Key not available for node

This error indicates that an agent is attempting to contact the dSeries Manager, but the Manager does not recognize the agent because it is missing from the defined Topology.

Environment

ESP dSeries Workload Automation

Cause

The dSeries Manager is receiving communication attempts from an agent host, but there is no corresponding Agent definition in the dSeries Topology. This usually happens after an agent is decommissioned but not reconfigured, or when a new agent is installed but not yet added to the Manager.

Resolution

Depending on whether the agent should be communicating with this Manager, choose one of the following two options:

Option 1: Remove Manager Definition from the Agent

Use this option if the agent should not be talking to this dSeries Manager.

1. Identify the Agent Host: Obtain the IP address or hostname of the agent from the dSeries tracelog.

2. Edit agentparm.txt: Login to the agent host with Administrator or root privileges. Navigate to the agent installation directory and open the agentparm.txt file.

3. Locate and Remove Manager Entries: Find the entries associated with the dSeries Manager (e.g., communication.managerid_1, communication.manageraddress_1). Remove all four parameters for that manager:

   • communication.managerid_n

   • communication.manageraddress_n

   • communication.managerport_n

   • communication.monitorobject_n

4. Maintain Sequential Numbering: If multiple managers are defined, ensure the _n suffix remains sequential (1, 2, 3...). If you remove Manager _2, you must renumber Manager _3 to _2.

5. Restart the Agent

Option 2: Add the Agent to the dSeries Topology

Use this option if the agent is intended to be used by this dSeries Manager.

1. Login to Desktop Client: Use an account with ADMIN privileges.

2. Navigate to Topology: Open the Admin perspective and select the Topology tab.

3. Define New Agent: Right-click the Agents section and select New Agent.

4. Configure: Enter the Agent Name, Address (IP or Hostname), and Port (default is 7500) exactly as configured on the agent side.

5. Save: Once saved, the Manager will recognize the security "key" (node) when the agent next attempts to communicate.

Next Steps: After performing either option, monitor the dSeries tracelog and errors.txt to ensure the "Key not available for node" error has ceased for that specific agent.