Ombi: Unable to start as service with latest Windows 10 Creators Update

[arm3n]

Ombi Version:

V 2.1.0

Update Branch:

Stable

Media Sever:

Plex

Media Server Version:

1.5.2.3557

Operating System:

Windows 10 1703

Mono Version (only if your not on windows)

(Place text here)

Applicable Logs (from /logs/ directory or the Admin page):

2017/04/01 11:49:58.349 Ombi.UI.Program Fatal: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Net.HttpListenerException: Access is denied
   at System.Net.HttpListener.AddAllPrefixes()
   at System.Net.HttpListener.Start()
   at Microsoft.Owin.Host.HttpListener.OwinHttpListener.Start(HttpListener listener, Func`2 appFunc, IList`1 addresses, IDictionary`2 capabilities, Func`2 loggerFactory)
   at Microsoft.Owin.Host.HttpListener.OwinServerFactory.Create(Func`2 app, IDictionary`2 properties)```

Problem Description:

I have been running fine with v2.1.0 and its nssm-created service, but every since I upgraded to Windows 10 Creators Update, the service is now getting paused and won't resume. I have tried re-installing with the latest 2.2 version to no avail.

Reproduction Steps:

[Ombi-robot]

Hi!
Thanks for the issue report. Before a real human comes by, please make sure you used our bug report format.
Before posting make sure you also read our FAQ and known issues.
Make the title describe your issue. Having "not working" or "I get this bug" for 100 issues, isn't really helpful.
If we need more information or there is some progress we tag the issue or update the tag and keep you updated.
Cheers!
Ombi Support Team

[tidusjar]

Run as admin. Check the FAQ

On Sat, 1 Apr 2017, 5:57 pm Ombi Support, [e-mail] wrote:

Hi!
Thanks for the issue report. Before a real human comes by, please make
sure you used our bug report format.
Before posting make sure you also read our FAQ
https://github.com/tidusjar/Ombi/wiki/FAQ and known issues
https://github.com/tidusjar/Ombi/wiki/Known-Issues.
Make the title describe your issue. Having "not working" or "I get this
bug" for 100 issues, isn't really helpful.
If we need more information or there is some progress we tag the issue or
update the tag and keep you updated.
Cheers!
Ombi Support Team

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tidusjar/Ombi/issues/1323#issuecomment-290932547, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AGVaLCWzRCybOllrhgPuWIfIKnGomuUwks5rroHggaJpZM4Mwi9n
.

[arm3n]

It's been running as admin since day 1, and I checked it again after upgrading.

[tidusjar]

The error is that we cannot reserve the port 3579 because it doesn't have access. It's a permission issue.

[arm3n]

Thanks Jamie - I have also posted this on the Windows 10 forums.

[tidusjar]

It you take a look at the FAQ there is a section on how you can manually reserve the URL with a console command. It wouldn't need admin permissions then.

[arm3n]

Jamie - I tried that as well:

Truly believe something is up with the new Win10 build - no worries though, I have been using this method with success this morning: https://superuser.com/a/198530

[tidusjar]

Strange!

[mrwebsmith]

arm3n - can you please detail how that link has you running again.. my service is also doing this "paused" only thing.. and i dont quite get the connection to the running the vbs/batch method you linked to... can you reply here with more detail for others that are also on updated win10s

[arm3n]

mrwebsmith - just create ombi.vbs, put it into C:\Users\YOURUSERNAME\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup
with the following content:

Dim WinScriptHost
Set WinScriptHost = CreateObject("WScript.Shell")
WinScriptHost.Run Chr(34) & "C:\Ombi\Ombi.exe" & Chr(34), 0
Set WinScriptHost = Nothing

[mrwebsmith]

thanks... managed to figure that out last night but i appreciate the confirmation ;)

[sekrause]

Some info for everyone who (like me) arrives at this issue through Google because their service won't start with nssm anymore after upgrading to the Windows 10 Creators Update: It seems that all nssm services won't start in the final version of the Windows 10 Creators Update if they were created with the "Console window" option which is enabled by default:

In my case it was a custom service and happened with multiple different services.

There is no need to reinstall the service, you can fix most services by creating the DWORD value AppNoConsole=1 in the registry key [HKLM\SYSTEM\CurrentControlSet\Services\MyService\Parameters].

However, if your service requires a console window I don't know any fix and I also don't know if it's a Windows 10 bug or an intentional change.

[arm3n]

Thanks Sebastian, that's something I might try. However, this does not exclude the existence of a regression in how Windows 10 handles ability to grab ports at startup (as you can see in this thread I started).

[CBers]

https://forums.ombi.io/viewtopic.php?f=9&t=25