Issues with Octopus stopping wrong service


We are experiencing an issue with Octopus where the incorrect service is being stopped on the IIS server. What we’ve done is migrate the server over the weekend to a new server. However since migrating to the new server, when running a deployment Octopus stops the incorrect service. I’ve upgraded the tentacles on the SQL and IIS servers to the latest versions.

Is there anything else I can do to resolve this issue? Would it be worth me reinstalling the tentacles from scratch where I completely uninstall the tentacle from the IIS server and reinstall it?


Ibrar Ahmed

Hi Ibrar,

Thanks for reaching out! It doesn’t sound like re-installing the Tentacles will change anything. This sounds like a deployment config issue. Couple of questions/requests about your environment:

  • Exactly which service are you trying to stop, and which one is being stopped instead?

  • Could you also please follow the below instructions and send me a deployment log?

1) Add these 2 variables to your project

2) Create a new release (so the new variables take effect) and deploy it. If possible skip as many steps as you can and only leave step we are troubleshooting in order to avoid the noise in the log.

3) Send us the raw log of that deployment


Hi Dalmiro,

We managed to resolve this issue by removing a vairalbe.

Thanks and Regards,

Ibrar Ahmed – Systems Administrator

Tel: +44 (0) 207 922 5154