Sonarr Not Starting Windows 10 v2.0.0.3953 (doesn't seem to be .NET known issue)

[rynh]

Sonarr version (exact version): 2.0.0.3953
Mono version (if Sonarr is not running on Windows):
OS: Windows 10 64bit
((Debug logs)) (posted to hastebin or similar): http://pastebin.com/jqHpX1Bc
Description of issue (if you think you’ve found a bug please include steps to reproduce):

The service won’t start. I can’t find the known issue "TinyIoC.TinyIoCResolutionException… " in the logs anywhere and I’ve confirmed I have the most updated .NET Framework 4.6.1.

From the logs are you able to tell what’s wrong?

[Taloth]

The log file seems truncated, are you sure that’s everything?

[rynh]

Thanks for the quick reply. Yeah it seems to cut off at that point… From the Windows side when I start the service I get an error 1053 "The service did not respond to the start or control request in a timely fashion."
Takes about 20 seconds to give that error.

Here’s a new paste of a 2nd start service attempt… this is from sonarr.debug.txt:
http://pastebin.com/sM37M65m

sonarr.trace.txt and sonarr.txt seems to have the same log info.

[Taloth]

Could you run NzbDrone.Console.exe or NzbDrone.exe manually? (not as service)
See it gives an error.

[rynh]

Interesting… running NzbDrone.Console.exe works.

Maybe uninstall and reinstall the service? Do I need any special operators when running those?

[Taloth]

That won’t do you any good, it’s taking a too long to start up. Way too long.

Check the log of the manual startup. Info|Bootstrap|Starting Sonarr till Trace|EventAggregator|ApplicationStartedEvent -> ReconfigureLogging is a pretty good indicator.
In your posted log file it’s 16-3-28 09:49:55.7|Info|Bootstrap|Starting Sonarr till over 16-3-28 09:50:25.0|Debug|netsh.exe| Delegate: No. That’s over 30 seconds, and it’s not even finished starting up.

That’s also whats the problem with the service, Windows is terminating the service for not starting up in time.

So something on the PC is causing it to go dead slow. Could be a problem with IO, CPU or a virus scanner, but something is definitely wrong.

FYI, on my computer it takes mere seconds to start up.

[rynh]

Yeah I see what you mean … everything else was running fine but I saw Windows Defender using a lot of CPU while running the console version directly.

I added the NzbDrone folder to the exclusion, restarted the console version and it was up within seconds… Stopped that and ran the service, it started right up too.

Guess I’ll leave the exclusion in place. Not sure why Windows Defender decided to do that seemingly out of the blue.

Thanks for your help!

[Taloth]

@markus101 We may want to look into this, could affect multiple users if it’s an issue with Windows Defender.

[netlynx]

I can confirm I was having the same problem where the service would not start automatically. Adding the exclusion to Windows Defender problem was resolved.