I upgraded one of my machines from 220.127.116.11 to 18.104.22.168. (Windows 10 x64)
After upgrading the TrayIcon process won’t start.
The following events are visible in the Event Viewer.
How can I troubleshoot this further?
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileNotFoundException
at Duplicati.Library.AutoUpdater.UpdaterManager.RunMethod(System.Reflection.MethodInfo, System.String)
at Duplicati.Library.AutoUpdater.UpdaterManager.WrapWithUpdater(Duplicati.Library.AutoUpdater.AutoUpdateStrategy, System.Action)
at Duplicati.Library.AutoUpdater.UpdaterManager.RunFromMostRecentSpawn(System.Reflection.MethodInfo, System.String, Duplicati.Library.AutoUpdater.AutoUpdateStrategy)
Found a bit more detail in Duplicati-crashlog.txt:
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.IO.FileNotFoundException: Could not load file or assembly 'CoCoL, Version=22.214.171.12405, Culture=neutral, PublicKeyToken=0983de3c914beeaa' or one of its dependencies. The system cannot find the file specified.
at Duplicati.GUI.TrayIcon.HostedInstanceKeeper..ctor(String args)
at Duplicati.GUI.TrayIcon.Program.RealMain(String _args)
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object parameters, Object arguments)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object parameters, CultureInfo culture)
at Duplicati.Library.AutoUpdater.UpdaterManager.RunMethod(MethodInfo method, String args)
Thanks for bringing this up - and glad you figured it out!
It is a known issue and there was a change made to how updates are handled somewhere in the 126.96.36.199x range (I think). That change should make issues like yours happen much less frequently - but only once you’re on the new code for both the “from” and “to” versions of the upgrade.
Please let us know if you run into it again now that your on the new update code.
Oh, and sorry for the delay in replying - sometimes life intrudes on my internet time.
Thanks for the reply! I think it would be beneficial to try and change the installer logic to make sure that DLL gets installed properly, even if someone is upgrading from 188.8.131.52. Seems like this may be a common scenario since many won’t be using canary/experimental builds.