Please read our guide for upgrading older versions of Octopus before continuing.
Upgrading Octopus 2.0 involves two major steps.
- Upgrading the Octopus Server.
- Upgrading Tentacles.
Additional information on troubleshooting upgrades is below.
Upgrading the Octopus Server
To upgrade the Octopus Server, you will need to follow these steps:
- Ensure you have a recent database backup that you can restore in case anything goes wrong.
- Download the Octopus Deploy 2.6.5 Installer.
- Run the installer and follow the prompts.
Changing installation paths If you change the Octopus Server installation path (e.g. C:\Program Files\Octopus Deploy\Server) between upgrades, you will need to reconfigure the Windows service after the installer completes. In the Octopus Server Manager, choose the “Reinstall” button to the right of the service status.
When the installer finishes, Octopus Manager will appear. Make sure the Octopus service is running by clicking Start.
Upgrading Tentacles
After upgrading the Octopus Server, browse to the Environments tab in the Octopus Web Portal. You may need to press the “Check health” button to refresh the status of your Tentacles. If any of the Tentacle agents need to be updated, a message will appear:
Click on the Upgrade machines button to have Octopus send the new Tentacle package to all of the machines.
Troubleshooting
When Octopus 2.0 was first released, the MSI was set as a “per user” install. This means that if Joe installed Octopus, Mary would not see the start menu entries.
For Octopus 2.1, we fixed the MSI and made it a “per machine” installation. However, this created one problem: when you install a new version of Octopus, we normally uninstall the old version. But a “per machine” installation cannot automatically uninstall a “per user” MSI.
Instead, we added a check in Octopus 2.1.3 that checks if a per-user installation already exists, and if so, blocks installation. The error message reads:
A previous version of Octopus 2.0 is currently installed. This version cannot be automatically upgraded. You will need to uninstall this version before upgrading. Please view this page for details: https://oc.to/UninstallFirst
Uninstall Octopus 2.0
Your data is safe Uninstalling the old Octopus MSI only removes the program files from disk and stops the Windows Service; your configuration files and the Octopus database will not be touched. When you install the new version, it will continue to work.
When upgrading from one version of Octopus to another we actually perform an uninstall of the old version and then install the new version; the only difference in this case is that due to limitations in Windows Installer/WiX, we can’t easily locate the per-user installation.
You can uninstall the old version of the Octopus Deploy MSI installer and install the new version by locating the entry in Programs and Features in the Windows Control Panel:
After you have uninstalled the old version of Octopus, you can install the new version.
If you are still getting this error
After uninstalling the old version of Octopus and restarting, if you still receive this error, please navigate to the following registry keys:
HKEY_LOCAL_MACHINE\Software\Octopus\OctopusServer
HKEY_LOCAL_MACHINE\Software\Octopus\Tentacle
And delete the InstallLocation value.
Depending on whether you are running the 32-bit registry editor or had previously installed 32-bit versions of Octopus on a 64-bit machine, you should also check:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Octopus\OctopusServer
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Octopus\Tentacle
Quick PowerShell way to do this:
$RegServer = 'HKLM:\Software\Octopus\OctopusServer'
$RegTentacle = 'HKLM:\Software\Octopus\Tentacle'
$RegServer64 = 'HKLM:\SOFTWARE\Wow6432Node\Octopus\OctopusServer'
$RegTentacle64 = 'HKLM:\SOFTWARE\Wow6432Node\Octopus\Tentacle'
$Entries = @($RegServer,$RegTentacle, $RegServer64, $RegTentacle64)
foreach ($reg in $Entries) {
if (Test-Path $reg) { Remove-ItemProperty -Path $reg -Name InstallLocation }
}
Help us continuously improve
Please let us know if you have any feedback about this page.
Page updated on Sunday, January 1, 2023