ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Operators Console dashboards/reports failing with NimsoftChartTemplate not found error

book

Article ID: 187267

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

The home page and every built in report that come with DX 9.2.0 Operators Console produces the same error:

Error Message

Chart theme "NimsoftChartTemplate" not found.

Error Trace

net.sf.jasperreports.engine.JRRuntimeException: Chart theme "NimsoftChartTemplate" not found. at net.sf.jasperreports.charts.util.ChartUtil.getTheme(ChartUtil.java:210) at net.sf.jasperreports.engine.fill.JRFillChart.evaluateChart(JRFillChart.java:828) at net.sf.jasperreports.engine.fill.JRFillChart.evaluateRenderer(JRFillChart.java:801) at net.sf.jasperreports.engine.fill.JRFillChart.evaluate(JRFillChart.java:790) at net.sf.jasperreports.engine.fill.JRFillElementContainer.evaluate(JRFillElementContainer.java:383) at net.sf.jasperreports.engine.fill.JRFillFrame.evaluate(JRFillFrame.java:159) at net.sf.jasperreports.engine.fill.JRFillElementContainer.evaluate(JRFillElementContainer.java:383) at net.sf.jasperreports.engine.fill.JRFillBand.evaluate(JRFillBand.java:506) at net.sf.jasperreports.engine.fill.JRVerticalFiller.fillSummaryNoLastFooterSamePage(JRVerticalFiller.java:1183) at net.sf.jasperreports.engine.fill.JRVerticalFiller.fillSummary(JRVerticalFiller.java:1135) at net.sf.jasperreports.engine.fill.JRVerticalFiller.fillReportEnd(JRVerticalFiller.java:271) at net.sf.jasperreports.engine.fill.JRVerticalFiller.fillReport(JRVerticalFiller.java:106) at net.sf.jasperreports.engine.fill.JRBaseFiller.fill(JRBaseFiller.java:607) at net.sf.jasperreports.engine.fill.BaseFillHandle$ReportFill.run(BaseFillHandle.java:123) at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl$SynchronousExecutor.execute(EngineServiceImpl.java:961) at net.sf.jasperreports.engine.fill.BaseFillHandle.startFill(BaseFillHandle.java:169) at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl$AsynchronousReportFiller.fillReport(EngineServiceImpl.java:912) at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl.fillReport(EngineServiceImpl.java:1840) at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl$ReportFill.runWithDataSource(EngineServiceImpl.java:1159) at
com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl$ReportFill.runReport(EngineServiceImpl.java:1088) at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl$ReportRunnable.run(EngineServiceImpl.java:983) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)



After following instructions in the KB186993 : CABI Summary dashboard does not work in Chrome Knowledge Document, the Operator Console home page works, but now the other reports generate errors similar to the following instead:

Error Message

There was an error on the server. Try again or contact site administrators. (Error UID: 6142e8e5-e042-4225-bbfc-c747237dfaf1)

Cause

Problem with one or more of the CABI dashboard or reports packages deployed to the  bundled CABI robot.

Environment

Release : 9.2.0

Component : UIM - CABI 4.10

Resolution

1.  Redeploy the following packages from the local archive on the primary hub to the CABI robot:

uim_core_dashboards_pack v2.44 or later
uim_cabi_health_report_pack v1.31 or later
uim_cabi_vmware_dashboards_pack v1.11 or later
uim_unified_reporter_pack v1.03 or later
uim_cabi_availability_report_pack v1.00 or later
uim_cabi_mcs_dashboards_pack v1.00 or later

2.  Wait about 15 minutes to allow the cabi probe to process the redeployment of these packages.  You will know that they have all been processed when the <installPath>\Nimsoft\probes\service\cabi\content\upload directory is empty on the CABI robot.

3.  Deactivate the Nisoft Robot Watcher Service on the CABI robot.
4.  Delete the following directory and its contents from the CABI robot:

<installPath>\Nimsoft\probes\service\wasp\work

Like the UMP robot, this is a temporary work directory which may have cached some stale data.  When the CABI wasp probe is activated, it will be recreated and repopulated with fresh data.
5.  Start the Nimsoft Robot Watcher Service on the CABI robot.
6.  When the cabi and wasp probes on the CABI robot both have a value in the PID and port columns, restart the UMP robot.
7.  Clear the browser cache from the beginning of time before logging into the UMP portal.

Additional Information

For the cabi_external probe, after executing steps 1 and 2 in the Resolution section, the following steps may need to be executed to fully resolve the issue:

3.  On the external CABI server, stop, then start the CABI service
4.  Restart the cabi_external robot
5.  Restart the UMP robot
6.  Clear the browser cache from the beginning of time before logging into the UMP portal