After transport load, error U00052002 Object ...with type 'CONN.X' does not exist in client '00200'.

Products

• Automic SaaS
• CA Automic One Automation
• CA Automic Workload Automation - Automation Engine

Issue/Introduction

After a db load of a transport case, an error starts happening whenever a connection object is used.  This happens on all tasks using a connection object in the same client and the client is shown with 5 digits instead of 4:

U00052002 Object 'CONN.CONNECTION_NAME' with type 'CONN does not exist in client '00100'.

The connection object does exist in the client.

Environment

Version: Automic on-prem 24.4 or Automic SaaS 24.6 (or above)

Cause

This was caused by a defect around duplicate PWPs and tracked under DE180577

Resolution

Resolution

This will be fixed for SaaS environments with the release of 26.0.0 and was fixed with 24.4.4 for on-prem environments

Workaround

The WP with role 'S' (WP that checks for Sync objects) must be stopped and another WP take over the role.