OLE DB Provider SQLNCLI11.1 Is Not Registered

  • I am not sure if there are components I need to install on my local PC or on our server, so I am hoping for some help.

    I have Visual Studio 2019 installed.  For a few years, I have been creating SSIS packages for a Microsoft SQL Server 2016 (SP1) - 13.0.4001.0 (X64).  I had my visual studio set to Target Version 2016 and had no issues.

    We are in the process of moving from this setup to an MSaaS Microsoft SQL Server 2022  - 16.0.4205.1 (X64).  I understand you cannot run SSIS packages on MSaaS, so we installed SSIS on our application server.  I changed my Target Version for the SSIS project to Visual Studio 2019 (there is no 2022 option for me in the dropdown).  When I try to run the package using dtexec.exe, I get the following error:  "The requested OLE DB provider SQLNCLI11.1 is not registered....."

    As such, I am not really sure what needs installed.  Do I need something installed on my PC so the target version can be SQL Server 2022 as well as on the server?

    I am hoping for some help

  • SQLNCLI11.1 is now depreciated, it is advised to switch to MSOLEDBSQL instead.

    https://learn.microsoft.com/en-us/sql/relational-databases/native-client/applications/installing-sql-server-native-client?view=sql-server-ver15

    The old SNAC and new OLEDB can be found in the link above.

  • It is also worth upgrading to the latest copy of VS 2022 and SSIS 2022 projects.

    https://marketplace.visualstudio.com/items?itemName=SSIS.MicrosoftDataToolsIntegrationServices

    The action plan would be to upgrade to VS2022, SSIS2022 projects and swap all your connection managers from SQLNCLI11.1 to MSOLEDBSQL.

    Make sure you take backups of your solutions / dtsx files prior to changing anything so you have copies in case anything goes wrong.

  • Some reason the site didn't like me posting both bits of information together in the same post, had to split them.

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply