SSMS March 2016 Fails to Install


It’s super frustrating when software fails to install, it’s especially frustrating when the log file doesn’t give you any useful help in figuring out why!

 

I’ve just set up a new VM with SQL Server 2016 RC1 and now need to install SSMS on the same machine.  My Hyper V VM is an offline machine (no net connection) so I need to do the installation manually…. no big deal right?

So I downloaded the SSMS setup file (https://msdn.microsoft.com/en-us/library/mt238290.aspx), copied the file to my VM and proceeded to install.  Happy days!  ~5 minutes later the setup failed.  Ok no problem, I get presented with a link to the output log, let’s check it out and fix what ever is causing the setup to fail…

Here is what the log reported:

………

[07B0:1150][2016-03-27T11:34:55]i000: MainViewModel.OnPackageActionProgress: Percent completed: 1, Overall progress: 6
[07B0:1150][2016-03-27T11:34:55]i000: MainViewModel.OnPackageActionProgress: Percent completed: 1, Overall progress: 6
[07B0:1150][2016-03-27T11:34:55]i000: MainViewModel.OnPackageActionProgress: Percent completed: 1, Overall progress: 6
[07B0:1150][2016-03-27T11:34:55]i000: MainViewModel.OnPackageActionProgress: Percent completed: 1, Overall progress: 6
[07B0:1150][2016-03-27T11:34:55]i000: MainViewModel.OnPackageActionProgress: Percent completed: 0, Overall progress: 6
[07B0:1150][2016-03-27T11:34:55]i000: MainViewModel.OnPackageAction: Install Completed for package Microsoft System CLR Types for SQL Server 2016 RC1
[07B0:1150][2016-03-27T11:34:55]i319: Applied rollback package: SQLSysClrTypes_x64, result: 0x0, restart: None
[10A0:1118][2016-03-27T11:34:55]i329: Removed package dependency provider: {43B232A0-BF88-4546-AA2A-B8FA3D2A726C}, package: SQLSysClrTypes_x64
[10A0:1118][2016-03-27T11:34:55]i351: Removing cached package: SQLSysClrTypes_x64, from path: C:\ProgramData\Package Cache\{43B232A0-BF88-4546-AA2A-B8FA3D2A726C}v13.0.1200.230\
[10A0:1118][2016-03-27T11:34:55]i329: Removed package dependency provider: {65FAE8B2-6351-4B24-8284-B749796179C8}, package: SQLSysClrTypes_x86
[10A0:1118][2016-03-27T11:34:55]i326: Removed dependency: {ef2470b7-8aa2-43fb-b6ff-1ec7c7b5659a} on package provider: {EC2D7589-B567-4D23-8F9E-DF8A8FF3A03C}, package SqlSupport_x86
[10A0:1118][2016-03-27T11:34:55]i329: Removed package dependency provider: {EC2D7589-B567-4D23-8F9E-DF8A8FF3A03C}, package: SqlSupport_x86
[10A0:1118][2016-03-27T11:34:55]i329: Removed package dependency provider: {EDC85D08-5DCC-4FF7-80A1-E9DECC2859CE}, package: SqlSupport_x64
[07B0:1150][2016-03-27T11:34:55]i000: MainViewModel.OnPackageActionProgress: Percent completed: 100, Overall progress: 100
[10A0:1118][2016-03-27T11:34:55]i330: Removed bundle dependency provider: {ef2470b7-8aa2-43fb-b6ff-1ec7c7b5659a}
[10A0:1118][2016-03-27T11:34:55]i352: Removing cached bundle: {ef2470b7-8aa2-43fb-b6ff-1ec7c7b5659a}, from path: C:\ProgramData\Package Cache\{ef2470b7-8aa2-43fb-b6ff-1ec7c7b5659a}\
[07B0:1150][2016-03-27T11:34:55]e000: MainViewModel.OnBundleAction: Bundle action failed
[07B0:1150][2016-03-27T11:34:55]i399: Apply complete, result: 0x800c0005, restart: None, ba requested restart:  No
[07B0:1138][2016-03-27T11:38:14]i000: MainViewModel.OpenUrl: Opening url: C:\Users\ADMINI~1.LOU\AppData\Local\Temp\SsmsSetup\SSMS-Setup-ENU_20160327112148.log

Right – so what part of that is actually useful!  I can see that it appears the installation got to 100%, failed, and didn’t/doesn’t need a restart.  Cheers for that!

 

After reviewing the release notes for SSMS (https://msdn.microsoft.com/en-us/library/mt238486.aspx) it does indeed appear to be a known issue but not 100% obvious.  Here is what the documentation states:

Installing the March Update of SSMS requires an internet connection
The Visual Studio SP1 installer package currently included with SSMS requires an internet connection to retrieve its complete set of components. To install SSMS offline:

  1. Download the Visual Studio 2010 Isolated Shell, and copy the executable to your offline machine.
  2. Next, download the Visual Studio 2010 Service Pack 1 Update, and copy the executable to your offline machine.
  3. Download the SSMS installer, and copy the executable to your offline machine.
  4. Install the Visual Studio 2010 Shell, Visual Studio SP1 Update, and SSMS executable on your offline machine.

 

I already had the VS2010 shell installed but I didn’t have VS2010 SP1 update installed.  After applying this and re-running the SSMS setup the installation succeeded.  Hopefully in future SSMS updates this will be a little more obvious.

Comments (3)

  1. David says:

    This was a good working solution, but took me forever to install all the parts. Thanks!

    1. Dibakar DharChoudhury says:

      This works like a charm, thanks Chris!

  2. marlon says:

    en windows 10 tambien soluciona el problema , muchas gracias

Skip to main content