OctopusDeploy Service stops after start

Legacy Uncategorised
1

I tried to install Octopus server, but it fails to run OctopusDeploy Service, with this exception log:

2015-12-09 13:27:16.1292 7 FATAL Operation is not supported on this platform.
System.PlatformNotSupportedException: Operation is not supported on this platform.
at System.Net.HttpListener…ctor()
at Octopus.Server.Web.OctopusNancyHost.TryStartListener() in Y:\work\refs\tags\3.2.9\source\Octopus.Server\Web\OctopusNancyHost.cs:line 182
at Octopus.Server.Web.OctopusNancyHost.StartListener() in Y:\work\refs\tags\3.2.9\source\Octopus.Server\Web\OctopusNancyHost.cs:line 155
at Octopus.Server.Web.OctopusNancyHost.Start() in Y:\work\refs\tags\3.2.9\source\Octopus.Server\Web\OctopusNancyHost.cs:line 139
at Octopus.Server.Web.WebServerInitializer.Start() in Y:\work\refs\tags\3.2.9\source\Octopus.Server\Web\WebServerInitializer.cs:line 48
at Octopus.Server.OctopusServerEngine.Start() in Y:\work\refs\tags\3.2.9\source\Octopus.Server\OctopusServerEngine.cs:line 48
at Octopus.Server.Commands.RunCommand.Start() in Y:\work\refs\tags\3.2.9\source\Octopus.Server\Commands\RunCommand.cs:line 37
at Octopus.Shared.Startup.AbstractCommand.Octopus.Shared.Startup.ICommand.Start(String[] commandLineArguments, ICommandRuntime commandRuntime, OptionSet commonOptions) in Y:\work\refs\tags\3.2.9\source\Octopus.Shared\Startup\AbstractCommand.cs:line 57
at Octopus.Shared.Startup.WindowsServiceHost.<>c__DisplayClass1_0.b__0() in Y:\work\refs\tags\3.2.9\source\Octopus.Shared\Startup\WindowsServiceHost.cs:line 19
at Octopus.Shared.Startup.WindowsServiceAdapter.RunService() in Y:\work\refs\tags\3.2.9\source\Octopus.Shared\Startup\WindowsServiceAdapter.cs:line 44
2015-12-09 13:27:16.1822 7 FATAL Unhandled AppDomain exception occurred: Operation is not supported on this platform.
System.PlatformNotSupportedException: Operation is not supported on this platform.
at System.Net.HttpListener…ctor()
at Octopus.Server.Web.OctopusNancyHost.TryStartListener() in Y:\work\refs\tags\3.2.9\source\Octopus.Server\Web\OctopusNancyHost.cs:line 182
at Octopus.Server.Web.OctopusNancyHost.StartListener() in Y:\work\refs\tags\3.2.9\source\Octopus.Server\Web\OctopusNancyHost.cs:line 155
at Octopus.Server.Web.OctopusNancyHost.Start() in Y:\work\refs\tags\3.2.9\source\Octopus.Server\Web\OctopusNancyHost.cs:line 139
at Octopus.Server.Web.WebServerInitializer.Start() in Y:\work\refs\tags\3.2.9\source\Octopus.Server\Web\WebServerInitializer.cs:line 48
at Octopus.Server.OctopusServerEngine.Start() in Y:\work\refs\tags\3.2.9\source\Octopus.Server\OctopusServerEngine.cs:line 48
at Octopus.Server.Commands.RunCommand.Start() in Y:\work\refs\tags\3.2.9\source\Octopus.Server\Commands\RunCommand.cs:line 37
at Octopus.Shared.Startup.AbstractCommand.Octopus.Shared.Startup.ICommand.Start(String[] commandLineArguments, ICommandRuntime commandRuntime, OptionSet commonOptions) in Y:\work\refs\tags\3.2.9\source\Octopus.Shared\Startup\AbstractCommand.cs:line 57
at Octopus.Shared.Startup.WindowsServiceHost.<>c__DisplayClass1_0.b__0() in Y:\work\refs\tags\3.2.9\source\Octopus.Shared\Startup\WindowsServiceHost.cs:line 19
at Octopus.Shared.Startup.WindowsServiceAdapter.RunService() in Y:\work\refs\tags\3.2.9\source\Octopus.Shared\Startup\WindowsServiceAdapter.cs:line 59
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()

We use Windows Server 2008 R2 Service Pack 1, .NET 4.5 is installed. Octopus Server version is 3.2.9.
So what could cause this issue?

2

Hi Dmitry,

Thanks for getting in touch!

What account is being used to run the Octopus Service? This error can appear if the service account doesn’t have permission to listen on an HTTP port.

You might also check to see whether Windows Activation Services are turned on for your server, and whether the firewall might be blocking TCP connections.

I hope this helps!
Damo

3

Hi Damian,

Thanks for your reply!

We use Local System account to run the Octopus Service.
I installed Windows Activation Services and double checked that they are turned on but that didn’t help anyway. Also I tried using different ports, added rules for them in Firewall but no luck again.

Best regards,
Dmitry

4

Hi Dmitry,

The Local Service account in Windows has minimal permissions locally and almost no credentials on the network. That suggests to me that it won’t have sufficient permissions to listen on the network which is why it wouldn’t be starting.

By default, the Octopus service should run as Local System, which gives it all the permissions it needs to operate. I’d suggest going back to the default, or at least creating a service account that has more permissions.

Let me know how you go!
Damo

5

Hi Damo,

Thanks a lot!

Finally I’ve figured out what was causing this issue. For some reason HTTP service was disabled. This service is required to initialize System.Net.HttpListener.

Maybe this will help somebody:
Run cmd as admin, type these commands:

sc config http start= auto
net start http

Best regards,
Dmitry