Troubleshooting for CABI JasperReports Server

casp1032
 
 
Service Reports show incorrect down/ up percentage values
 
Symptom:
 
There are incorrect percentages values in the service reports when the 'Date Range' is chosen and when the end period value is the future date/time which is set under the Input Controls option.
Solution
:
The end period value should always be set to a value which is less than or equal to the current date or time. 
Jasper SSO access issue when Single Sign-On is enabled in both Jasper and 
DX NetOps Spectrum
Symptom: 
When Single Sign-On is enabled in Jasper Server and at the same time if you enable the Single Sign-On feature in 
DX NetOps Spectrum
, you may face access issues for Jasper SSO.
Solution:
To enable the Single Sign-On for both Jasper and 
DX NetOps Spectrum
  1. In the 
    DX NetOps Spectrum
     machine, go to $Specroot\tomcat\webapps\spectrum\repmgr\admin folder
  2. Copy the 'spectrum.jks' and 'spectrum.properties' files
  3. In the Jasper machine, go to <<CABusinessIntelligenceINstalledDIR>>\apache-tomcat\webapps\jasperserver-pro\WEB-INF\config folder
  4. Replace the existing 'spectrum.jks' and 'spectrum.properties' files with the copied files from 
    DX NetOps Spectrum
     machine
Jasper report charts are not loading properly (going into processing)
Symptom: 
Jasper report which contains graphs such as pie chart or bar graph does not load and keeps on processing.
Solution:
This issue is caused because of running Ad-Blocker within the Web browser like Firefox or Chrome. We recommended you disable the extension for the JasperReports page, while running the reports to get the charts loaded properly in reports.
Unable to export report data (without Titles, Headers, Group Headers, Summary, Footers) to .csv format
Symptom: 
When I export the report data into CSV format, I want to filter out Title, Header, Group Header, Summary, and Footer information.
Solution:
 
  1. On Jasper Server, navigate to :
    <<CA Business Intelligence Installed Directory>>\apache-tomcat\webapps\jasperserver-pro\WEB-INF\classes.
  2. Open the jasperreports.properties file.
  3. Add the following properties at the end of the file.
    net.sf.jasperreports.export.csv.remove.empty.space.between.rows=true net.sf.jasperreports.export.csv.remove.empty.space.between.columns=true net.sf.jasperreports.export.csv.exclude.origin.band.1=pageHeader net.sf.jasperreports.export.csv.exclude.origin.report.1=* net.sf.jasperreports.export.csv.exclude.origin.band.2=pageFooter net.sf.jasperreports.export.csv.exclude.origin.report.2=* net.sf.jasperreports.export.csv.exclude.origin.band.3=columnHeader net.sf.jasperreports.export.csv.exclude.origin.report.3=* net.sf.jasperreports.export.csv.exclude.origin.band.4=columnFooter net.sf.jasperreports.export.csv.exclude.origin.report.4=* net.sf.jasperreports.export.csv.exclude.origin.band.5=lastPageHeader net.sf.jasperreports.export.csv.exclude.origin.report.5=* net.sf.jasperreports.export.csv.exclude.origin.band.6=summaryPageHeader net.sf.jasperreports.export.csv.exclude.origin.band.7=groupHeader net.sf.jasperreports.export.csv.exclude.origin.band.8=groupFooter net.sf.jasperreports.export.csv.exclude.origin.band.9=reportHeader net.sf.jasperreports.export.csv.exclude.origin.band.10=reportFooter net.sf.jasperreports.export.csv.exclude.origin.band.11=lastPageFooter net.sf.jasperreports.export.csv.exclude.origin.report.11=* net.sf.jasperreports.export.csv.exclude.origin.band.12=summaryPageFooter net.sf.jasperreports.export.csv.exclude.origin.band.13=summary net.sf.jasperreports.export.csv.exclude.origin.report.13=* net.sf.jasperreports.export.csv.exclude.origin.band.14=title net.sf.jasperreports.export.csv.exclude.origin.report.14=* net.sf.jasperreports.export.csv.parameters.override.IgnorePagination=true
  4. Save the changes to the properties file and close.
  5. Restart the Jasper Tomcat Server.
DX NetOps Spectrum
 logo stretches in the Jasper reports that are exported to Excel format 
Symptom:
 While exporting the Jasper reports to Excel format, the 
DX NetOps Spectrum
 logo is stretched.
Solution:
 To prevent the 
DX NetOps Spectrum
 logo from stretching: 
  1. On the Jasper Server Machine
  2. Open the file applicationContext,xml located at <Jasper Install Directory>\CA\SharedComponents\CA Business Intelligence\apache-tomcat\webapps\jasperserver-pro\WEB-INF.
  3. Change the 'ignoreGraphics' property to 'false' and save the file.
  4. Restart the Jasper Tomcat server. 
 
'Install with default components such as Tomcat and Postgres option is grayed out while installing Jasper server
 
Symptom:
 While installing JasperReports Server 6.3 using GUI, the “Install with default components(Tomcat and Postgres….)” option grays out. The user is forced to select “Custom install”.
Solution:
 
  1. Verify the host file entries in the '/etc/hosts' (for non-Windows platforms), %SystemRoot%\System32\drivers\etc\hosts (for Windows). 
  2. Correct the entries and save the file. 
  3. Restart the installation.
For more details, see the 'Host Name / IP Resolution' section in the CABI documentation
JasperReports Server Integration fails
Symptom:
 JasperReports Server integration with 
DX NetOps Spectrum
 fails
