Upgrading Tentacles from 3.0 to 3.1 fails if the Tentacle is not running as Local System account

Hi,

Some of our tentacles are running as a custom domain user instead of Local System, which results in the following upgrade error. We had to manually remote in, change the tentacle to run as Local System, upgrade, and then change it back. For the tentacles which ran as Local System there were no issues.

Task ID: ServerTasks-4563
Task status: Success
Task queued: 26. september 2015 12:10
Task started: 26. september 2015 12:12
Task duration: 3 minutes

                | == Success: Upgrade Tentacles in ssis-production ==

12:12:58 Info | 1 machines will be upgraded to the latest Tentacle version.
|
| == Success: AALS511 ==
12:13:02 Info | Running Tentacle version 3.0.10.2278
12:13:02 Info | Beginning upgrade
12:13:04 Verbose | Octopus Deploy: Tentacle version 3.0.10.2278
12:13:05 Verbose | Package: H:\Octopus\Work\20150926101301-70\Tentacle.nupkg
12:13:05 Verbose | Destination: H:\Octopus\Upgrade\20150926101258-U97QW
12:13:05 Verbose | 5 files extracted
12:13:15 Info | Waiting for Tentacle to shut down and restart with the new version 3.1.1…
12:13:19 Info | Running Tentacle version 3.0.10.2278
12:13:28 Info | Running Tentacle version 3.0.10.2278
12:13:36 Info | Running Tentacle version 3.0.10.2278
12:13:43 Info | Running Tentacle version 3.0.10.2278
12:13:51 Info | Running Tentacle version 3.0.10.2278
12:13:59 Info | Running Tentacle version 3.0.10.2278
12:14:06 Info | Running Tentacle version 3.0.10.2278
12:14:14 Info | Running Tentacle version 3.0.10.2278
12:14:22 Info | Running Tentacle version 3.0.10.2278
12:14:29 Info | Running Tentacle version 3.0.10.2278
12:14:37 Info | Running Tentacle version 3.0.10.2278
12:14:45 Info | Running Tentacle version 3.0.10.2278
12:14:52 Info | Running Tentacle version 3.0.10.2278
12:15:00 Info | Running Tentacle version 3.0.10.2278
12:15:07 Info | Running Tentacle version 3.0.10.2278
12:15:15 Info | Running Tentacle version 3.0.10.2278
12:15:19 Info | Finishing upgrade
12:15:21 Verbose | Gathering logs from the upgrade
12:15:21 Verbose | H:\Octopus\Upgrade\20150926101258-U97QW\UpgradeLog-20150926101314-c32e0.log
12:15:21 Verbose | Octopus upgrader version 0.0.0.0
12:15:21 Verbose | Current directory: H:\Octopus\Upgrade\20150926101258-U97QW
12:15:21 Verbose | Arguments:
12:15:21 Verbose | [0] = "OctopusDeploy Tentacle"
12:15:21 Verbose | [1] = "H:\Octopus\Upgrade\20150926101258-U97QW\Octopus.Tentacle.msi"
12:15:21 Verbose | [2] = "H:\Octopus\Upgrade\20150926101258-U97QW\Octopus.Tentacle-x64.msi"
12:15:21 Verbose | Upgrade mutex acquired
12:15:21 Verbose | Stopping service: OctopusDeploy Tentacle
12:15:21 Verbose | Stopping service…
12:15:21 Verbose | Waiting for service to stop. Current status: StopPending
12:15:21 Verbose | Waiting for service to stop. Current status: Stopped
12:15:21 Verbose | Service stopped
12:15:21 Verbose | Running MSIEXEC on MSI: H:\Octopus\Upgrade\20150926101258-U97QW\Octopus.Tentacle-x64.msi, output will go to: 33471492-6e97-40ea-b697-6c8ba56b2a17
12:15:21 Verbose | Starting: OctopusDeploy Tentacle
12:15:21 Verbose | Waiting for service to start. Current status: StartPending
12:15:21 Verbose | Waiting for service to start. Current status: Running
12:15:21 Verbose | Service started
12:15:21 Verbose | Error: System.ComponentModel.Win32Exception (0x80004005): Unknown error (0xfffffffe)
12:15:21 Verbose | at System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo)
12:15:21 Verbose | at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
12:15:21 Verbose | at Octopus.Upgrader.SoftwareInstaller.Install(String msiPath) in Y:\work\refs\heads\master\source\Octopus.Upgrader\SoftwareInstaller.cs:line 16
12:15:21 Verbose | at Octopus.Upgrader.Program.Main(String[] args) in Y:\work\refs\heads\master\source\Octopus.Upgrader\Program.cs:line 39
12:15:28 Info | Running Tentacle version 3.0.10.2278
|
| == Success: Summary ==
12:15:29 Info | ONLINE:
12:15:29 Info | - AALS511 at https://aals511:10933/, running version 3.0.10.2278

Hi Thomas,

Thanks for getting in touch and sharing the details of the problem. This is a bug and we have created a github issue to get it fixed. You can follow it’s progress here at the following URL. https://github.com/OctopusDeploy/Issues/issues/2023

I’m happy to see you found a workaround for this in the short term.

Thanks again!

Rob