Troubleshooting Insights (CABI JasperReports)

This article includes information that can help you troubleshoot Insights issues.
casm172
This article includes information that can help you troubleshoot Insights issues.
Cannot Use Fields with Local Attributes (CA SDM) as a Filter or in Cross-Tab
Any fields that contain local attributes (CA SDM) cannot be used as a filter or in a cross-tab.
For example, ‘a
ssignee_combo_name
’ is a local field in "
chg
" object. An Ad-Hoc view can be created using this field in Table format but, the field cannot be used in CrossTab format or as a filter to filter information.
To troubleshoot this issue, construct the local attribute using the direct fields in derived Tables.
For example, '
Assignee Combo Name
' was constructed using '
assignee_first_name
’, ‘a
ssignee_last_name
’ and '
assignee_middle_name
’ direct fields in derived tables.
How can I troubleshoot issues with Datamart installation?
To troubleshoot issues with Datamart installation, review the 
.log
 file that is located in 
<Datamart Installed Directory>\_CA_Datamart_Installation\Logs\CA_Datamart_Install_MM_DD_YYYY_Hours_Minutes_Seconds.log
 folder.
How can I troubleshoot issues with data load failure during ETL?
Follow these steps:
  1. Review the following files and take corrective measures:
    1. config.properties
       file located in 
      <Datamart 
      Installed Directory
      >\config
       folder.
    2. datamart_std.log 
      file located in 
      <Datamart Installed Directory>\logs
       folder.
    3. Jobmetrics.log 
      file located in 
      <Datamart Installed Directory>\logs
       folder
  2. Re-initiate the ETL job.
The integration of xFlow Interface with CABI JasperReports Server fails even after following the integration steps. How can I troubleshoot the issue?
Follow these steps:
  1. Review the 
    install log
     file displayed on the Installation Summary screen of the CASM installer. Take corrective measures, and then select the 
    Retry
     option to proceed with integration.
  2. Verify that the following files are located in 
    <CA Business Intelligence Installation Directory>\apache-tomcat\webapps\jasperserver-pro\WEB-INF\config
     folder:
    • casm_insights.jks
    • casm_insights.properties
  3. Review the 
    jasperserver.log
     file located in 
    <CA Business Intelligence Installation Directory>\apache-tomcat\webapps\jasperserver-pro\WEB-INF\logs
     folder.
  4. Review the
     install log
     file located in 
    %temp%\casm\install.log
     folder.
Why do I encounter the following error message?
‘Could not retrieve the document due to internal server error. Please contact your administrator.' 
Follow these steps:
  1. Review the following file and take corrective measures:
    1. insightsMS.log
       file located in 
      <xFlow Interface Installation Directory>\Apps
       folder
Why do I encounter the following error message when I try to add an Adhoc View to a dashboard?
An unexplained error has occurred and the operation failed.
The error occurs due to a limitation in CA Business Intelligence JasperReports® Server - 6.3.0.
Follow these steps:
  1. Right-click the Ad-Hoc View and select 
    Create Report
     and <save>.
  2. In the Dashboard, drag the report to the dashboard pane.
Aggregate Reports
How do I verify the Status of the ETL Jobs Related to Aggregate (Datamart)?
If you want to verify the status of the jobs which perform the data extract, transform and load (ETL) from CMDB to Aggregate .
CA Service Management
 maintains the log of the jobs which perform the data ETL from CMDB to Aggregate.
Navigate to the server where Aggregate is installed and navigate to <Datamart Installation Folder>\pdi-ce-7.1.0.0-12\data-integration\logs. The folder includes the following log files:
  • jobmetrics.log
    Includes the log entries related to ETL jobs specifying whether each job is run successfully or failed.
  • spoon.log
    Includes the detailed log entries related to the ETL jobs which run from Spoon GUI.
  • output.log
    Includes the detailed log entries related to the ETL jobs which are run from STD-Load.bat using command line interface. The folder includes the latest file named as output.log along with 10 roll-up files. Each roll-up file is named with a incremented number used as suffix to the file name. For example, output.log.1. Each file can have the log data of a maximum 10MB in size.
    The STD-Load.bat file is typically available under the path <Datamart Installation Folder>\bin\ on the Datamart installed server.
Why is the Microsoft SQL Server Enterprise Edition the only supported SQL Server version for Insights Datamart?
CA Service Management
 17.2 Supportability Matrix shows Microsoft SQL Server Enterprise Edition (2012, 2014 and 2016) as the only Microsoft SQL Server version supported/certified with Insights - Aggregate (Datamart). There are some online index operations that the Insight Aggregate jobs depend on (Pentaho API) which the Microsoft SQL Server Standard Edition does not support. Since the online index operations can only be successfully executed with Microsoft SQL Server Enterprise Edition, the SQL Server Enterprise Edition (2012, 2014 and 2016) is the only SQL version supported/certified with Insights Aggregate.
JasperSoft Studio shows a JAVA Heap Space Error
 JasperSoft Studio 6.x shows a JAVA Heap Space error similar to the following:
java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(Unknown Source)
at java.io.ByteArrayOutputStream.write(Unknown Source)
at sun.nio.cs.StreamEncoder.writeBytes(Unknown Source)
at sun.nio.cs.StreamEncoder.implWrite(Unknown Source)
at sun.nio.cs.StreamEncoder.write(Unknown Source)
at sun.nio.cs.StreamEncoder.write(Unknown Source)
at java.io.OutputStreamWriter.write(Unknown Source)
at java.io.Writer.write(Unknown Source)
Perform the following to resolve this issue: 
  1. Increase the JVM Heap Size allocated to Jaspersoft Studio.
  2. On the machine where Jaspersoft Studio is installed, modify the 
    Jaspersoft
     Studio Professional.ini file. 
    This file is located in the root of the JasperStudio install directory (example: C:\Program Files\TIBCO\Jaspersoft Studio Professional-6.2.1.final),
  3. Modify the 
    -Xms
     and 
    -Xmx
     lines to the following (assuming you have enough RAM available):
    -Xms1024m
    -Xmx4096m
  4. If JasperSoft Studio is open when the above changes are made, a restart of JasperSoft Studio is required.
JasperSoft Studio License Expired
After installing Jasper Studio Professional, if the license file is not properly applied, a "License Expired" message might be displayed by the "License Manager" similar to the following: 
JasperStudio_License.png
The out of the box reports provided in Jasper Reports Server for
CA Service Management
 solution does not fulfill customer expectations. Users are required to  develop custom reports in Jasper Studio Professional to import them into the Jasper Reports server. After installing the Jasper Studio, users cannot use it. A "License Expired" message is displayed.
The Jasper Studio license is included in the JasperSoft install media.
  1. Launch Jaspersoft Studio Professional and navigate to Help/License Manager to install the license key.
  2. Click Install new license.
  3. Browse '
    CA_INSTALL\jasperreports.license
    ' file included on the JasperSoft install media.
  4. Click Open to install the license file.
  5. Wait until the message “The new license for Jaspersoft Studio Professional was successfully installed.” displays. 
    Click 
    OK
    .
    You may also need to copy the license to the disk and manually install it. Should use the license file out of the installed directory and not DVD.
    The "License Manager" will be displayed.