For existing Workbooks, you will need to apply the appropriate SQL Server Native Client per TLS 1.2 support for Microsoft SQL Server and then change the connection properties by replacing SQLOLEDB.1 with SQLNCLI10 or SQLNCLI11depending on the version of SQL Native Client you installed.A requirement is that you have the SQL Native Client (2008 or 2012) or ODBC drivers with appropriate patches per TLS 1.2 support for Microsoft SQL Server below. Instead use the "From Data Connection Wizard" and select a compliant driver from the list. For all NEW workbooks, do not use that menu option.So, how do you address this? There are several alternatives depending on your situation. You will also receive the same or similar error if you have existing workbooks that use this feature and attempt to refresh those workbooks. You will receive an error similar to the one below. So, if you have SQL Servers that have TLS 1.0 Server disabled, you will no longer be able to use this feature. This provider is an older MDAC/WDAC provider (see Data Access Technologies Road Map below) that comes built into the Operating System (including Windows 10) but DOES NOT support TLS 1.1+. The problem with this feature lies in the fact that this menu option will, by default, leverage SQLOLEDB.1 as the OLE DB provider when connecting to SQL Server.
See the screen print below from Excel 2016. What you may NOT know is that there is a popular feature in Excel to import data from SQL Server. You may also know that Microsoft has provided TLS 1.1/1.2 patches for the SQL Server Database Engine (2008+) as well as the client connectivity components (see TLS 1.2 support for Microsoft SQL Server below). As you may know, TLS 1.0 is being deprecated due to various known exploits and will no longer be PCI compliant as of June 30th, 2018 (see PCI DSS v3.1 and SSL: What you should do NOW below).
0 kommentar(er)
