Error Installing Tentacle on Azure VM Using Powershell Remoting / Scheduled Task

Legacy Uncategorised
1

Hi,
So we’re trying to automate installation of the Tentacle using a combination of Powershell Remoting to create a scheduled task and then executing a Powershell script that configures the Tentacle.

We’re doing it this way due to the user profile / certificate issue using Powershell Remoting although we’ve encountered the same error when executing the commands via a Powershell Remoting session directly.

The error is…

Cannot start service from the command line or a debugger. A Windows Service must first be installed (using installutil.exe) and then started with the ServerExplorer, Windows Services Administrative tool or the NET START command.

I can’t see any reason why it’s happening - if we run the Tentacle configuration from an interactive command prompt it works fine.

Any ideas what we’re tripping up on here? Edit: We’re installing Octopus Tentacle v2.0.13.1100

Thanks,
Dean

2

Hi Dean,

The Tentacle.exe commands all require the --console flag to be specified when running non-interactively. We missed this in the command help originally (fixed in the next build).

Cheers,
Nick

3

Nice one, thanks Nick, it’s all working now. Great work on Octopus by the way, fantastic product :).

Cheers,
Dean