Deploy Windows Service with Active Directory account as user

Joo_Rosa · 8 August 2016 13:25

Hi,

I’ve a strange problem with the installation of an Windows Service for the first time.
The scenario: Windows Service, custom location, an run as an AD account; Deploy it using Online and Offline methods via Octopus.

The installation fails when try to start up the service. For some reason it do not take the right credentials.
If we re-input the credentials in the Services and re-run the redeployment, the service starts up.

The password is correct, to debug it we use the password in clear text (low security, but for debug purposes).
The Octopus version is 3.2.8.

Thanks João Rosa

robpearson · 9 August 2016 01:23

Hi João,

Thanks for getting in touch. We’ve had similar issues reported in the past and it was generally due to passwords with special characters or sometimes incorrect variable scoping. I’d suggest confirming that your password does not have any special characters (i.e. single (’) or double quote (") characters) and try changing it if necessary.

Alternately, the following support page is quite helpful to debug variable problems. Specifically the “Write the variables to the deployment log” section.
http://docs.octopusdeploy.com/display/OD/Debug+problems+with+Octopus+variables

Let me know how you go.

Rob

Joo_Rosa · 9 August 2016 07:56

Hi Rob,

Thanks for the info. In this case the password as an asterisk (*), however that should not be a problem. We pass across a problem with the pound sign (£) where Octopus can’t pass it along.
We will investigate further and let you know.

Regards, João Rosa

robpearson · 11 August 2016 01:20

Hi João,

Thanks for the reply. I took a look at the code that actually executes the windows service deployment and this area hasn’t changed much since August last year so it should be pretty stable. FYI - It’s open source and available on github if you’d like to take a look.

github.com

OctopusDeploy/Calamari/blob/779e9644b95ba8baddaec25ea538f03016946eff/source/Calamari/Scripts/Octopus.Features.WindowsService_BeforePostDeploy.ps1

## --------------------------------------------------------------------------------------
## Configuration
## --------------------------------------------------------------------------------------

$isEnabled = $OctopusParameters["Octopus.Action.WindowsService.CreateOrUpdateService"]
if (!$isEnabled -or ![Bool]::Parse($isEnabled)) 
{
    exit 0
}

$serviceName = $OctopusParameters["Octopus.Action.WindowsService.ServiceName"]
$displayName = $OctopusParameters["Octopus.Action.WindowsService.DisplayName"]
$executablePath = $OctopusParameters["Octopus.Action.WindowsService.ExecutablePath"]
$arguments = $OctopusParameters["Octopus.Action.WindowsService.Arguments"]
$startMode = $OctopusParameters["Octopus.Action.WindowsService.StartMode"]
$serviceAccount = $OctopusParameters["Octopus.Action.WindowsService.ServiceAccount"]
$customAccountName = $OctopusParameters["Octopus.Action.WindowsService.CustomAccountName"]
$customAccountPassword = $OctopusParameters["Octopus.Action.WindowsService.CustomAccountPassword"]
$dependencies = $OctopusParameters["Octopus.Action.WindowsService.Dependencies"]
$description = $OctopusParameters["Octopus.Action.WindowsService.Description"]

This file has been truncated. show original

Let me know how you go.

Rob

Octopus_Support · 4 January 2017 06:27

Notice:

This issue has been closed due to inactivity. If you encounter the same or a similar issue and require help, please open a new discussion (if we asked for logs or extra details in this thread, consider including them in the new thread). If you are the creator of this thread and believe it should not be closed let us know via our support email.