Open JorritSalverda opened 7 years ago
When running the same command via remote desktop it takes 41 minutes:
$ Get-Date
Wednesday, October 26, 2016 8:04:26 AM
$ cinst visualstudio2015community --version=2015.03.02 --execution-timeout=10800 --yes --accept-license
Chocolatey v0.10.3
Installing the following packages:
visualstudio2015community
By installing you accept licenses for the packages.
VisualStudio2015Community v2015.03.02 [Approved]
visualstudio2015community package files install completed. Performing other installation steps.
System.Collections.Hashtable
Visual Studio will be installed from Web
Install-ChocolateyPackage VisualStudio2015Community exe /Quiet /NoRestart /Log C:\Users\jsalverda\AppData\Local\Temp\cho
colatey\vs.log http://download.microsoft.com/download/0/B/C/0BC321A4-013F-479C-84E6-4A2F90B11269/vs_community.exe -valid
ExitCodes 0 3010 2147781575
WARNING: Url has SSL/TLS available, switching to HTTPS for download
Downloading VisualStudio2015Community
from 'https://download.microsoft.com/download/0/B/C/0BC321A4-013F-479C-84E6-4A2F90B11269/vs_community.exe'
Progress: 100% - Completed download of C:\Users\jsalverda\AppData\Local\Temp\chocolatey\VisualStudio2015Community\2015.0
3.02\vs_community.exe (2.9 MB).
Download of vs_community.exe (2.9 MB) completed.
Hashes match.
Installing VisualStudio2015Community...
VisualStudio2015Community has been installed.
No ISO to dismount
Environment Vars (like PATH) have changed. Close/reopen your shell to
see the changes (or in powershell/cmd.exe just type `refreshenv`).
The install of visualstudio2015community was successful.
Software installed to 'C:\Program Files\Microsoft SQL Server Compact Edition\'
Chocolatey installed 1/1 packages. 0 packages failed.
See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).
$ Get-Date
Wednesday, October 26, 2016 8:45:10 AM
Inspecting the vs.log it seems like it doesn't do anything after the first couple of seconds.
[0F28:0DE0][2016-10-26T08:35:12]i001: Burn v3.7.4029.0, Windows v10.0 (Build 14393: Service Pack 0), path: C:\Users\packeradmin\AppData\Local\Temp\VisualStudio2015Community\2015.03.02\vs_community.exe, cmdline: '/Quiet /NoRestart /Log C:\Users\packeradmin\AppData\Local\Temp\vs.log -burn.unelevated BurnPipe.{853EB3DD-F94C-4E92-95FA-1B437B2CA8EF} {C85253E4-052D-4431-A028-40531C902BCD} 3588'
[0F28:0DE0][2016-10-26T08:35:12]i000: Initializing string variable 'SKUFriendlyName' to value 'VS Community'
...
[0F28:0DE0][2016-10-26T08:35:17]i000: MUX: Scheduling update from http://go.microsoft.com/fwlink/?LinkID=786519&clcid=0x409.
[0F28:0DE0][2016-10-26T08:35:17]i000: MUX: Executing Process: Exe:C:\Users\packeradmin\AppData\Local\Temp\20161026_083517_{4312D170-FE25-36BF-B5E6-0A87C44B7EF0}\vs_community.exe Arguments: /OriginalSource "C:\Users\packeradmin\AppData\Local\Temp\VisualStudio2015Community\2015.03.02\vs_community.exe" /UpdateLaunch /ProductKey "WXN74VRMXHJ8X3HM8F7WCPQB8" /SessionGuid "be43c22a-f8f8-4590-a97a-56f860103fd9" /quiet /norestart
When boxstarter installs MSIs remotely, it runs them in a sheduled task and sets a timeout on the task of one hour. If the task does not complete in an hour, it kills the task. Sounds like you must be hitting this timeout. Unfortunately there is not currently a way to override that however, it sounds to me like there is something fundamentally wrong with the vs install if it is taking this long.
It seems to be related to server 2016. Haven't tested yet with visualstudio2015community, but the following older visual studio package works fine on server 2012 r2 but hangs on server 2016:
cinst VisualStudio2013ExpressWeb --version 12.0.21005.20150920 --ignore-checksums
Perhaps some incompatibility warning or the by default enabled windows defender kicking in. Via remote desktop this works fine, but unfortunately not over winrm. Any tips on how to find the root cause of a hang?
@JorritSalverda It is entirely possible that there are some pre-dependencies like vcredist and other things that don't exist for Server 2016 that the older version of Visual Studio think they require. Do you have any output from the chocolatey.log file output into the $env:ProgramData folder where Chocolatey gets installed? Not sure if that file gets created when Boxstarter uses the DLL or not.
When installing a large Chocolatey package remotely on Windows Server 2016 the execution timeout passed to Chocolatey seems to be overridden by the shorter BoxStarter timeout.
I run the following command with a 3 hour timeout
However the installation fails after an hour with the
Boxstarter: Task has exceeded its total timeout.
error:Is there a BoxStarter specific way to increase the timeout? And could BoxStarter respect the --execution-timeout parameter instead?
By the way, it could be that the installation really hangs. But I think my winrm settings are already tweaked to prevent its limitations being in the way: