CABI / CABIJS not installed properly and within OC Data Access Error
search cancel

CABI / CABIJS not installed properly and within OC Data Access Error


Article ID: 206813


Updated On:


DX Unified Infrastructure Management (Nimsoft / UIM)


While cabi  v4.20 probe deployment on installed robot V9.32 on a dedicated server, the probe deployment process stop and cabi became red with the following error in the log "NullPointerException" and wasp folder was not fully extracted by the installation process, as it failed to install cabi.

Then I decided to deployed cabi 4.30, and it was clean upgrade to Jasperserver 7.5 and the cabijs in the wasp also ran. But within OC, in "Reports" section I got a "Data Access Error" message.


Release : 20.3



Solution summary to "Data access error" in "Reports" view"
I deleted the work directory of the OC robot, that means C:\Nimsoft\probes\service\wasp\work
and the work directory of the CABI robot, that means C:\Nimsoft\probes\service\wasp\work.
Assuming there are more than one issue.
The first one was the issue that there were very old DB tables of unified reporter and the CABI installer can't handle this.
After fixing this by deletion of this DB tables and the whole CABI and wasp folders the CABI installer ran in the keystore issue due to access restriction of java keystore located in windows/system/... folder. 
After fixing this by deleting DB tables and CABI and wasp folder and using the CABI installer v4.20 (as suggested in KB article) the CABI installer ran through his process and finished without errors. Then CABI server was installed and works if I use the direct url http://<cabiserver>/cabijs as expected. 
But within OC I got data access errors on Overview and Reports view. After deletion of the C:\Nimsoft\probes\service\wasp\work folder on OC robot, restarting of wasp - OC came up and CABI integration works perfect in Overview and Reports view.