Error message "The request could not be handled" when attempting to edit a role in the New or Applied state in RSA Identity Governance & Lifecycle
Originally Published: 2017-12-19
Article Number
Applies To
RSA Product/Service Type: Business Role Manager
RSA Version/Condition: 7.0.x
Issue
The request could not be handled
In addition the exception below is logged in the aveksaServer.log file. (/home/oracle/wildfly-10.1.0.Final/standalone/log/aveksaServer.log)
10/03/2017 13:08:02.503 ERROR (default task-127) [com.aveksa.gui.core.MainManager]
org.hibernate.ObjectNotFoundException: No row with the given identifier exists: [com.aveksa.server.core.Entitlement#512511]Cause
Resolution
In this version if you attempt to delete an entitlement associated with a role in any state the message below will be displayed.
Some of the selected entitlements are being sued by roles. Please remove the references to delete these entitlements.
Contact RSA Customer Support and reference this article number for additional information if you are unable to resolve this issue by patching.
Related Articles
Access Fulfillment Express (AFX) does start after applying Patch 11 or higher to RSA Via Lifecycle and Governance 6.9.1 3Number of Views Dashboard not available error message 90Number of Views Business descriptions are applied incorrectly when using a wildcard with an underscore in RSA Identity Governance and Life… 19Number of Views Explanation of GTT_ tables used in RSA Identity Governance & Lifecycle 6Number of Views Roles stuck in Applied state in SecurID Governance & Lifecycle 384Number of Views
Trending Articles
RSA Authentication Manager 8.9 Setup and Configuration Guide How to 'Trust' the RSA Authentication Manager Security Console Self-Signed Root CA certificate and prevent Cert warnings. RSA Authentication Manager 8.9 Release Notes (January 2026) Configure RSA Authentication Manager as a Secure Proxy Server for Cloud Access Service RSA Authentication Manager Upgrade Process
Don't see what you're looking for?