Thanks for sharing that information. Was that MSI designed to be installed from the command line? The lack of output during the “freeze” on the task log make me think that the MSI might be asking the user for some info, and since the process is not being invoked by an active user, it just freezes up waiting for input.
Couple of things to check/try:
When the deployment reaches the “MSI Install” step, do you see the installer process firing up on the Task Manager on the server?
Are you able to install this MSI manuall from Powershell if you log into the server?
Thanks for the message! This is just a note to let you know that we’ve
received it, and we’ll get back to you as soon as possible.
The Octopus Deploy team
PS: Our team is located in Brisbane, Australia, and we usually respond
between 9 and 5 weekdays Brisbane time. You can see what time it is
for us here:
Hi ,
By server, do you mean the target deployment server or the server where
octopus is installed?
One of our guys was actually successful to install the same MSI package
following the same steps . However, he has left the company now and I don’t
have access to his machine.
So I think this MSI supports silent installation.
Can there be any other reason or is there any work around?
I mean the Target deployment server where the MSI is gonna be used on. There’s no other workaround for this than confirming if this MSI supports silent installation really.
Also now I am able to go to the second step but there is an error. It says
"1603.
17:56:33 Info | === Logging stopped: 06.11.2015 15:56:18 ===
17:56:33 Error | Error code 1603 was returned: Fatal error
during installation.
17:56:33 Error | At
C:\Octopus\Work\20151106145614-5\Script.ps1:233 char:3
17:56:33 Error | + throw "Error code $exitCode was
returned: $errorMessage"
17:56:33 Error | +
17:56:33 Info | MSI (s) (C4:04) [15:56:17:686]: Product: NOV MPD Early Kick Detection 0.0.1 -- Error 1923. Service 'NOV Early Kick Detection' (NOV EKD) could not be installed. Verify that you have sufficient privileges to install system services.
17:56:33 Info | Error 1923. Service 'NOV Early Kick Detection' (NOV EKD) could not be installed. Verify that you have sufficient privileges to install system services.
It seems that the account running the Tentacle (which is the account that’s doing all the work) doesn’t have enough privileges to do what the MSI needs to do.
Later on you get this other error message
17:56:33 Error | + FullyQualifiedErrorId : Error code 1603 was returned: Fatal error during
17:56:33 Error | installation.
It works when I use tentacle in my local machine but I am not able to reach
to step 2 ( run window installer) when tentacle is installed in virtual
machine.
I am using ESXI 6.0 and have two virtual machines. In one, I have installed
octopus server and in another, I have installed tentacle.
Problem,
1)
When Octopus server is VM
And Tentacle is local machine
MSI gets downloaded to tentacle and installed
When Octopus server is VM
And Tentacle is also VM
MSI gets downloaded to tentacle but not installed
We are using virtual machine extensively and need it to work in virtual
machines.
I am doubting that there is communication problem between server(VM1) and
tentacle (VM2). Any resolution for this?
How can I make it to work? Any guidelines? I think I am very close but
still something is not getting quite right.
Hi,
I have gone through it . The only problem I am having is when trying to
deploy to virtual machine. In normal machine , I am able to do it. Is there
any guidelines for it?
We don’t have a special guide for VM’s vs Physical machines. The networking guidelines are the same for Physical, Virtual and Cloud machines for Octopus.