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

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

book

Article ID: 422970

calendar_today

Updated On:

Products

Automic SaaS

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 SaaS 24.6 (or above)

Resolution

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