Introduction
Microsoft have included support for TLS 1.2 in their SQL Server drivers’ updates — https://blogs.msdn.microsoft.com/sqlnativeclient/2018/03/30/released-microsoft-ole-db-driver-for-sql-server/. TLS 1.2 support was not available in BPA Platform 2018 or any previous versions for any SQL Server connection or Microsoft SQL Server Trigger Agent connection.
Resolution
The SQL Server connection procedures for the store and the Microsoft SQL Server Trigger Agent have been amended to include support for TLS 1.2.
If you are using TaskCentre or BPA Platform and you have changed your SQL Server installation to use TLS 1.2, you must apply this hotfix.
Note: This hotfix can only be applied to BPA Platform 2018; if you are running TaskCentre v4.7 or earlier, you must upgrade to BPA Platform 2018 first — go to BPA Platform 2018 Release Notes
Notes
Note: Installation of this patch will cause the BPA Platform services to restart. It should be noted that some services may require a manual restart after the hotfix installation — Go to Control Panel > Administrative Tools > Services and check those services that start with BPA Platform.
Note: If you have installed this hotfix onto a BPA Platform installation that does not make use of the Microsoft SQL Server Trigger Event Agent but you decide to make use of this tool at a later date, you must uninstall this hotfix before installing the Event Agent, then re-install the hotfix.
Note: If using Database Query (ODBC) steps in your tasks, you may find you get an “SSL Security error” after installing this hotfix. This is because the driver you are using (more than likely, the SQL Server driver), does not support TLS 1.2. Change your global configuration connections to use the ODBC Driver 13 for SQL Server driver.
Note: When uninstalling this hotfix, be aware that the SQL Server drivers for that machine may be uninstalled as well. You must download the relevant drivers from Microsoft and re-install them before continuing, else you may encounter an unhandled exception error.
