After enabling the TLS 1.2 on the MSSQL Server, the AE can no longer connect to the target database

book

Article ID: 185658

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine CA Automic Workload Automation - Automation Engine

Issue/Introduction

After enabling the TLS 1.2 on the MSSQL Server, the AE can no longer connect to the target database and failing to start with the error message below in the WP log.

U00003545 UCUDB: Opening database ...
U00029112 UCUDB - Length of the DB-History area: 100
U00029108 UCUDB: SQL_ERROR Database handles DB-HENV: 124adc0 DB-HDBC: 124aea0
U00003591 UCUDB - DB error info: OPC: 'SQLDriverConnect' Return code: 'ERROR'
U00003592 UCUDB - Status: '08001' Native error: '18' Msg: 'SSL Security error'
U00003592 UCUDB - Status: '01000' Native error: '1' Msg: 'ConnectionOpen (SECCreateCredentials()).'
U00003590 UCUDB - DB error: 'SQLDriverConnect', 'ERROR ', '01000', 'ConnectionOpen (SECCreateCredentials()).'
U00003524 UCUDB: ===> Time critical DB call! OPC: 'OPEN' time: '15:922.092.123'
U00003611 DB OPEN executed. Return Code = '0000003590'
U00003620 Routine 'UCMAIN_R' forces trace because of error.
U00003449 Output to the TRACE file is finished.

Cause

The ODBC connection that the DSN in the SQLDriverConnect is pointing to not configured to use the TLS 1.2.


SQLDRIVERCONNECT=ODBCVAR=SNNNNNRN,DSN=automic;UID=automic;PWD=automicpwd1

Environment

Release : 12.3

Component : AUTOMATION ENGINE

Application: MSSQL Server, SSL, TLS

Resolution

Please reconfigure the ODBC connection that the DSN in SQLDriverConnect is pointing to so that it is using the TLS v1.2.  A windows or db admin should be able to help with this.

Additional Information

Note: Per Microsoft the DSN that Automic uses should be using ODBC Driver 17

Attachments