We are upgrading Octopus server from Version v2020.1.15 to v2020.5.3. Seems like the upgrade failed as Octopus server is failing to start. When checking the logs we found the below in the log:
2021-01-13 18:17:32.1632 13176 8 FATAL Unhandled AppDomain exception occurred: One of the pre-conditions to safely upgrade your database has failed, and the upgrade cannot continue.
-
PASS: All columns use the default collation.
-
PASS: Your Octopus Server will be compliant with your license after upgrading.
-
PASS: We’ve done our best to remove any unexpected database indexes.
-
FAIL: The version (12.0.6372) of your SQL Server doesn’t satisfy Octopus Server installation requirements. Octopus Server would not start if we allowed the upgrade to continue. Please upgrade your SQL Server to one of the supported versions listed here: https://g.octopushq.com/SQLServerRequirements.
Please take the following steps to get your Octopus Server back up and running:
Step 1: Re-run the installer for the version of Octopus Server you were using just before trying this upgrade. Your data hasn’t been changed and everything will go back to how it was beforehand. This will give you time to solve the problem and try the upgrade again.
Step 2: Contact support@octopus.com with a copy of your Octopus Server log file so we can help you upgrade successfully.
Octopus.Shared.ControlledFailureException: One of the pre-conditions to safely upgrade your database has failed, and the upgrade cannot continue. -
PASS: All columns use the default collation.
-
PASS: Your Octopus Server will be compliant with your license after upgrading.
-
PASS: We’ve done our best to remove any unexpected database indexes.
-
FAIL: The version (12.0.6372) of your SQL Server doesn’t satisfy Octopus Server installation requirements. Octopus Server would not start if we allowed the upgrade to continue. Please upgrade your SQL Server to one of the supported versions listed here: https://g.octopushq.com/SQLServerRequirements.
Please take the following steps to get your Octopus Server back up and running:
Step 1: Re-run the installer for the version of Octopus Server you were using just before trying this upgrade. Your data hasn’t been changed and everything will go back to how it was beforehand. This will give you time to solve the problem and try the upgrade again.
Step 2: Contact support@octopus.com with a copy of your Octopus Server log file so we can help you upgrade successfully.at Octopus.Core.Initialization.DatabaseUpgradeCoordinator.RunPreconditions() in C:\buildAgent\work\f014c79b193351c2\source\Octopus.Core\Initialization\DatabaseUpgradeCoordinator.cs:line 108
at Octopus.Core.Initialization.DatabaseUpgradeCoordinator.Upgrade(CancellationToken cancellationToken) in C:\buildAgent\work\f014c79b193351c2\source\Octopus.Core\Initialization\DatabaseUpgradeCoordinator.cs:line 64
at Octopus.Core.Initialization.DatabaseUpgradeCoordinatorFactory.DisposableDatabaseUpgradeCoordinatorFacade.Upgrade(CancellationToken cancellationToken) in C:\buildAgent\work\f014c79b193351c2\source\Octopus.Core\Initialization\DatabaseUpgradeCoordinatorFactory.cs:line 147
at Octopus.Core.Initialization.BuiltIn.DatabaseUpgradeInitializer.Initialize(IRawRelationalStore store) in C:\buildAgent\work\f014c79b193351c2\source\Octopus.Core\Initialization\BuiltIn\DatabaseUpgradeInitializer.cs:line 20
at Octopus.Core.Initialization.StoreInitializer.Initialize() in C:\buildAgent\work\f014c79b193351c2\source\Octopus.Core\Initialization\StoreInitializer.cs:line 22
at Octopus.Server.OctopusServerEngine.Start() in C:\buildAgent\work\f014c79b193351c2\source\Octopus.Server\OctopusServerEngine.cs:line 82
at Octopus.Server.Commands.RunCommand.Start() in C:\buildAgent\work\f014c79b193351c2\source\Octopus.Server\Commands\RunCommand.cs:line 75
at Octopus.Shared.Startup.AbstractCommand.Start(String[] commandLineArguments, ICommandRuntime commandRuntime, OptionSet commonOptions)
at Octopus.Shared.Startup.OctopusProgram.Start(ICommandRuntime commandRuntime)
at Octopus.Shared.Startup.WindowsServiceHost.<>c__DisplayClass1_0.b__0()
at Octopus.Shared.Startup.WindowsServiceAdapter.RunService()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
— End of stack trace from previous location where exception was thrown —
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
This is a minor upgrade and as per the documents the version v2020.1.15 and v2020.5.3 are compatible with same version of database.
Any insights into why the upgrade failed are greatly appreciated.