![installation of microsoft sql server native client failed because a higher version installation of microsoft sql server native client failed because a higher version](https://photos1.blogger.com/x/blogger/3402/1340/1600/122307/urlremoval_blogpost1.png)
- #INSTALLATION OF MICROSOFT SQL SERVER NATIVE CLIENT FAILED BECAUSE A HIGHER VERSION HOW TO#
- #INSTALLATION OF MICROSOFT SQL SERVER NATIVE CLIENT FAILED BECAUSE A HIGHER VERSION INSTALL#
The dynamic-link library (DLL) file that contains all of the driver's functionality. The ODBC driver on Windows contains the following components: Component Components of the Microsoft ODBC Driver for SQL Server on Windows msiexec /i msodbcsql.msi APPGUID=" in the connection string. A product code must be created when using Microsoft Installer to bundle your application setup program. To specify a dependency on the driver, set the APPGUID command-line parameter to your product code when silently installing the driver. this indication enables the driver installer to report dependent applications before uninstalling.
#INSTALLATION OF MICROSOFT SQL SERVER NATIVE CLIENT FAILED BECAUSE A HIGHER VERSION INSTALL#
When an application uses the driver, the application should indicate that it depends on the driver through the install option APPGUID. msiexec /quiet /passive /qn /uninstall msodbcsql.msi
#INSTALLATION OF MICROSOFT SQL SERVER NATIVE CLIENT FAILED BECAUSE A HIGHER VERSION HOW TO#
The following example shows how to perform a silent uninstall. msiexec /quiet /passive /qn /i msodbcsql.msi IACCEPTMSODBCSQLLICENSETERMS=YES ADDLOCAL=ALL This option must be specified in all uppercase letters. Specify IACCEPTMSODBCSQLLICENSETERMS=YES to accept the terms of the end-user license if you use the /passive, /qn, /qb, or /qr option to install. To install the SDK components, specify ADDLOCAL=ALL on the command line. The client components are files that support running an application that was developed using the driver. When you invoke msodbcsql.msi, only the client components are installed by default. Major versions of the driver (11, 13, 17) can all be installed side-by-side with each other, as well. The driver can be installed side-by-side with SQL Server Native Client. The driver is installed when you run msodbcsql.msi from one of the Downloads for Windows.įor those who have Driver 17.1.0.1 or below installed, it is recommended that it be uninstalled manually prior to installing the newer version of the Driver. Installing Microsoft ODBC Driver for SQL Server The following matrix indicates driver version support for Windows operating system versions: Operating system → The driver name that you specify in a connection string is ODBC Driver 11 for SQL Server or ODBC Driver 13 for SQL Server (for both 13 and 13.1) or ODBC Driver 17 for SQL Server. But new features in SQL Server releases may not be available with older client drivers. SQL Server releases generally try to maintain backwards compatibility with existing client drivers. SQL version compatibilityĬompatibility indicates that a driver was tested for compatibility against existing releases of SQL at the time of the driver's release. This article discusses the ODBC drivers that connect to SQL Server.