000030641 - (IMG) RSA Identity Management and Governance, error "The request could not be handled" error when editing imported report.

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000030641
Applies ToRSA Product Set: Identity Management and Governance
RSA Product/Service Type: Appliance
RSA Version/Condition: 6.x, 7.0
Platform: JBoss, All
Platform (Other): null
O/S Version: null
Product Name: RSA-0018012
Product Description: Data Access Governance
Issue

When attempting to edit an imported RSA Identity Management and Governance (IMG) (Aveksa) report the following error is generated and the report cannot be edited. 
"The request could not be handled"
In addition in the Aveksa server.log file shows the following exception: 
06/16/2015 15:40:22.450 ERROR (http-0.0.0.0-8443-2) [com.aveksa.server.report.ReportServiceProvider] FAILED method=getReport subTask=retrieving report by id [658] 
com.aveksa.server.runtime.ServerException: java.lang.NullPointerException
 


CauseThis error can occur if a reported is exported from one system and imported on another, and the report is based on a custom report template.  The issue does not occur if the report is based on one of the default templates.  This error indicates that the report on the target system is unable to locate the template that it was based on.  The error message "retrieving report by id [658] " lists the internal ID of the report template that is missing.  
Currently there is no way to export report templates, so it is not possible to transfer custom report templates from one machine to another.  Reports that are based on custom templates will not function correctly when imported into a different machine. 
ResolutionThe ability to export report templates is being considered for a future version of the product. 
WorkaroundIf you are planning on exporting and importing reports between different machines you should based reports only on the standard report templates and avoid using reports that are based on custom report templates.
For existing reports that are based on custom templates you can dissociate the reports from the templates so that they can be exported and imported without errors.  This can be done by exporting and saving the report using the following method.
  1. On the host system where you where your original report is located. 
  2. Under the "Reports" menu, under "Tabular" select the report that you want to migrate on your host system.
  3. Under the "General" tab of the reports menu select the "Edit" button to edit the report.
  4. In the report editor select the "Export" button to export the report in jrmxl format. 
  5. On the host system where your original report is located.
  6. Under the "Reports" menu, under "Tabular" select the "Create Report" button.
  7. Create a new report in the report editor under a new name. (use a name that reflects that this is the updated report). 
  8. From the report editor menu choose import, and select the report jrmxl file you recently exported.  
  9. The new report will now be dissociated from the template and it will be missing sorting and filter criteria.
  10. Edit this new report to correct the sort order as desired.
  11. Save the report.
  12. Using the Import/Export menu under Admin, export this new report.  This report will be in the xml format.
  13. Import this report into the target system.    
The new report should be dissociated with the template and should now work correctly. 

Attachments

    Outcomes