You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix has been tested by manually adding "TrustServerCertificate=yes" to the connect string with ODBC Driver 18 and confirmed that this connection is made without receiving the error.
By default, HammerDB uses ODBC Driver 17 for SQL Server, when switching to ODBC Driver 18 the following message is received:
The following posts indicate the cause and the fix.
https://stackoverflow.com/questions/71688125/odbc-driver-18-for-sql-serverssl-provider-error1416f086
https://stackoverflow.com/questions/17615260/the-certificate-chain-was-issued-by-an-authority-that-is-not-trusted-when-conn
It looks like encrypt=yes is now default from ODBC 18 whereas previously it was not.
So the enhancement needed for ODBC Driver 18 is to add a Trust Server Certificate option as shown is SSMS
This option will also be in the XML/dict and will add TrustServerCertificate=yes to the connect string.
The text was updated successfully, but these errors were encountered: