Error during CDA upgrade 24.4.4 HF2 to 24.4.5: Invalid object name 'Usr' or Access denied.
search cancel

Error during CDA upgrade 24.4.4 HF2 to 24.4.5: Invalid object name 'Usr' or Access denied.

book

Article ID: 453368

calendar_today

Updated On:

Products

Automic Continuous Delivery Automation Automic Automation

Issue/Introduction

This article addresses common errors encountered when upgrading Continuous Delivery Automation (CDA) from 24.4.4 HF2 to 24.4.5, specifically involving "Invalid object name 'Usr'" or "Access denied" during folder synchronization in Release Manager.

  • RamiusUpgradeTool reports "Could not find the object" for users that were previously deleted or renamed in the Automation Engine (AE).
  • Release Manager returns "Invalid object name 'Usr'" in AWI logs when logged into Client 0.
  • "Access denied" error occurs during folder synchronization for active user objects.

Environment

  • Continuous Delivery Automation (CDA) version 24.4.5.

Cause

These issues are attributed to known defects in the Release Manager, including incorrect table prefixing for Client 0 logins and conflicts in user object authorizations within the Automation Engine.

DE209848 and DE210257.

Resolution

  1. "Invalid object name 'Usr'" error: This is a known defect occurring when logged into Client 0. This issue is targeted to be fixed in release 24.4.6 - TBA. To stay updated on the fix status, subscribe to this article (reference: https://knowledge.broadcom.com/external/article/275360).
  2. "Could not find the object" error (Deleted users): If the logs indicate the user no longer exists in the corresponding AE client, delete the leftover record for this user within Release Manager.
  3. "Access denied" error (Active users): To resolve the synchronization failure, perform the following steps:
    1. Log in to the affected client using a CDA admin user.
    2. Navigate to the Administration perspective and open the user experiencing the error.
    3. Remove the specific row in Object Authorization for this user.
    4. Re-configure the folder authorizations and permissions for the user to match your required settings.
    5. Re-run the folder synchronization.

If the issue persists, Contact Support (https://knowledge.broadcom.com/external/article/206567/contact-broadcom-support.html). Scroll to the bottom of the page and click on your respective region.