Article Content
Article Number | 000035732 |
Applies To | RSA Product Set: RSA Identity Governance & Lifecycle RSA Version/Condition: 7.0.x, 7.1.0, 7.2.0 |
Issue | When exporting metadata in RSA Identity Governance & Lifecycle (Admin > Import/Export > Export), the metadata export fails with: 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):
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 | There 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:
|
Resolution | To 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.
|
Notes | Please 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. |