Solution:
 To debug the integration fail issue, you must ensure that JasperReports Server parameters are given correctly in Jasper Integration page and also verify that the 'SRM - Core - Report Manager' Module is set to 'ON' in the Debug Controller to collect (To set this value go to OneClick, Administration, Debugging, and Web Module Debug Pages). Verify the OneClick Tomcat log file to identify the error. 
Symptom:
 JasperReports Server integration with 
DX NetOps Spectrum
 fails
Solution:
 If you have installed the CABI jasper reports server that comes with any CA product other than 
DX NetOps Spectrum
, then you must ensure that SpectrumProxy.war file is copied to $TOMCAT\webapps folder and the reportViewerMain.js file is copied to the folder.
JasperReports Server GUI Install screen shows that the product is already installed
Symptom:
 JasperReports Server GUI installation screen shows that the product is already installed
Solution:
 This happens when the uninstaller fails to clean up the registry entries of the jasper server. For windows, check the registry using regedt32 for CABI Jasper server entries. For Linux, check for the file $HOME/.cabijasper file and delete it if found.
A lot of postgres.exe processes even though I only started the server once
Symptom:
 You may see a number of postgres.exe processes running when started Postgres and tomcat of Jasper server (if Postgres is used as a repository of jasper server)
Solution:
 This is normal. PostgreSQL uses a multi-process architecture. In a fresh system with Postgres server, you may see anything from two to five processes. Once clients start to connect, the number of processes increases.
OC users don’t sync in jasper, some newly created users are missing
Symptom:
 Do not see all the 
DX NetOps Spectrum
/OC users in jasper server
Solution:
 You can restart the OneClick server and verify it.
Hibernate errors appear when trying to run reports
Symptom:
 Getting hibernate error messages “Socket Write Error” and “Last Packet Not Finished” and unable to run reports.
Error Message: org.springframework.transaction. CannotCreateTransactionException: Could not open Hibernate Session for transaction; nested exception is org.hibernate. TransactionException: JDBC being failed: Error Message: org.hibernate.TransactionException: JDBC begin failed: OR Error Message: org.springframework.tranaction. CannotCreateTransactionException: Could not open Hibernate Session for transaction; nested exception is java.lang.AssertionError: Last packet not finished Error Message: java.lang.AssertionError: Last packet not finished
Reason: 
The c3p0 hibernation settings are not available
Solution:
  Add the following property key values (which are in bold letters) in the 
hibernateProperties
 in 
<js-app>/jasperserver-pro/WEB-INF/applicationContext.xml 
file and restart the CABI Tomcat to apply these changes. (Refer to the KB article for more information).
<property name="hibernateProperties">
<props>
<prop key="hibernate.dialect">${metadata.hibernate.dialect}</prop>
<prop key="hibernate.show_sql">false</prop>
<prop key="hibernate.generate_statistics">true</prop>
<!--uncomment property below if a default schema should be specified such as for DB2-->
<!--<prop key="hibernate.default_schema">${metadata.hibernate.default_schema}</prop>-->
<!--Cache Configurations-->
<prop key="hibernate.cache.region.factory_class">${hibernate.cache.region.factory_class}</prop>
<prop key="net.sf.ehcache.configurationResourceName">/ehcache_hibernate.xml</prop>
<prop key="hibernate.cache.use_minimal_puts">false</prop>
<prop key="hibernate.cache.use_query_cache">true</prop>
<prop key="hibernate.jdbc.batch_size">20</prop>
<prop key="hibernate.cache.use_second_level_cache">true</prop>
<prop key="hibernate.cache.use_structured_entries">true</prop>
<prop key="hibernate.c3p0.min_size">5</prop>
<prop key="hibernate.c3p0.max_size">200</prop>
<prop key="hibernate.c3p0.timeout">300</prop>
<prop key="hibernate.c3p0.max_statements">500</prop>
<prop key="hibernate.c3p0.idle_test_period">60</prop>
<prop key="hibernate.c3p0.acquire_increment">2</prop>
<prop key="hibernate.c3p0.testConnectionOnCheckin">true</prop>
</props>
</property>
 
 
Printed Jasper reports contain huge space above the header and below the footer
Symptom:
 Noticed huge space above the header and below the footer when printed the PDF report that is exported from Jasper.
Solution:
 To print the reports, you need to export/save the report as PDF and then use the print facility provided by the acrobat reader (do not try to print the report by opening it in the browser). You must select 'Fit To Page' option in the Print dialog and select the page orientation as “Landscape”. If you select 'Fit to Page', the acrobat reader scales the document to fit into a page and places it in the center. If you select 'Custom Scale' option and specify the same scale value - the document is scaled but placed at the page top. Refer to the following screenshot.
  Print Jasper Reports.png  
The JasperReports Server 6.3 login button is grayed out or the content page does not look correct in Internet Explorer 11
Symptom: 
When using IE 11 and Jasper Reports 6.3 either the login button is grayed out or if you are logged in, the page format looks incorrect.
Probable Cause:
This is due to a setting on the Jasper server
Solution/Workaround:
 
Force the Edge mode for Internet Explorer by modifying the following section in the <Tomcat Install Directory>/WEBAPPS/JASPERSERVER-PRO/WEB-INF/decorators/decorator.jsp file on the JasperSoft Server: 
<!--
<meta http-equiv="X-UA-Compatible" content="IE=8"/>
-->
Uncomment this section, and then set content to "IE=Edge" instead of "IE=8".
<meta http-equiv="X-UA-Compatible" content="IE=Edge"/>