000035732 - 'Request could not be handled' and 'No enum constant com.aveksa.server.core.DataCollector.Status.InActive' errors exporting metadata from RSA Identity Governance & Lifecycle

Document created by RSA Customer Support Employee on Dec 15, 2017Last modified by RSA Customer Support Employee on Mar 16, 2020
Version 3Show Document
  • View in full screen mode

Article Content

Article Number000035732
Applies ToRSA Product Set: RSA Identity Governance & Lifecycle 
RSA Version/Condition: 7.0.x, 7.1.0, 7.2.0
IssueWhen exporting metadata in RSA Identity Governance & Lifecycle (Admin > Import/Export > Export), the metadata export fails with:
The request could not be handled

User-added image

Older versions of RSA Identity Governance & Lifecycle might manifest as follows:
User-added image

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.
CauseThere is a column in the T_DATA_COLLECTORS table in the AVUSER schema called STATUS which is allowed to have only three values: Active, Inactive, or null. This error occurs when  one or more rows in table T_DATA_COLLECTORS contains an invalid value in the STATUS column (i.e. a value other than Active, Inactive, or null.) These values are case-sensitive. In the example presented in this article, several collector definitions had a value of InActive in the STATUS column. Note the capital A in InActive. This is not a valid value for the STATUS column.

Note the invalid value is part of the error message:

No enum constant com.aveksa.server.core.DataCollector.Status.InActive
ResolutionTo resolve this issue, run a query to detect the invalid values and then contact RSA Identity Governance & Lifecycle Support for assistance with updating those values. Mention this RSA Knowledge Base Article ID 000035732 for reference.
  1. Login as avuser.
  2. Run the below SQL query to detect any invalid values: 

select distinct(status) from t_data_collectors;

  1. 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';
NotesPlease see RSA Knowledge Base Article 000038569 -- 'Request could not be handled' error exporting metadata from RSA Identity Governance & Lifecycle for other causes of this issue.