Enterprise Vault Audit Viewer reports an error when a higher TLS protocol is used while the TLS 1.0 client is disabled on the Enterprise Vault server

book

Article ID: 100049331

calendar_today

Updated On:

Cause

Enterprise Vault Audit Viewer uses ODBC driver to connect to the SQL Server to access data. The existing ODBC driver on the Enterprise Vault setup has limitations working with the higher TLS protocols.

Resolution

A new ODBC driver (version 17.6 and higher) for the SQL server needs to be manually installed on the Enterprise Vault server to support the higher TLS protocols when TLS 1.0 is disabled. Connection to the SQL database using either the old or the new driver can be determined through a registry value. By default, the Audit Viewer continues to connect to the database using the older ODBC driver.

Perform the following steps:

Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.

  1. Install the latest ODBC driver installer which can be downloaded from the location: https://docs.microsoft.com/en-us/sql/connect/odbc/windows/release-notes-odbc-sql-server-windows?view=sql-server-ver15
  2. Create the DWORD registry value:
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\KVS\Enterprise Vault\AuditViewer\UseTLS12SupportedDriver

    To use the older ODBC driver, set the value as 0.
    To use the new driver, set the value as 1 to use the new ODBC driver that supports higher TLS protocol, such as TLS 1.2.

Issue/Introduction

Enterprise Vault Audit Viewer reports a message “Error querying database” when a higher TLS protocol is used and the TLS 1.0 client is disabled on the Enterprise Vault server.