So I can't reproduce any issues with the new driver on my dev box. I tried simply deleting the driver's ASProtect entry from the Registry, but it just gets recreated and the DLL still fails to load with an 'expired' popup. Is there any way to reset the DBX driver's trial period? I installed a trial version of the driver a LONG time ago, and apparently its expiration is still lingering on my box as I can't use the latest driver version. We really need a DBX driver for SQLServer that works in C++Builder 6 (upgrading is not an option), doesn't crash/hang when used in a Windows service, and can utilize TLS 1.2 (whatever it takes to make that work). Resolution To check if the browser can handle TLS v1.

If not, the browser needs to be upgraded. However, one needs to first test if TLS 1.2 is supported by the current browser or not.

PME2020 supports TLS 1.2 and this feature needs to be enabled. Rolling back to our old driver (dbexpsda.dll 4.25.0.8) works fine, but then we don't get TLS 1.2 even when setting the VendorLib to sqlncli11.dll (which, incidentally, gets loaded anyway when the VendorLib is set to sqloledb.dll instead). Older versions of TLS are becoming obsolete and need to be disabled.

We are having an issue where the latest driver (dbexpsda40.dll 4.80.0.29) sometimes crashes our software when run as a normal desktop app ('Abnormal Program Termination'), and hangs when run as a Windows service (like its waiting for user input, or something).

Rest test test tls 1.2