So now dealing with 9.2.0's cabi 4.10 probe. I had a dedicated robot and deployed the cabi v4.10 probe to the robot. Waited about 30min and cabi probe is red. wasp probe is gray.
cabi probe at log level 5 just says:
Aug 21 11:31:11:863 [1224] Controller: Probe 'cabi' (command = <startup java>) returns no-restart code (42)
Searching community found few different possible solutions.
1. said bump up the memory of the probe's max.
Checked the 4.10's start up section and its only using 256m.
<startup>
<opt>
java_mem_init = -Xms64m
java_mem_max = -Xmx256m
dump_memory = -XX:+HeapDumpOnOutOfMemoryError
</opt>
</startup>
I bumped up the max memory to 4096 and starting to 256 and stop/start and still turns red.
I then added the cryptkey setting to the robot.cfg and stop/start and still no, turns red.
I then deployed java 2.0 to the box stop/start and no, turns red.
Same message:
Aug 21 13:37:23:563 [main, cabi] setting the lastInstallStatus=4
Aug 21 13:37:23:563 [main, cabi] successfully set the lastInstallStatus=4
Aug 21 13:37:23:563 [main, cabi] srcFilePath=C:\Program Files (x86)\Nimsoft\probes\service\cabi\cabi.log, srcFilePath.exists=true, tgtFilePath=C:\Program Files (x86)\Nimsoft\probes\service\cabi\cabi_install_archive.log, tgtFilePath.exists=false
Aug 21 13:37:24:579 [3036] Controller: Probe 'cabi' (command = <startup java>) returns no-restart code (42)
Now I'm deleting both probes fully (cabi and wasp) and running the cabi drop SQL table script. Removing the nimsoft/c directory.
https://docops.ca.com/ca-unified-infrastructure-management/9-0-2/en/installing/ca-business-intelligence-with-ca-uim/installing-and-upgrading-ca-business-intelligence-jasperreports-server-with-ca-uim/install-or-upgrade-for-a-bundled-ca-business-intelligence-jasperreports-server/uninstall-bundled-ca-business-intelligence-jasperreports-server-from-ca-uimOur data_engine is connecting to the SQL DB via a sql user not Windows Authentication so running the Robot service as that user doesn't apply here.
Anyway I did a full clean up by uninstalling the robot on this box. Deleted entire Nimsoft directory and then installed fresh 9.20 robot from the primary hub's installers page. Added the robot.cfg cryptkey entry and then deployed jre v2.00 to the box. Made a entire directory backup and then deployed cabi 4.10 to this box.
Magically this time it worked...
Why is deploying cabi always a 50% chance of it working or not?
Anyway since it's running I'm leaving it alone. good luck..
------------------------------
Daniel Blanco
Enterprise Tools Architect
Alphaserve Technologies
------------------------------