Space added to Dynamic Property of a Component after deep import/import causes errors when Workflow executed

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

Affects Release version(s): 5;6

Error Message :
U00010015 Activation of RunID '' was aborted by :STOP NOMSG. Additional Information: 'HEADER: STOP WINDOWS RUNBOOK BECAUSE IT'S A AGENT'"

An additional space is added to the dynamic property of a Component within a Workflow after performing a deep import/import within the Application.  This additional space causes the execution of the Workflow to fail and the above errors are displayed.

Investigation

• Create Dynamic Properties where type is Agent Reference (e.g. /Reference). Set value to existing Agent name.
• In the Component Workflow, drag and drop an Action (e.g. Restart Tomcat Server) into the Promptset Tab of the Action, set "Overwirte Agent" with value EXT:\Reference.
• Execute the Workflow.  The first time it will execute successfully.

<Please see attached file for image>

• DeepExport the Application to a zip file.
• Then DeepImport the zip file without any changes.
• Execute the Workflow again.

The action fails with a message from AE:

U00010015 Activation of '[email protected]' RunID '0001018098' was aborted by :STOP NOMSG. Additional Information: 'HEADER: STOP WINDOWS RUNBOOK BECAUSE IT'S A AGENT'"

 

Checking the information generated in the Deployment Context (this can be seen from the History of Execution in ARA), the following text can be seen, "WINDOWS:<space>", before agent name.

<Please see attached file for image>

Environment

Release:
Component: ARLSMG

Cause

Cause type:
Defect
Root Cause: A Workflow fails when executed after deep import/import due to an additional space being added when an Agent Refereced dynamic property is imorted from a template.

Resolution

This field was added on 30/03/2017. This article has not been updated yet. Refer to the "Description" or "Workaround" sections for solution information.

Fix Status: Released

Fix Version(s):
Release Manager 7.0.0 - Available
Release Manager 6.0.2 - Available

Additional Information

Workaround :
N/A