Cannot start AS400 Agent, receive "an incorrect Company Key" message
search cancel

Cannot start AS400 Agent, receive "an incorrect Company Key" message

book

Article ID: 84545

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

Error Message :
U00003359 Agent 'AS400' uses an incorrect Company Key.

When starting the agent on AS400 the Agent immediately terminates.

The Agent log contains the following messages:

U02000041 Shutdown Agent 'AS400'.
U02000002 Agent 'AS400' version '21.0.4+build.3' ended abnormally.
U02000010 Connection to Server 'UC4#CP001' terminated.


The relevant message is in the CP log:
 

       U00003412 Agent 'AS400' logged on (Client connection='15').
       U00003359 Agent 'AS400' uses an incorrect Company Key.
       U00003407 Client connection '15(9)' from '[TCP.IP.ADD.RES]:[PORT#]' has logged off from the Server.
       U00003397 Agent 'AS400' logged off (client connection='15').

Environment

OS: IBM AS/400

Cause

Cause type: Configuration
Root Cause: The Automation Engine cannot identify the agent properly

Resolution

For Automation Engine v21:

  • Log into client 0 / System Overview / Agents
  • Right-click on the AS400 agent and select: Reset Agent Public Key
  • Verify that the SYSTEM variable in the agent .ini file is correct (the same as on the engine ucsrv.ini)
  •  Start the Agent and check the connection to the Automation Engine (AE).   

For Automation Engine v12.3:

1. Verify that the variable SYSTEM is correctly set in the agent .ini:

(GLOBAL)        
SYSTEM=YOUR_AE_SYSTEM_NAME

2. Change the agent .ini:

(AUTHORIZATION)          
KEYSTORE=[AGENT LIB]/KEYSTORE      <---- use the same library as for UC_EX_PATH_BIN          

 
3. Log into client 0 / System Overview / Agents:

Right-click on the AS400 agent and select:  Renew the transfer key 

       If the agent list doesn’t contain the entry for the specific agent, then create a New Object / Agent / OS400.
       The name for the Agent object should be the same as specified in the .ini.
       After that, the "renew transfer key" agent should be possible.
 
4. Check to see if the agent library contains a KEYSTORE *FILE, and remove it