000037303 - RSA Archer Package generation fails due to Unknown Component referencing report that was unable to be packaged

Document created by RSA Customer Support Employee on Apr 11, 2019
Version 1Show Document
  • View in full screen mode

Article Content

Article Number000037303
Applies ToRSA Product Set: Archer
RSA Product/Service Type: RSA Archer (On-Premise)
RSA Version/Condition: 6.4.1.1
Issue

Package generation for application(s) fails with the below error.
 



Package Generation Errors



Component Type: Unknown



Object: Vulnerabilities by Severity - Last 30 Days (Business Process)



Object Type: Report



Error Type: Error



Error Message:  The report "Vulnerabilities by Severity - Last 30 Days (Business Process) was unable to be package. The following error has been thrown Object reference not set to an instance of an object.



User-added image

CauseIf:
  • Application A contains a Report Object on the layout
  • Report Object references a report
  • Report references an application B that is not licensed
Then: 

  • Application A cannot be packaged.

Important Note: Many applications can be in this state out of the box. Some examples that may have this issue depending on licensing are below:

In the Applications, Business Processes, and Business Unit applications: 
• Vulnerability Scan Results Severity Trending (30 Days) 
• Vulnerability Scan Results Status Trending (Last 30 Days) 
• Open Vulnerability Scan Results Trending – Last 30 Days 

In the Devices application: 
• Matched Technologies 
• Associated Vulnerability Scan Results 
• Associated Vuln Scan Results by Severity 
• Associated Vulnerability Scan Results by Overall Status 
• VSR Tickets by Overall Status 
• VSR Tickets by Owner 
• Scorecard of Active Vulnerability Definitions by Severity 
• Scorecard of All Vulnerability Definitions by Severity 
• Potential Vulnerabilities 

In the Technologies application: 
• All Active Devices with Defined Technology 
• Devices Scorecard 
• Potential Vulnerability Scorecard Based on Technology Utilization 


 
ResolutionIssue is planned to be addressed in a later release.
Workaround

Remove Report Objects from all layouts that reference reports which reference unlicensed applications.

Workaround #1



  1. Administration -> Application Builder -> Applications -> (application included in package)
  2. Layouts Tab
  3. Open a layout
  4. Designer Tab
  5. Scan through all objects and tabs that are on the layout
  6. (if exists) Report Object -> Edit Report Object Properties
  7. Verify a report is selected in this report object, or remove the report object from the application's layout (if applicable)
  8. Verify the report is not the report referenced in the package installation error message. If it is, remove the report object from the application's layout. (if applicable)
  9. Repeat steps 6 through 8 for all report objects on the layout
  10. Repeat steps 3 through 9 for all layouts in the application
  11. Repeat steps 1 through 10 for all applications included in the package.



Workaround #2



  1. Run the below SQL Query against the Archer instance database to retrieve a listing of all Report Object.

    select mt.module_name, lm.layout_module_name, lot.layout_obj_name, lo.* from tblIVLayoutObject lo with(nolock)
    JOIN tblIVLayoutObjectTranslation lot with(nolock) on lo.layout_obj_id = lot.layout_obj_id
    JOIN tblIVLayoutSection ls with(nolock) on ls.layout_section_id = lo.layout_section_id
    JOIN tblIVLayoutTab lt with(nolock) on lt.layout_tab_id = ls.layout_tab_id
    JOIN tblIVLayoutModule lm with(nolock) on lm.layout_module_id = lt.layout_module_id
    JOIN tblModuleTranslation mt with(nolock)  on mt.module_id = lm.module_id
     where lo.layout_obj_type_id = '8'

  2.  In the module_name column, identify which applications were also included in the package that failed generation.
     
  3. Administration -> Applications -> (Application from Step #2) -> Layouts Tab -> (Layout_module_name from SQL Results) -> Locate (layout_obj_name from SQL Results ) on layout -> Edit Report Object Properties
  4. Verify a report is selected in this report object, or remove the report object from the application's layout (if applicable)
  5. Verify the report is not the report referenced in the package installation error message. If it is, remove the report object from the application's layout. (if applicable)
  6. Repeat 1-5 for all SQL Query results matching applications in the package
     

Attachments

    Outcomes