SQL Server 2016 Management Studio – Warning: SSMS install detected shared components on this machine

As soon as SQL Server 2016 Management Studio was released on 1st June 2016, I tried installing it. This is a great way to learn and I love to get going as soon as the new software gets released. I especially get excited when it is related to SQL Server. If you have not known new process to install SQL Server Management Studio, then you should read below the blog.

SQL SERVER – Installing SQL Server Management Studio 2016 – Step by Step

On my machine I already had last RC bits were installed so as soon as I started install, I was welcomed by below error. This was not something I was prepared for.

SQL Server 2016 Management Studio - Warning: SSMS install detected shared components on this machine ssms-setup-01

When I clicked on hyperlink to look at the log file, I found below:

[3B6C:3B54][2016-06-02T05:51:05]i052: Condition ‘(WixBundleInstalled OR NOT(SqlEngineCoreExists_x64) OR NOT(DatabaseEngineVersion_x64 << “13”) OR DatabaseEngineVersion_x64 >= “13.0.1601.5”)’ evaluates to false.

[3B6C:3B54][2016-06-02T05:51:05]i000: MainViewModel.AddFailedCondition: Warning: SSMS install detected shared components on this machine. If the installation continues, applications such as SQL Server may be impacted by an update to the shared components.

I think the message came because I also had SQL Server 2014 installed. Since this is my lab machine, I have clicked on Yes and it installed fine. Here is the final screen.

SQL Server 2016 Management Studio - Warning: SSMS install detected shared components on this machine ssms-setup-02

Have you also installed the latest version of SQL Server 2016 yet? As you can see in this case, the error messages are a great source of understanding what goes on in your system before going to the internet for a solution. In my case, the internet would have not been of help as I was installing on the first day of release and I had to figure out a solution. I love these experiments, but I am sure this is going to help you too.

Reference: Pinal Dave (https://blog.sqlauthority.com)

, ,
Previous Post
SQL SERVER – System Objects Not Visible in SQL Server Management Studio
Next Post
SQL SERVER – Database Mail Breaks with TLS 1.0 Disabled Discovery – Notes from the Field #128

Related Posts

4 Comments. Leave new

  • Marcos Vinicius Fontes
    June 11, 2016 6:35 am

    Hello. I had the same error message, but I had installed SQL Server 2016 RC3 earlier. The solution in my case was to uninstall this preview version of SQL Server and install the latest version – SQL Server 2016 RTM. So, I managed successfully to install SQL Server Management Studio.

    Reply
  • Michael E Alfes
    June 11, 2016 11:42 pm

    Thank you for this posting. One more reason to not hurry up with such tempting *FREE* upgrades.
    For now, I am very happy with SQL Server Server Developer Edition 2014 and Visual Studio 2013 Pro.

    Reply
  • How to fix error 0x80070643 by installing MS SQl Managemnet Studio 2016
    Hello,
    I wanted to instal MS SQL Server 2016 and MS SQL Management Studio 2016.
    First of all I upgraded from Windows 7 to Windows 10.
    I installed MS SQL Sever 2016.
    But by instalation MS SQL Management Studio 2016 I have this error:
    [3288:2A44][2016-10-22T20:10:20]i319: Applied execute package: VSTA2015, result: 0x80070643, restart: None
    [3288:2A44][2016-10-22T20:10:20]e000: Error 0x80070643: Failed to execute EXE package.
    [27F8:376C][2016-10-22T20:10:20]i351: Removing cached package: VSTA2015, from path: C:\ProgramData\Package Cache\5E6157D16EC044A823B2FD2C030ED6DECD2E997E\
    [27F8:376C][2016-10-22T20:10:20]i351: Removing cached package: VSTALS2015, from path: C:\ProgramData\Package Cache\CD0A7331010B0F718B2C483338AE2CDFAADAA35F\
    [27F8:376C][2016-10-22T20:10:20]i351: Removing cached package: VS2015KB3095681Update, from path: C:\ProgramData\Package Cache\02A26E554FBB4232ACD36E70D09F2C7893D399CD\
    [27F8:376C][2016-10-22T20:10:20]i326: Removed dependency: {64e19200-00bf-4a24-92f4-e12b86f6b195} on package provider: {B9EED901-157A-4AB8-BFD1-2C6FBF5CF802}, package sql_common_core_loc_x86

    Thanks for advice.

    Reply

Leave a Reply

Menu