2.4.5 tentacle failes when installed on windows 2003

Legacy Uncategorised
1

Hi,

There is a failure in configuration stage of tentacle installation in version 2.4.5 on windows 2003.

Install log:

Saving instance: Tentacle
A certificate already exists, no changes will be applied.
Generating a new SQUID for the Tentacle...
The new SQUID of this Tentacle is: SQ-RMX-QA-APP1-E1B32037
Removing all trusted Octopus servers...
Home directory set to: D:\Octopus
Application directory set to: D:\Octopus\Applications
Services listen port: 10933
Adding 1 trusted Octopus servers
The following command was not found: advfirewall firewall add rule "name=Octopus Deploy Tentacle" dir=in action=allow protocol=TCP localport=10933.
Error: The previous command returned a non-zero exit code of: 1
Error: The command that failed was: "netsh" advfirewall firewall add rule "name=Octopus Deploy Tentacle" dir=in action=allow protocol=TCP localport=10933
Deleted instance: Tentacle

Obviously, advfirewall does not exists on win 2003, AFAIK it supported since win 2008 …

thanks

2

Hi,

Thanks for reporting this bug.
We have added an issue here if you would like to track it:

However a workaround currently would be the following:
On the ‘listening Tentacle’ tab of the Tentacle setup wizard you need to uncheck ‘Add Windows Firewall Exception’ and it will skip that step in the installation of the Tentacle for Windows 2003.

I hope this helps!
Vanessa

3

Thanks Vanessa
Didn’t pay attention to this little checkbox :slight_smile:
It helped.

By the way, just FYI
On other win 2003 tentacles, which had 2.4.3, the automatic upgrade process initiated by the server was successful.

Thanks,
Igal

4

This issue is back in version 2.4.7… except somebody removed the ‘Add Windows Firewall Exception’ checkbox so it always tries to add the firewall exception and fails…

I had to drop back to 2.4.5.

5

Hi Kevin,

I’m really sorry about that. A bit of mis-communication and over enthusiasm on our end only fixed half the issue (and kinda made it worse!).
I’ve reopened the issue and will make sure its resolved as soon as possible.

Thanks for letting us know about this!

Vanessa

6

Hi Kevin and Igal,

I am happy to report that the fix that fixed the fix is now fixed and live in the latest version of Octopus Deploy. (In otherwords, we unbroke what we broke).

The download and release notes can be found here:

Happy Deployments!
Vanessa