Unable to install bundeled CABI 4.10 on UIM 9.20, robot 9.20.

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

Install fails, last msg is: 

Sep 10 09:56:27:557 [4580] Controller: Probe 'cabi' (command = <startup java>) returns no-restart code (42) 

Seems problem is, installer unable to find wasp, based on:

sep 10 09:56:24:716 [main, cabi] request failed: (4) not found, Received status (4) on response (for sendRcv) for cmd = 'probe_config_get' name = 'wasp'

sep 10 09:56:24:716 [main, cabi] (4) not found, Received status (4) on response (for sendRcv) for cmd = 'probe_config_get' name = 'wasp'

Wasp is running fine.

Environment

Release : 9.2.0

Component : UIM - CABI 4,10

SQLSERVER 2017 with TLS 1.2

Resolution

Although UIM 9.20 supports SQL 2017 the cabi probe does not. To support SQL with TLS 1.2 you can use SQL Server 2012, 2014, or 2016. SQL however cannot be installed on Windows 2016.

Both the TLS and SQL2017 restriction comes from the jasper reports server that CABI uses. If you need to use windows authentication then you need to ensure you have followed:

https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/unified-infrastructure-management/9-0-2/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.html#concept.dita_c2a97a88c62cb3b239ae19b62fa62638ef4156bf_FirstTimeCABIServerInstallationonaNewUIMServer

locate for "(Microsoft SQL Server Windows Authentication Only) Set up Windows Authentication for CABI" subchapter on the page:

You do need to install the wasp first. If the cryptkey is correctly configured on the robot then the wasp installer will discover the data_engine and configure wasp correctly.

We have detected an issue with the cabi installer where it decrypts the password from the data_engine incorrectly when it contains some special characters. So we would recommend testing without these as we have not yet resolved this.

Please redesign the test environment (if available) to supported OS \ DB combinations, then ensure the cryptkey is correctly defined. Test with a non-complex password and ensure you have configured correctly for windows authentication.