Microsoft Sql Server Native Client Installation Failed
Repair operation can be used in the following scenarios:
Oct 01, 2013 The following procedure describes the minimum options for installing the Microsoft SQL Server Native client. Before you begin, see the Microsoft SQL Server Native client Installation Guide that was provided with the client software for complete instructions and pre-installation requirements.
Repair an instance of SQL Server that is corrupted after it was successfully installed.
Repair an instance of SQL Server if the upgrade operation is cancelled or fails after the instance name is mapped to the newly-upgraded instance.
If you see the following message in the summary log, you can repair the failed upgrade instance:
'SQL Server upgrade failed. To continue, investigate the reason for the failure, correct the problem, and then repair your installation.'
If you see the following message in the summary log, you need to uninstall and reinstall SQL Server. You cannot repair the SQL Server instance.
'SQL Server upgrade failed. To continue, investigate the reason for the failure, correct the problem.'
Microsoft Sql Server Native Client Installation Failed Update
When you repair an instance of SQL Server:
All missing or corrupt files are replaced.
All missing or corrupt registry keys are replaced.
All missing or invalid configuration values are set to default values.
Before you continue, for SQL Server failover clusters, review the following important information:
Repair must be run on individual cluster nodes.
To repair a failover cluster node after a failed Prepare operation, use Remove node and then perform the Prepare step again. For more information, see Add or Remove Nodes in a SQL Server Failover Cluster (Setup).
Repair a failed installation of SQL Server from the Installation Center
Launch the SQL Server Setup program (setup.exe) from SQL Server installation media.
After prerequisites and system verification, the Setup program will display the SQL Server Installation Center page.
Click Maintenance in the left-hand navigation area, and then click Repair to start the repair operation.
Tip
If the Installation Center was launched using the start menu, you will need to provide the location of the installation media at this time.
Setup support rule and file routines will run to ensure that your system has prerequisites installed and that the computer passes Setup validation rules. Click OK or Install to continue.
On the Select Instance page, select the instance to repair, and then click Next to continue.
The repair rules will run to validate the operation. To continue, click Next.
The Ready to Repair page indicates that the operation is ready to proceed. To continue, click Repair.
The Repair Progress page shows the status of the repair operation. The Complete page indicates that the operation is finished.
To repair a failed installation of SQL Server using Command Prompt
Run the following command at a command prompt:
See Also
View and Read SQL Server Setup Log Files
Installation How-to articles
Microsoft SQL Server Native Client 11.0 is installed when you install SQL Server 2016 (13.x).
There is no SQL Server 2016 Native Client. For more information, see SQL Server Native Client.
You can also get sqlncli.msi from the SQL Server 2012 Feature Pack web page. To download the most recent version of the SQL Server Native Client, go to Microsoft速 SQL Server速 2012 Feature Pack. If a previous version of SQL Server Native Client earlier than SQL Server 2012 is also installed on the computer, SQL Server Native Client 11.0 will be installed side-by-side with the earlier version.
The SQL Server Native Client files (sqlncli11.dll, sqlnclir11.rll, and s11ch_sqlncli.chm) are installed to the following location:
%SYSTEMROOT%system32
Note
All appropriate registry settings for the SQL Server Native Client OLE DB provider and the SQL Server Native Client ODBC driver are made as part of the installation process.
The SQL Server Native Client header and library files (sqlncli.h and sqlncli11.lib) are installed in the following location:
%PROGRAMFILES%Microsoft SQL Server110SDK
In addition to installing SQL Server Native Client as part of the SQL Server installation, there is also a redistributable installation program named sqlncli.msi, which can be found on the SQL Server installation disk in the following location: %CD%Setup.
You can distribute 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 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}
Silent Install
If you use the /passive, /qn, /qb, or /qr option with msiexec, you must also specify IACCEPTSQLNCLILICENSETERMS=YES, to explicitly indicate that you accept the terms of the end user license. This option must be specified in all capital letters.
Uninstalling SQL Server Native Client
Because applications such as SQL Server server and the SQL Server tools depend on SQL Server Native Client, it is important not to uninstall SQL Server Native Client until all dependent applications are uninstalled. To provider users with a warning that your application depends on SQL Server Native Client, use the APPGUID install option in your MSI, as follows:
msiexec /i sqlncli.msi APPGUID={0CC618CE-F36A-415E-84B4-FB1BFF6967E1}
The value passed to APPGUID is your specific product code. A product code must be created when using Microsoft Installer to bundle your application setup program.
Gateway w340ua drivers xp. Canada (English) Canada United States Mexico Argentina Brasil Colombia Panama Peru Uruguay. Asia Pacific. Australia China Hong Kong India Indonesia Japan Malaysia New Zealand Philippines Singapore Taiwan Thailand Vietnam. © 2012 All rights reserved. Overview Drivers & Downloads Top Answers Registration Warranty Contact Support Acer Store Recycling Windows 10 Support. Drivers & Downloads. Search by Serial Number or SNID. How do I find my serial number or SNID? Auto-detect my Serial Number. Search by Product Model. Download the latest version of Gateway W340UA drivers according to your computer's operating system.
See Also
Building Applications with SQL Server Native Client
Installation How-to Topics