'Request could not be handled' and 'No enum constant com.aveksa.server.core.DataCollector.Status.InActive' errors exporting metadata from RSA Identity Governance & Lifecycle
Originally Published: 2017-11-13
Last Modified: 2023-11-30
Article Number
Applies To
RSA Version/Condition: 7.0.x, 7.1.0, 7.2.0
Issue
The request could not be handled
Older versions of RSA Identity Governance & Lifecycle might manifest as follows:
The error is logged to the aveksaServer.log file ($AVEKSA_HOME/wildfly/standalone/log/aveksaServer.log):
Caused by: java.lang.IllegalArgumentException: No enum constant com.aveksa.server.core.DataCollector.Status.InActive at java.lang.Enum.valueOf(Enum.java:238) at com.aveksa.server.core.DataCollector$Status.valueOf(DataCollector.java:91) at com.aveksa.server.core.DataCollector.getBaseDataCollectorVO(DataCollector.java:433) at com.aveksa.server.export.ExportImportModel.addEntitlementDataCollectors(ExportImportModel.java:203) at com.aveksa.server.export.ExportImportModel.getExportableObjects(ExportImportModel.java:170) at com.aveksa.server.export.ExportImportModel.getExportableObjectCount(ExportImportModel.java:276) ... 69 more 03/13/2020 19:13:34.059 ERROR (default task-1) [com.aveksa.gui.pages.admin.metadata.MetadataSummaryPageView] com.aveksa.server.db.PersistenceException: ExportableObjectCount error at com.aveksa.server.export.ExportImportModel.getExportableObjectCount(ExportImportModel.java:280)
Please refer to RSA Knowledge Base Article A000039327 -- Artifacts to gather in RSA Identity Governance & Lifecycle to find the location of the aveksaServer.log file for your specific deployment if you are on a WildFly cluster or a non-WildFly platform. The aveksaServer.log may also be downloaded from the RSA Identity Governance & Lifecycle user interface (Admin > System > Server Nodes tab > under Logs.
Cause
Note the invalid value is part of the error message:
No enum constant com.aveksa.server.core.DataCollector.Status.InActiveResolution
- Login as avuser.
- Run the below SQL query to detect any invalid values:
select distinct(status) from t_data_collectors;
- If any invalid values are returned, run the following query to determine which rows in the table are invalid. This example uses the value InActive:
select * from t_data_collectors where status='InActive';
Notes
Related Articles
RSA Governance & Lifecycle 8.0 Patch 05 Release Notes 59Number of Views Exporting and Importing a rule results with java.lang.NullPointerException in RSA Identity Governance & Lifecycle 59Number of Views Configuring authentication with RADIUS attributes with a NetWare Core Protocol (NCP) server for RSA Authentication Manager… 66Number of Views Generic REST Collector fails with 'com.aveksa.client.genericrest.GenericRestException: UNEVEN_JSON_PATH_CONFIGURATION' in … 282Number of Views Cancelling a change made in a review redirects to a null page or a request could not be handled error in RSA Identity Gove… 33Number of Views
Trending Articles
RSA Authentication Manager 8.9 Patches and Hotfixes Readme RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA-2026-24: RSA Authentication Manager Security Update for Third-Party Component Vulnerabilities IDR SSO - Step 3: Deploy the Identity Router RSA Authentication Manager 8.9 Setup and Configuration Guide
Don't see what you're looking for?