Installation Issue - Windows 10, Build 19042
Just downloaded Beta v1.0.0-beta5 and attempting to install. Application hangs at “Checking for native dependencies ..”
OS: Windows 10 x64; Build: 19042; .net Framework: 4.8
When I attempt to execute “ModBrosMonitoringService.exe” from a command prompt as Administrator, I get the following error:
C:\Users\xxx\AppData\Local\MoBro_Local>ModBrosMonitoringService.exe
Configuration Result:
[Success] Name ModBros Monitoring
[Success] DisplayName ModBros Monitoring Service
[Success] Description System Monitoring Service by ModBros
[Success] ServiceName ModBros Monitoring
Topshelf v4.2.1.215, .NET Framework v4.0.30319.42000
Topshelf.Hosts.ConsoleRunHost Error: 0 : An exception occurred, System.PlatformNotSupportedException: Operation is not supported on this platform.
at System.Net.HttpListener..ctor()
at Nancy.Hosting.Self.NancyHost.TryStartListener()
at Nancy.Hosting.Self.NancyHost.StartListener()
at Nancy.Hosting.Self.NancyHost.Start()
at Topshelf.ServiceConfiguratorExtensions.<>c__DisplayClass2_0`1.<WhenStarted>b__0(T service, HostControl control)
at Topshelf.Builders.DelegateServiceBuilder`1.DelegateServiceHandle.Start(HostControl hostControl)
at Topshelf.Hosts.ConsoleRunHost.Run()
Thoughts? Thanks in advance!
Hi @braintez
first off thanks for reporting this and directly including a stacktrace and the windows version used ?
I've just updated my Windows to the same 19042 build and could install the service without any error.
Also executing it manually via command prompt does work
Could you open an admin command prompt again and check if your http service is running by executing:
sc query http
It should report back as running and the response should look something like this:
SERVICE_NAME: http
TYPE : 1 KERNEL_DRIVER
STATE : 4 RUNNING
(STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
If it's not running, please execute the following two commands:
sc config http start=demand
sc start http
If it starts successfully, try again to execute our monitoring service (ModBrosMonitoringService.exe).
Would be awesome if you could report back if that solved the problem :)
Thanks, @Seraksab !
I tried to anticipate what questions you would ask as a developer before I submitted my post. I've been on the other side so I know how it is when there isn't enough data to troubleshoot a problem.
Your solution worked! I initially disabled http services while troubleshooting another program. I have since found a workaround so that I can open port 80 once again. Just in case, will it be possible in the future to configure a different port to listen on i.e. 8080 or something custom?
Yeah, I know that situation all too well ^^
Changing the port is currently not possible. Making it configurable would definitely make sense but that would also have implications on the Raspberry Pi and Android app as we would have to include settings there as well.
We may enable this in the future but it's definitely not on our priority list at the moment.
But neither our background service nor our main application currently uses port 80, so you shouldn't have to open that one for it to work.
Understood. Thanks for the fast reply and quick solution! Going to roll my sleeves up and start tinkering. I suppose you can close this issue, if it's viewed as a ticket / open item. Appreciate the work of the ModBros!!