Hi Octopus team,
We’ve recently installed and configured octopus 220.127.116.110 and decided to upgrade to 18.104.22.168.
To get into more detail:
The initial upgrade of octopus lead to a situation where we could only use a local system or a SA account to connect to the SQL database. This was not desired due to the use of domain accounts. After troubleshooting we stumbled upon http://help.octopusdeploy.com/discussions/problems/36573-installation-issues-with-30-permissions where was an interesting option that was not shown during the installation: local or service account selection.
We figured that the previous installation might have been a local one due to the raven DB, so we uninstalled the software and performed a clean install. and the option showed.
After the second installation, the OctopusDeploy service wouldn’t start so we uninstalled the software and noticed that the service still existed under services.msc. we figured that might have to be the issue of the failing services due to older information about the actual service (2.6)
After removing the services, reboot (just to make sure) the installation worked like a charm and all seemed good.
Phase 2, data import…
We proceded with restoration of the 2.6 database and followed the steps provided by the software (select 2.6 database, use masterkey, sit back, relax and await the outcome).
The import took 12 minutes and showed: “Import complete, committing transaction”.
After the import, the tooling initializes a service cycle which resulted in an error:
Import took 00:12:51s
Please look in the Octopus logs directory *****\Octopus\Logs for detailed logging information
Waiting for service to stop. Current status: StopPending
Waiting for service to stop. Current status: Stopped
Error: Cannot start service OctopusDeploy on computer ‘.’.
Full error details are available in the log files.
Cannot start service OctopusDeploy on computer ‘.’.
System.InvalidOperationException: Cannot start service OctopusDeploy on computer ‘.’. —> System.ComponentModel.Win32Exception: The service did not respond to the start or control request in a timely fashion
— End of inner exception stack trace —
at System.ServiceProcess.ServiceController.Start(String args)
at Octopus.Shared.Startup.ConfigureServiceHelper.ConfigureService() in Y:\work\refs\heads\master\source\Octopus.Shared\Startup\ConfigureServiceHelper.cs:line 163
at Octopus.Shared.Startup.ServiceCommand.Start() in Y:\work\refs\heads\master\source\Octopus.Shared\Startup\ServiceCommand.cs:line 46
at Octopus.Shared.Startup.AbstractCommand.Octopus.Shared.Startup.ICommand.Start(String commandLineArguments, ICommandRuntime commandRuntime, OptionSet commonOptions) in Y:\work\refs\heads\master\source\Octopus.Shared\Startup\AbstractCommand.cs:line 57
at Octopus.Shared.Startup.ConsoleHost.Run(Action`1 start, Action shutdown) in Y:\work\refs\heads\master\source\Octopus.Shared\Startup\ConsoleHost.cs:line 72
at Octopus.Shared.Startup.OctopusProgram.Run() in Y:\work\refs\heads\master\source\Octopus.Shared\Startup\OctopusProgram.cs:line 86
Error: The previous command returned a non-zero exit code of: 100
Error: The command that failed was: *****\Octopus Deploy\Octopus\Octopus.Server.exe" service --instance “OctopusServer” --stop --start
We’ve tried to use the ‘local system’ account for the service, but that results in the same error.
what step’s have we missed? Is the initial database configured to use other paths / locations / useraccounts?