Update Failed (2.0.0.3732 - 15 Jan 2016) - Logs inside

[Smellyllama]

Hi Everyone,

I’ve been using Sonarr now for ages after moving across from Sickbeard and I love it. I noticed the other day it hadn’t done the latest update and gave it a few days to see if there was something odd happening that would sort itself out but no.

I get the following message when trying to automatically update;

Message;
Error occurred while executing task ApplicationUpdate: Method not found: 'System.Diagnostics.Process NzbDrone.Common.Processes.IProcessProvider.Start(System.String, System.String, System.Action1<System.String>, System.Action1<System.String>)'.

Exception;
System.MissingMethodException: Method not found: ‘System.Diagnostics.Process NzbDrone.Common.Processes.IProcessProvider.Start(System.String, System.String, System.Action1<System.String>, System.Action1<System.String>)’.
at NzbDrone.Core.Update.InstallUpdateService.InstallUpdate(UpdatePackage updatePackage)
at NzbDrone.Core.Update.InstallUpdateService.Execute(ApplicationUpdateCommand message) in m:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\Update\InstallUpdateService.cs:line 207
at NzbDrone.Core.Messaging.Commands.CommandExecutor.ExecuteCommand[TCommand](TCommand command, CommandModel commandModel) in m:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\Messaging\Commands\CommandExecutor.cs:line 91
at CallSite.Target(Closure , CallSite , CommandExecutor , Object , CommandModel )
at System.Dynamic.UpdateDelegates.UpdateAndExecuteVoid3[T0,T1,T2](CallSite site, T0 arg0, T1 arg1, T2 arg2)
at CallSite.Target(Closure , CallSite , CommandExecutor , Object , CommandModel )
at NzbDrone.Core.Messaging.Commands.CommandExecutor.ExecuteCommands() in m:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\Messaging\Commands\CommandExecutor.cs:line 41

The only thin that looks weird to me is I don’t have an M: drive.

Any ideas on what I should do?

Is any more information going to help and what?

Cheers

[markus101]

Make sure your .net installation is up to date (via Windows update), you may also need to reboot. That method is part of the .net framework and not part of Sonarr.

[Smellyllama]

Thanks markus101, I’ll give that a go now.

[Smellyllama]

Ok, I’ve got windows up to date. There were quite a few updates and some for .net as well. Restarted a few times now but the update fails;

Message
Error occurred while executing task ApplicationUpdate: Method not found: ‘System.Diagnostics.Process NzbDrone.Common.Processes.IProcessProvider.Start(System.String, System.String, System.Action1<System.String>, System.Action1<System.String>)’.

Exeption
System.MissingMethodException: Method not found: ‘System.Diagnostics.Process NzbDrone.Common.Processes.IProcessProvider.Start(System.String, System.String, System.Action1<System.String>, System.Action1<System.String>)’.
at NzbDrone.Core.Update.InstallUpdateService.InstallUpdate(UpdatePackage updatePackage)
at NzbDrone.Core.Update.InstallUpdateService.Execute(ApplicationUpdateCommand message) in m:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\Update\InstallUpdateService.cs:line 207
at NzbDrone.Core.Messaging.Commands.CommandExecutor.ExecuteCommand[TCommand](TCommand command, CommandModel commandModel) in m:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\Messaging\Commands\CommandExecutor.cs:line 91
at CallSite.Target(Closure , CallSite , CommandExecutor , Object , CommandModel )
at System.Dynamic.UpdateDelegates.UpdateAndExecuteVoid3[T0,T1,T2](CallSite site, T0 arg0, T1 arg1, T2 arg2)
at CallSite.Target(Closure , CallSite , CommandExecutor , Object , CommandModel )
at NzbDrone.Core.Messaging.Commands.CommandExecutor.ExecuteCommands() in m:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\Messaging\Commands\CommandExecutor.cs:line 41

Looks like the same error message to me.

[markus101]

Yeah it does.

Which version of Sonarr are you currently running?

[Smellyllama]

Here we go;

Version
2.0.0.3530

[markus101]

Thanks, wanted to make sure there wasn’t another issue in a really old version causing issues.

Can you post trace logs of the update process (enable trace logging, clear the log files, tell Sonarr to update and then post them.

Also how is Sonarr running? Windows service? If so can you try stopping Sonarr, starting it by running NzbDrone.Console.exe and seeing if anything changes?

[Smellyllama]

hmm, Sonarr is starting from the Startup folder with a shortcut to ‘NzbDrone.exe’

Perhaps this is not ideal. I hadn’t considered running it another way.

The logs show exactly the same error message again.

[Smellyllama]

Running Sonarr from the NzbDrone.Console.exe has much the same effect and I can see the console displayed, the error message was the same as before, most odd.

[markus101]

Might be worth trying:

https://blogs.msdn.microsoft.com/dotnet/2014/04/28/introducing-the-microsoft-net-framework-repair-tool/

Otherwise I’m pretty much out of ideas, it definitely looks like a framework issue though. Do you happen to see a similar error if you restart Sonarr from the UI? Or anything similar when it starts?

[Smellyllama]

OKies, I’ve done the Repair tool and it restarted a few windows services.

I tried to restart Sonarr from the UI and it closed OK but the task manger is showing ‘Epic Fail!’ as a task which then links to the process NzbDrone.exe.

I think I’ll back up the DB and uninstall/reinstall to see if that fixes it.

[Smellyllama]

updated now via a fresh install, hopefully this will sort it out for further updates.

Thanks for your help Markus.