- Microsoft Sql Server Native Client 11.0 Protocol Error In Tds Stream
- Microsoft Sql Server Native Client 11.0 Encryption Not Supported On The Client
- Microsoft Sql Server Native Client 11.0 Error 80040e31
Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more informations see SQL Server Books Online. Sqlcmd: Error: Microsoft SQL Server Native Client 10.0: Login timeout expired. Why can't I make it work? I already tried everything.
Microsoft ODBC Driver 11 for SQL Server is a single dynamic-link library (DLL) containing run-time support for applications using native-code APIs to connect to Microsoft SQL Server 2005, 2008, 2008 R2, SQL Server 2012, SQL Server 2014 and Windows Azure SQL Database. Microsoft no longer supports this browser. As a result, some of the functionality on this website may not work for you. For an optimal experience on our website, please consider changing to Microsoft Edge, Firefox, Chrome or Safari.
-->S’applique à :Applies to:
Microsoft SQL ServerSQL Server Native Client 11.0 est installé quand vous installez SQL Server 2016 (13.x)SQL Server 2016 (13.x).Microsoft SQL ServerSQL Server Native Client 11.0 is installed when you install SQL Server 2016 (13.x)SQL Server 2016 (13.x).
Il n’existe aucun SQL Server Native Client 2016.There is no SQL Server 2016 Native Client.Pour plus d’informations, consultez SQL Server Native Client.For more information, see SQL Server Native Client.
Vous pouvez également obtenir sqlncli.msi à partir de la page web de SQL Server 2012 Feature Pack.You can also get sqlncli.msi from the SQL Server 2012 Feature Pack web page.Pour télécharger la version la plus récente du SQL Server Native Client, accédez à Microsoft® SQL Server® 2012 Feature Pack.To download the most recent version of the SQL Server Native Client, go to Microsoft® SQL Server® 2012 Feature Pack.Si une version précédente de SQL ServerSQL Server Native Client antérieure à SQL Server 2012 est également installée sur l’ordinateur, SQL ServerSQL Server native client 11,0 sera installé côte à côte avec la version antérieure.If a previous version of SQL ServerSQL Server Native Client earlier than SQL Server 2012 is also installed on the computer, SQL ServerSQL Server Native Client 11.0 will be installed side-by-side with the earlier version.
Les fichiers SQL ServerSQL Server Native Client (sqlncli11.dll, sqlnclir11.rll et s11ch_sqlncli.chm) sont installés à l'emplacement suivant :The SQL ServerSQL Server Native Client files (sqlncli11.dll, sqlnclir11.rll, and s11ch_sqlncli.chm) are installed to the following location:
%SYSTEMROOT%system32
Notes
Tous les paramètres du Registre appropriés pour le fournisseur OLE DB SQL ServerSQL Server Native Client et le pilote ODBC SQL ServerSQL Server Native Client sont définis dans le cadre de la procédure d'installation.All appropriate registry settings for the SQL ServerSQL Server Native Client OLE DB provider and the SQL ServerSQL Server Native Client ODBC driver are made as part of the installation process.
Les fichiers de bibliothèque et d'en-tête SQL ServerSQL Server Native Client (sqlncli.h et ssqlncli11.lib) sont installés à l'emplacement suivant :The SQL ServerSQL Server Native Client header and library files (sqlncli.h and sqlncli11.lib) are installed in the following location:
%PROGRAMFILES%Microsoft SQL Server110SDK
Outre l'installation de SQL ServerSQL Server Native Client dans le cadre de l'installation de SQL ServerSQL Server, un programme d'installation redistribuable nommé sqlncli.msi se trouve sur le disque d'installation de SQL ServerSQL Server, à l'emplacement suivant : %CD%Setup.In addition to installing SQL ServerSQL Server Native Client as part of the SQL ServerSQL Server installation, there is also a redistributable installation program named sqlncli.msi, which can be found on the SQL ServerSQL Server installation disk in the following location: %CD%Setup.
Vous pouvez distribuer SQL ServerSQL Server Native Client par le biais de sqlncli.msi.You can distribute SQL ServerSQL Server Native Client through sqlncli.msi.Vous pouvez être amené à installer SQL ServerSQL Server Native Client lorsque vous déployez une application.You might have to install SQL ServerSQL Server Native Client when you deploy an application.Une façon d'installer plusieurs packages dans ce qui paraît à l'utilisateur être une installation unique consiste à utiliser la technologie des programmes de chaînage et d'amorçage.One way to install multiple packages in what seems to the user to be a single installation is to use chainer and bootstrapper technology.Pour plus d’informations, consultez Création d’un package de programme d’amorçage personnalisé pour Visual Studio 2005 et Ajout de composants requis personnalisés.For more information, see Authoring a Custom Bootstrapper Package for Visual Studio 2005 and Adding Custom Prerequisites.
Les versions x64 et Itanium de sqlncli.msi installent également la version 32 bits de SQL ServerSQL Server Native Client.The x64 and Itanium versions of sqlncli.msi also install the 32-bit version of SQL ServerSQL Server Native Client.Si votre application vise une plateforme autre que celle sur laquelle elle a été développée, vous pouvez télécharger les versions de sqlncli.msi pour x64, Itanium et x86 à partir du Centre de téléchargement Microsoft.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.
Lorsque vous appelez sqlncli.msi, seuls les composants clients sont installés par défaut.When you invoke sqlncli.msi, only the client components are installed by default.Les composants clients sont des fichiers qui prennent en charge l’exécution d’une application développée à l’aide de SQL ServerSQL Server Native Client.The client components are files that support running an application that was developed using SQL ServerSQL Server Native Client.Pour installer également les composants SDK, spécifiez ADDLOCAL=All dans la ligne de commande.To also install the SDK components, specify ADDLOCAL=All on the command line.Par exemple :For example:
msiexec /i sqlncli.msi ADDLOCAL=ALL APPGUID={0CC618CE-F36A-415E-84B4-FB1BFF6967E1}
Installation sans assistanceSilent Install
Si vous utilisez l'option /passif, /qn, /qb, ou /qr avec msiexec, vous devez également spécifier IACCEPTSQLNCLILICENSETERMS=YES, pour indiquer explicitement que vous acceptez les termes de la licence utilisateur final.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.Cette option doit être spécifiée en majuscules.This option must be specified in all capital letters.
Désinstallation de SQL Server Native ClientUninstalling SQL Server Native Client
Étant donné que les applications telles que SQL ServerSQL Server Server et les SQL ServerSQL Server Outils dépendent de SQL ServerSQL Server Native Client, il est important de ne pas désinstaller SQL ServerSQL Server native client tant que toutes les applications dépendantes ne sont pas désinstallées.Because applications such as SQL ServerSQL Server server and the SQL ServerSQL Server tools depend on SQL ServerSQL Server Native Client, it is important not to uninstall SQL ServerSQL Server Native Client until all dependent applications are uninstalled.Pour les utilisateurs du fournisseur disposant d’un avertissement indiquant que votre application dépend de SQL ServerSQL Server Native Client, utilisez l’option d’installation APPGUID dans votre MSI, comme suit :To provider users with a warning that your application depends on SQL ServerSQL Server Native Client, use the APPGUID install option in your MSI, as follows:
msiexec /i sqlncli.msi APPGUID={0CC618CE-F36A-415E-84B4-FB1BFF6967E1}
La valeur passée à APPGUID est votre code de produit spécifique.The value passed to APPGUID is your specific product code.Un code de produit doit être créé lors de l'utilisation de Microsoft Installer pour regrouper votre programme d'installation d'application.A product code must be created when using Microsoft Installer to bundle your application setup program.
Voir aussiSee Also
Création d’applications avec SQL Server Native ClientBuilding Applications with SQL Server Native Client
Rubriques de procédures relatives à l'installationInstallation How-to Topics
Applies to:
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:
Microsoft Sql Server Native Client 11.0 Protocol Error In Tds Stream
%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:
Microsoft Sql Server Native Client 11.0 Encryption Not Supported On The Client
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.
See Also
Microsoft Sql Server Native Client 11.0 Error 80040e31
Building Applications with SQL Server Native Client
Installation How-to Topics