Footprints 11.6.XX all versions
For security reasons, TLS 1.0 and TLS 1.1 are now being deprecated, and Footprints needs a TLS1.2 compatible driver.
Footprints 11.6.XX work with an ODBC connector to connect to the Footprints MSSQL database.
The communication is established in the ODBC using a specific driver, and most of the time this is SQL Server Driver which is used.
Problem is that for certain versions of SQL Driver, this is not compatible with anything else than TLS 1.0 or 1.1
If you have disabled TLS 1.0 and 1.1 on the SQL server side, then the ODBC connector on the application server needs to be replaced with one which does take TLS 1.2 in charge.
This is totally possible and you would need to install such a driver on your application server, and then configure a new ODBC connector using this driver.
A suitable SQL DRIVER 13 can be downloaded here : https://www.microsoft.com/en-us/download/details.aspx?id=50420
Now, in case you are planning to upgrade an existing Footprints 11.6.XX to a newer version, we do have a defect... DRZMZ-82
The problem is that :
- We destroy an existing connector which was probably set for good reasons and sometimes with a SPECIFIC driver (TLS 1.2 compatibility for instance)
- We should not destroy a connector which was working previously as a first step, since we cannot proceed with the upgrade after that in case the connection to the database is lost.
In some cases, TLS 1.0 and 1.1 have been deactivated on SQL Server side for security reasons.
Only TLS 1.2 is available, and the only possibility is to build then a ODBC connector using SQL 13 driver for instance.
Problem is that if we destroy the connector and recreate it with SQL Server driver, this is not connecting to the database anymore, and the upgrade process is stopped from the DB point of view.
An error is also visible when testing the ODBC connector we have created, and this states "SQL Server Error : 18".
The only possible workaround so far is to reactivate TLS 1.0 and 1.1 in SQL Server, then perform the upgrade.
Then only once the upgrade is done, you can remove TLS 1.0 and 1.1 from SQL Server and leave TLS 1.2 as active, and finally recreate a new ODBC Connector using SQL Native Driver compatible with TLS 1.2