Find out more ›
Most likely this happens because the ODBC driver, you configured our "TestODBCConnection" custom action to use, cannot properly work when TLS is disabled.Why does the Advanced Installer "testODBCconnection" not work the same on both OS (when TLS is disabled) ?
On the newer operating systems you can configure the connection string (consumed by our "TestODBCConnection" custom action) to use an ODBC driver which works when TLS 1.0 is disabled and newer version of TLS (1.1 and 1.2) is enabled.Is there a change i can make to our installer to be able to complete the test ODBC connection, even if TLS is disabled?
This has been added in Advanced Installer 17.3, released on July 29th, 2020.As a feature request it would be good for Advanced Installer to support a property that contains the latest driver so we don't have to write a custom action to find it ourselves for example
Driver={[MOST_UPTODATE_SQL_DRIVER]};Server=[DATABASE_INSTANCE]; Trusted_Connection=yes; Database=[DATABASE_NAME]