The latest edition of SSMS updates SMO, which includes the SQL Assessment API. SSMS lets developers and administrators of all skill levels use SQL Server. So I uninstalled SQL Server 2012 Native Client and reinstalled SQL Server 2017 Developer Edition and boom!! – it worked. SQL Server Management Studio (SSMS) is an integrated environment to access, configure, manage, administer, and develop components of SQL Server. I also noticed SQL Server 2016 LocalDB which is installed by Visual Studio – which I made a note to upgrade to version 2017 as this can cause issues with things like the TRANSLATE function that was introduced in SQL Server 2017. So I looked in Programs and Features and lo and behold there was SQL Server Native Client: Huh – I didn’t install that… oh wait – Visual Studio probably did!! Until I remembered that unlike my normal setup I had installed Visual Studio 2019 on the VM first. I (obviously) could not find those as I had not installed it – so I downloaded the native Client off Microsoft’s website and then proceeded to get this error: If a later version is installed – why does the installer want me to install it…?!!Īt which point I wondered what the heck was going on…. Try the installation again using a valid copy of the installation package ‘sqlncli.msi’.Īnd it then asked me to locate the install files for SQL Server 2012 Native Client. MSI Error: 1706 An installation package for the product Microsoft SQL Server 2012 Native Client cannot be found. Halfway through I got an interesting error that (1) I’ve never seen before and (2) did not expect post SQL Server 2014. This install is one I have done over 50 times, if not more. This blog post is about a situation that initially perplexed me – I was installing SQL Server 2017 onto a new DEMO machine – running Windows Server 2019.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |