Title:
SES v9.1 SQL ODBC V18 driver Error "Connection failed"
Topic:
This How-To article provides steps to workaround a "Connection failed" error with SQL ODBC V18 using SecureDoc SES Server v9.1
Background
SecureDoc SES Server v9.1 added support for “ODBC Driver 18.0 for SQL Server”. However, the driver introduced breaking change - now it encrypts connection by default and requires valid SQL Server certificate. The SES Console will show an error like this:
Or
Environment (OS/hardware/software):
SES Server v9.1
All Windows Server OS
All Devices
Workaround:
Warning
This article describes making changes a Windows registry setting. Create a BACK UP the registry before starting the following steps.
On the SES Server, Open/Run Registry Editor as Administrator. (Regedit)
Navigate to
[HKEY_CURRENT_USER\Software\WinMagic\SDDB\Database]
Create the following Entry.(New, DWord Value, "Trust"
Enter the value “dword:00000001”
Save this change.
3. Login to the SES Console. Browse to Help --> About
The error should no longer appear, and you will see the ODBC V18 drivers as above.