Symptoms
- Some reports are empty when exported to PDF in ViPR SRM 3.6.x- Not all reports are affected- For those that are affected, XLS and XML exports are fine, only failing for PDF- The affected pdf exports that are generated are empty (but table names, headings, etc. all present)- The same reports behave the same way when scheduled- In the case of the scheduled reports, the accompanying email contains the following error message (as well as the attached empty pdf report):
com.watch4net.apg.v2.gui.report.renderer.RenderingException: com.watch4net.apg.v2.gui.report.ReportRestrictionException: report element count restriction (limit: 50)at com.watch4net.apg.v2.gui.report.renderer.xls.XlsReportRenderer.render(XlsReportRenderer.java:195)at com.watch4net.apg.v2.gui.report.renderer.xls.XlsReportRenderer.render(XlsReportRenderer.java:73)
- Unaffected reports do not have a high row count (note: the above error message refers to an element count restriction)
Cause
There is a bug with ViPR 3.6.x which causes this fault for reports with the following 3 conditions:
- A report contains several nodes (i.e. a branch of parents/children)
- There exists more than one node in the branch where with Report Type = Mixed Reports or Mixed Using Defaults (in any combination)
- Of the above mixed report nodes, there exist 2 or more with the same Display Mode (e.g. Default, One Report Per Line, etc.)
Resolution
This issue was fixed in ViPR SRM version 3.6.3 (EMC M&R Platform 6.5u3)A work around is to ensure that none of the mixed report nodes in a given branch have the same Display Mode. This can be quite a constraint in practice though, and may require much experimentation in redesigning equivalent reports with a different structure.
