The default robot installation is a 32-bit installation that resides in the X86 programs folder.
When using a 32-bit robot it will use 32-bit ado drivers that is my I suggested testing the 32-bit odbc drivers.
It does not look like you have enabled TLS from the logs provided. I do not see any SSL information:
Sep 02 08:17:47:839 [main, cabi] Resulting parsed connection data is: DatabaseConnectionInfo [databaseName=CA_UIM, databaseServer=XXXXXXXXXXXXXX, dbProvider=SQLNCLI11, nisJdbcUsername=XXXXXXXXXX, nisJdbcPassword={not_shown_for_security_reasons}, nisJdbcUrl=jdbc:sqlserver://;serverName=SHA2016SQLDEV;databaseName=CA_UIM;applicationName=cabi;Network Library=dbmssocn;Language=us_english]
Sep 02 08:17:47:964 [main, cabi]
tlsEnabled: false If you are using TLS 1.2 on the sql server this should be set to yes and you should have followed the instructions for setting up the data_engine with TLS.
https://docops.ca.com/ca-unified-infrastructure-management/9-0-2/en/installing/pre-installation-planning/install-and-configure-your-database-software/microsoft-sql-server/support-for-tls-v1-2-microsoft-sql-serverYou may want to verify with your DBA if you are allowing ONLY TLS 1.2 if so you will need to correct your data_engine setup per the documentation then move back to the CABI.
If you do not then check with your DBA to see if he is seeing the login from the cabi when it starts and provide more details on why the SQL server is failing the login.
------------------------------
Gene Howard
Principal Support Engineer
Broadcom
------------------------------
Original Message:
Sent: 09-04-2019 05:12 AM
From: devi ojha
Subject: Need a third eye on CABI installation
Hello @Gene Howard , @Franklin Ravi D'souza
Thanks a lot for your attention on to this . Below is the details sought for
Is this a domain user or a SQL server user? --- SQL authentication [ details attached ]
IE are you using windows auth or sql Auth? -- SQL
Can you create a 32-bit ODBC connection from the CABI machine to the sql server with this user? -- doesn't it work with 64 bit , i tried connecting to database using SQL manager studio and was able to do that(Screen shot attached )
if this is a windows auth is your robot service starting as this user? We are not using windows Auth
Franklin ,
Can you share corresponding parameter values from your data_engine.cfg
provider = SQLNCLI11
database = CA_UIM
user = svc_uim_dbo_dev
parameters = Network Library=dbmssocn;Language=us_english
also just confirmed with Team regarding version and TLS 1.2
SHA2016SQLDEV is running on "Microsoft SQL Server 2016 (SP2) (KB4052908) - 13.0.5026.0 (X64) "
SQL server 2016 supports TLS 1.2 by default .
Thanks
Devi
Original Message:
Sent: 09-03-2019 09:41 PM
From: Franklin D'souza
Subject: Need a third eye on CABI installation
Hi
Can you share corresponding parameter values from your data_engine.cfg
provider =
database =
user =
parameters =
Also is TLS 1.2 enabled on your SQL 2016 database ?
Original Message:
Sent: 09-03-2019 04:54 AM
From: devi ojha
Subject: Need a third eye on CABI installation
hello Frank,
Thanks a lot for response .
I did try out both the suggestion but its still the same . same set of credentials is working fine to connect database but its just not working with CABi
certificate :
ls D:\Certificate\certificate.pem
roobot.cfg : cryptkey = D:\Certificate\certificate.pem
and 2nd suggestion from KB to alter
ALTER LOGIN <SQL Username> WITH DEFAULT_DATABASE = CA_UIM
GO
still getting the same error
Sep 03 04:47:10:629 [main, cabi] dataEngine is not explicitly specified so will try to locate the same from the hub hierarchy. Sep 03 04:47:10:629 [main, cabi] dataEngine is not explicitly specified so will try to locate the same from the hub hierarchy. Sep 03 04:47:10:926 [main, cabi] In FileUtils.getFileChecksum Sep 03 04:47:10:926 [main, cabi] local certificate store FileChecksum - e690f90a52cc9aa5701d7b7cebf00557 Sep 03 04:47:10:957 [main, cabi] ConnectionString=jdbc:sqlserver://XXXXXXX:1433;databaseName=CA_UIM;Language=us_english;Network Library=dbmssocn;Provider=SQLNCLI11, server=XXXXXXXXXXX, port=1433, username=svc_uim_dbo_dev, password=[not displayed for security reasons], databaseName=CA_UIM, normalizedProviderName=sqlserver Sep 03 04:47:10:957 [main, cabi] stdout: Wallet Type: null Sep 03 04:47:10:973 [main, cabi] checking the config file: [D:\Program Files\Nimsoft\probes\service\cabi\config.zip] [exists: false] Sep 03 04:47:10:973 [main, cabi] begin getLastInstalledUimCabiBundleVersion(config=<not null>) Sep 03 04:47:10:973 [main, cabi] check lastInstalledUimCabiBundleVersion= Sep 03 04:47:10:973 [main, cabi] read from cfg: lastInstalledUimCabiBundleVersion= Sep 03 04:47:10:973 [main, cabi] end getLastInstalledUimCabiBundleVersion(config=<not null>) return lastInstalledUimCabiBundleVersion= Sep 03 04:47:10:973 [main, cabi] begin doesUimCabiBundleNeedsToBeUpgraded(lastVer=, cfgVer=7.1.1-u1) Sep 03 04:47:10:973 [main, cabi] uim.cabi.bundle.version: at-least one out of lastVer= or cfgDdmVer=7.1.1-u1 is null or empty, so setting shdUpgrade=true Sep 03 04:47:10:973 [main, cabi] end doesUimCabiBundleNeedsToBeUpgraded(lastVer=, cfgVer=7.1.1-u1) return shdUpgrade=true Sep 03 04:47:10:973 [main, cabi] changing probe state from 'INITIALIZING' to 'INSTALLING_CABI' Sep 03 04:47:10:973 [main, cabi] deleting the old cabi extracted dir: nimPath=D:\Program Files\Nimsoft, dir=cabi Sep 03 04:47:10:973 [main, cabi] begin deleteDirIfPresent(pathPrefix=D:\Program Files\Nimsoft, dir=c) Sep 03 04:47:10:973 [main, cabi] dirToDel=D:\Program Files\Nimsoft\c Sep 03 04:47:10:973 [main, cabi] deleting directory: D:\Program Files\Nimsoft\c ... Sep 03 04:47:14:692 [main, cabi] ... done with deleting directory: D:\Program Files\Nimsoft\c Sep 03 04:47:14:692 [main, cabi] end deleteDirIfPresent(pathPrefix=D:\Program Files\Nimsoft, dir=c) return isDeleted=true Sep 03 04:47:14:692 [main, cabi] extracting cabi installer ... at com.ca.cabi4uim.Probe.setupCabiInBundledMode(Probe.java:388) at com.ca.cabi4uim.Probe.setupcabi(Probe.java:354) at com.ca.cabi4uim.Probe.initOnTimer(Probe.java:700) at com.nimsoft.nimbus.NimProbe.doForever(NimProbe.java:418) at com.ca.cabi4uim.Probe.run(Probe.java:892) at com.ca.cabi4uim.Probe.main(Probe.java:123) Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Login failed for user 'svc_uim_dbo_dev'. ClientConnectionId:9a51fccf-8be7-4f25-9e20-689439278090 at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:258) at com.microsoft.sqlserver.jdbc.TDSTokenHandler.onEOF(tdsparser.java:256) at com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:108) at com.microsoft.sqlserver.jdbc.SQLServerConnection.sendLogon(SQLServerConnection.java:4290) at com.microsoft.sqlserver.jdbc.SQLServerConnection.logon(SQLServerConnection.java:3157) at com.microsoft.sqlserver.jdbc.SQLServerConnection.access$100(SQLServerConnection.java:82) at com.microsoft.sqlserver.jdbc.SQLServerConnection$LogonCommand.doExecute(SQLServerConnection.java:3121) at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:7151) at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:2478) at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:2026) at com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:1687) at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectInternal(SQLServerConnection.java:1528) at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:866) at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(SQLServerDriver.java:569) at java.sql.DriverManager.getConnection(DriverManager.java:664) at java.sql.DriverManager.getConnection(DriverManager.java:247) at com.nimsoft.nimdbprovider.base.provider.NimDBProviderBase.createConnection(NimDBProviderBase.java:159) ... 12 more Sep 03 04:48:59:363 [main, cabi] setting the lastInstallStatus=4 Sep 03 04:48:59:363 [main, cabi] successfully set the lastInstallStatus=4 Sep 03 04:48:59:363 [main, cabi] srcFilePath=D:\Program Files\Nimsoft\probes\service\cabi\cabi.log, srcFilePath.exists=true, tgtFilePath=D:\Program Files\Nimsoft\probes\service\cabi\cabi_install_archive.log, tgtFilePath.exists=true Sep 3 04:49:00:926 [5252] Controller: Probe 'cabi' (command = <startup java>) returns no-restart code (42)
Original Message:
Sent: 09-02-2019 05:09 PM
From: Franklin D'souza
Subject: Need a third eye on CABI installation
Hi
Have you configured cryptkey on cabi robot
example
cryptkey = c:\Certificate\certificate.pem
https://docops.ca.com/ca-unified-infrastructure-management/9-0-2/en/installing/configure-the-robot-cfg-file
Also please check
https://ca-broadcom.wolkenservicedesk.com/external/article?articleId=47286
Original Message:
Sent: 09-02-2019 08:26 AM
From: devi ojha
Subject: Need a third eye on CABI installation
Hello There ,
I have been trying to install cabi in our setup and have been facing issues since 9.0.1 release . and was expecting it to be fixed with 9.2(UIM) and 4.10(cabi) .
Cabi simply fails to connect microsoft sql database even though it is configured with same credentials as data_engine probe . i did all steps as per the document (link below ) . also took care of Nimbus robot watcher configuration .
https://docops.ca.com/ca-unified-infrastructure-management/8-5/en/installing-ca-uim/install-or-upgrade-ca-business-intelligence-with-ca-uim#InstallorUpgradeCABusinessIntelligencewithCAUIM-FirstTimeCABIServerInstallationonaNewUIMServer
Attached logs from my cabi probe .
Thanks in advance . any pointer will be of great help.
Thanks,
Devi