U00020590 Host was not found if Agent set dynamically with PUT_ATT LOGIN or Prompset

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

PUT_ATT LOGIN Script function doesn’t work if in ATTRIBUTES tab of Job a login is added where the Host is not mentioned.

Following error message may appear in the logs:

U00020590 Runtime error in object 'OBJNAME', line 'LINENR'. Host 'X' was not found in Login object 'LOGIN.1'.

If a scenario similar to the following one is used problem will show up:

Step 1: Create 2 Login Objects, one for ONE Windows agent, the other with SECOND Windows agent, the Login Objects must not contain both Agents.

Step 2: Create a Windows Job, add Windows Agent ONE and Login Object ONE to the Attributes tab.

Step 2a: In PRE_SCRIPT do a

:PUT_ATT HOST = "SECOND_HOST"
:PUT_ATT LOGIN = "SECOND_LOGIN" (With second Host)

Step 3: run the Job, it will fail with the error U00020590

 

Another example of a non working scenario is the following:

1. A Workflow has a prompset where the Attribute Agent is set
   
2. Inside the Workflow, a Event File inherits the Attribute Agent via the variable from the Prompset
   
3. When launched, the Event File execution fails with FAULT_OTHER - Start impossible. Other error.
   If we click on Details - Message:
   

   U00020590 Runtime error in object 'OBJNAME', line 'LINENR'. Host '' was not found in Login object 'LOGIN_OBJECT_USED'.
   
   

Environment

Release : 21.0.x

Component : AUTOMATION ENGINE

Cause

This is defect in the Automation Engine

Resolution

Workaround:

Remove the name in LOGIN and replace with * or use the previously working version (12.x)

Solution:

Update to a fix version listed below or a newer version if available.

Fix version:
Component(s): Automation Engine
Automation.Engine 21.0.4 HF1 - Available
Automation.Engine 21.0.5 - Available

Additional Information

Solution details: PUT_ATT LOGIN/HOST does not work if in ATTRIBUTES tab of Job already a login is added where the host is not mentioned.