SQL Server Express 2017 Installation Fails

Question

Hi

I am trying to install SQL Server 2017 Express on my Laptop on which I am an Administrator.

It just fails with:

 Unable to install SQL Server (setup.exe).

Exit code (Decimal): -2068052310Error description: An installation package for the product Microsoft SQL Server 2012 Native Client cannot be found. Try the installation again using a valid copy of the installation package 'sqlncli.msi'.

Then the location of the Log file which is in: C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log

So how do I resolve this???

Looking at my Folders and Apps & Features I seem to have various earlier SQL Server files/Apps installed - From 2012 (11.x), 2014 (12.x) and 2016 (13.x)!

BUT - I think these must have been installed by other Programs/Apps using some SQL Server features as I have not installed SQL Server?!?

Is the error above saying it cannot uninstall (or configure) SQL Server 2012 Native Client? - If so how do I resolve this?

FYI - I have ODBC Drivers "SQL Server" 10.00.19041.01 (SQLSRV32.DLL) and "SQL Server Native Client 11.0" 2011.110.7462.06 (SQLNCLI11.DLL), since I have been accessing remote SQL Servers via ODBC!

So is it the ODBC Driver causing the issue? - I still need ODBC access to a SQL Server (2014?) and to Azure SQL!

Help please as I am stuck and I need to do work with SQL Server Express. Thanks.

Answer 1

Hi @Henry Kafeman ,

As Shashank mentioned, suggest you look at your Programs and Features, uninstall Microsoft SQL Server 2012 Native Client. Then install SQL server 2017 Express again as administrator. Please refer the blog “An installation package for the product Microsoft SQL Server 2012 Native Client cannot be found” – during SQL Server 2017 install.

Microsoft will not be releasing a SQL Server 2014 or later version of the SQL Server Native Client. The SQL Server 2012 Native Client (v11, e.g. sqlncli11.dll), can continue to be utilized by SQL Server 2014 and later versions.

> but will that mean that I need to changed my exisiting ODBC connections to use the newer version of the Driver?

Suggest you using ODBC Drivers 17 for SQL Server, please refer to Microsoft ODBC Driver for SQL Server.

ODBC Drivers "SQL Server" 10.00.19041.01 (SQLSRV32.DLL) is deprecated and has not been enhanced since for many years. It is included with Windows only to support legacy applications and is unaware the new SQL data types and features introduced since the release of SQL 2005. From this old thread Compatibility of ODBC driver SQLSRV32.dll with SQL Server versions.

>Will there be any issues communicating with the SQL Server 2014 with the newer ODBC Driver?

No. Don't worry about that. Go ahead.

Best regards,
Cathy

---

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Looking at my Folders and Apps & Features I seem to have various earlier SQL Server files/Apps installed - From 2012 (11.x), 2014 (12.x) and 2016 (13.x)!

Please go ahead and uninstall SQL Server 2012 native client completely. if you just want to use SQl Server 2017 I would suggest uninstall all SQL Server native clients of SQL Server 2014/2016. But first i suggest to uninstall native client o 2012 and check if the issue resolves.

Please also make sure to uninstall failed sql server 2017 components, restart the machine and try fresh installation.

Answer 3

Shashank-Singh

Thank you, but will that mean that I need to changed my exisiting ODBC connections to use the newer version of the Driver?

Will there be any issues communicating with the SQL Server 2014 with the newer ODBC Driver?

Thanks

Answer 4

Cathy

Many thanks.

I uninstalled "SQL Server Native Client 12", but that required me first to uninstall "SQL Server 2016 Local DB" (which worryingly asked if it could stop and restart VEEAM!) and "SQL Server Data Tools - enu". Then to restart before it successfully installed "SQL Server Express 2017"!

So far all seems to be working okay, but strangely "SQL Server Native Client 12" is back and my ODBC connections that were using the "SQL Server Native Client 11.0" are still working too!

Thanks

Answer 5

Cathy

Can you help with one more thing?

ODBC works okay to SQL Express now BUT only using Windows Authentication. I need Database Authentication!

I have copied a Database from Azure SQL to SQL Express. But the User Logins for the Database are now "SQL user without login"!

I cannot change this or add a new user! - I have tried adding securityadmin to my Windows Login to SQL Express but that did not help.

So I am stuck!

FYI - I have enabled TCP/IP and 127.0.0.1 and strangely, just get this with the correct password using the "ODBC Driver for SQL Server" (version 17.05.0001):
Attempting connection
[Microsoft][ODBC Driver 17 for SQL Server]Shared Memory Provider: No process is on the other end of the pipe.

Though the first time I try with the right or wrong password it gives me:
Attempting connection
[Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Login failed for user '<username>'.

and with the "SQL Server ODBC Driver" (version 10.00.19041):
Attempting connection
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user '<username>'.

Is there some security setting I need to add/change to be able to do what I need?

Thanks