Reputation: 458
I am trying to add integration services to an instance of SQL Server on my machine. When attempting to do so I get the following error:
Some basic googling around has not yielded anything helpful. Does anyone here have any insight?
Upvotes: 3
Views: 921
Reputation: 4095
Check if sqlncli.msi exists in %PROGRAMFILES%\Microsoft SQL Server\100\SDK
. If it does not exist use the subsequent steps to download, uninstall, and re-install it to resolve this error.
The SQL Server Native Client header and library files (sqlncli.h and sqlncli10.lib) are installed in the following location:
%PROGRAMFILES%\Microsoft SQL Server\100\SDK
You can distribute (install) SQL Server Native Client through sqlncli.msi. You might have to install SQL Server Native Client when you deploy an application. One way to install multiple packages in what seems to the user to be a single installation is to use chainer and bootstrapper technology. For more information, see Authoring a Custom Bootstrapper Package for Visual Studio 2005 and Adding Custom Prerequisites.
The x64 and Itanium versions of sqlncli.msi also install the 32-bit version of SQL Server Native Client. If your application targets a platform other than the one it was developed on, you can download versions of sqlncli.msi for x64, Itanium, and x86 from the Microsoft Download Center.
When you invoke sqlncli.msi, only the client components are installed by default. The client components are are files that support running an application that was developed using SQL Server Native Client. To also install the SDK components, specify ADDLOCAL=All on the command line. For example:
msiexec /i sqlncli.msi ADDLOCAL=ALL APPGUID={0CC618CE-F36A-415E-84B4-FB1BFF6967E1}
Steps to take if sqlncli.msi does not exist in the documented path
SQL Server 2012 Native Client
Microsoft® SQL Server® 2012 Native Client - QFE
https://www.microsoft.com/en-us/download/details.aspx?id=50402 and installUpvotes: 2