This technical article documents a known issue faced when using the jdbcgtw probe MSSQL provider with a robot running java_jre version 2.09.
The probe will fail to connect to the database. The probe logs display the following errors:
Jan 27 11:17:18:795 [main, jdbcgtw] ****************[ Starting ]****************
Jan 27 11:17:18:795 [main, jdbcgtw] 1.04
Jan 27 11:17:18:795 [main, jdbcgtw] Nimsoft Corp (C) 2007-2010
Jan 27 11:17:18:795 [main, jdbcgtw] port=48011
Jan 27 11:17:18:826 [main, jdbcgtw] Has already a SID
Jan 27 11:17:18:826 [main, jdbcgtw] Login to NimBUS is OK
Jan 27 11:17:33:438 [profile_pool - 44787, jdbcgtw] Unable to create connection - host - <hostname> user - <username>
Jan 27 11:17:33:438 [profile_pool - 44787, jdbcgtw] com.microsoft.sqlserver.jdbc.SQLServerException: The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: No appropriate protocol (protocol is disabled or cipher suites are inappropriate).
com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(Unknown Source)
Jan 27 11:17:33:438 [profile_pool - 44787, jdbcgtw] [UIM] got connection for - url-jdbc:sqlserver://<database_servername>:1433;DatabaseName=<database_instancename> driver -com.microsoft.sqlserver.jdbc.SQLServerDriver
Jan 27 11:17:33:438 [profile_pool - 44787, jdbcgtw] [robotless_status] raise connection alarm
Jan 27 11:17:33:438 [profile_pool - 44787, jdbcgtw] [robotless_status] raise connection alarm - (supp key y+000000000#<profilename>, alarm msg -Profile '<profilename>' failed to connect to database server - <hostname>, severity -2
Jan 27 11:17:33:438 [profile_pool - 44787, jdbcgtw] [robotless_status] create CI for connection error alarm
Jan 27 11:17:33:438 [profile_pool - 44787, jdbcgtw] Remote dev created for hostname '<hostname>', probe 'jdbcgtw'
Jan 27 11:17:33:438 [profile_pool - 44787, jdbcgtw] [robotless_status] created CI for connection error alarm
Jan 27 11:17:33:438 [profile_pool - 44787, jdbcgtw] [robotless_status] raise connection error Alarm
Jan 27 11:17:33:438 [profile_pool - 44787, jdbcgtw] [robotless_status] raised connection error Alarm
Jan 27 11:17:33:438 [profile_pool - 44787, jdbcgtw] sendAlarm NimAlarm closed successfully.
Release : 20.4
Component : UIM JDBCGTW
Attached to this article is a new build of the mssql-jdbc-9.4.1.jre8.jar.
Please follow the below steps:
1. Access the server where the jdbcgtw probe is running.
2. Place the "mssql-jdbc-9.4.1.jre8.jar" into the jdbcgtw_lib folder (Nimsoft\probes\gateway\jdbcgtw\jdbcgtw_lib).
3. Open the jdbcgtw probe in Raw Configure via the IM GUI. Go to providers -> MSSQL -> modify the "path" key:
OLD KEY = ./jdbcgtw_lib/sqljdbc.jar
NEW KEY = ./jdbcgtw_lib/mssql-jdbc-9.4.1.jre8.jar
4. Apply the changes and restart the jdbcgtw probe.
5. Now redeploy the java_jre v2.09 package to the robot hosting the jdbcgtw.
Note: A probe or robot restart might be required if the probe turns red.
6. Retest the connection.
Note: This issue is now resolved as part of probe build: 1.04HF1 - Available on our HF Index Site: Support Content Notification - Support Portal - Broadcom support portal