REPAIR command failing - Xamarin.Mac.dll load failing

REPAIR & other commands fail with logmessage “Failed to load assembly C:\Program Files\Duplicati 2\Xamarin.Mac.dll error message: Non-abstract, non-.cctor method in an interface.”
This is with Duplicati - 2.0.7.1_beta_2023-05-25 on Windows 10 with the latest Microsoft Visual C++ installed.
Other info:

  • CLRVersion : 4.0.30319.42000
  • CLROSInfo : {“Platform”:“Win32NT”,“ServicePack”:“”,“Version”:“10.0.19045.0”,“VersionString”:“Microsoft Windows NT 10.0.19045.0”}

Are they really ? this is an ‘explicit only’ message, not an error message.
Can you provide a screenshot of the job log ?

In any case the REPAIR doesn’t do anything.
Here is a copy from the LIVE log. Screenshot is not accepted here and email reply address seems to be invalid.

  • Jan 31, 2024 2:29 PM: Failed to load assembly C:\Program Files\Duplicati 2\Xamarin.Mac.dll, error message: Non-abstract, non-.cctor method in an interface.

  • Jan 31, 2024 2:29 PM: Failed to load assembly C:\Program Files\Duplicati 2\Xamarin.Mac.dll, error message: Non-abstract, non-.cctor method in an interface.

  • Jan 31, 2024 2:29 PM: Failed to load assembly C:\Program Files\Duplicati 2\Xamarin.Mac.dll, error message: Non-abstract, non-.cctor method in an interface.

  • Jan 31, 2024 2:29 PM: Failed to load assembly C:\Program Files\Duplicati 2\Xamarin.Mac.dll, error message: Non-abstract, non-.cctor method in an interface.

  • Jan 30, 2024 7:11 PM: Failed to load assembly C:\Program Files\Duplicati 2\Xamarin.Mac.dll, error message: Non-abstract, non-.cctor method in an interface.

  • Jan 30, 2024 7:11 PM: Failed to load assembly C:\Program Files\Duplicati 2\Xamarin.Mac.dll, error message: Non-abstract, non-.cctor method in an interface.

  • Jan 30, 2024 7:11 PM: Failed to load assembly C:\Program Files\Duplicati 2\Xamarin.Mac.dll, error message: Non-abstract, non-.cctor method in an interface.

  • Jan 30, 2024 7:11 PM: Failed to load assembly C:\Program Files\Duplicati 2\Xamarin.Mac.dll, error message: Non-abstract, non-.cctor method in an interface.

  • Jan 30, 2024 7:11 PM: Failed to load assembly C:\Program Files\Duplicati 2\Xamarin.Mac.dll, error message: Non-abstract, non-.cctor method in an interface.

  • Jan 30, 2024 7:11 PM: Failed to load assembly C:\Program Files\Duplicati 2\Xamarin.Mac.dll, error message: Non-abstract, non-.cctor method in an interface.

  • Jan 30, 2024 7:11 PM: Failed to load assembly C:\Program Files\Duplicati 2\Xamarin.Mac.dll, error message: Non-abstract, non-.cctor method in an interface.

  • Jan 30, 2024 7:11 PM: C:\Program Files\Duplicati 2\win-tools\gpg.exe

I asked for the job log, not the live log.

What do you mean with “job log”. The log labeled Stored,is at the end of this mail.
I now reran the commandline REPAIR.
The first time I got something like “Waiting to start task”. Nothing happened, so I cancelled the Duplicati Background Process.
I then restarted Duplicati and tried the Repair again and now I get “Running … stop now”, but again nothing happens, no CPU, no Disk.
In the Live log I see the messages about Xamarin
Thank you
Jean-Paul

  • General
  • Remote
  • Jan 30, 2024 6:37 PM: list
  • Jan 30, 2024 2:40 PM: get duplicati-b8de1ac21b5e4460e864dcc020d54787d.dblock.zip
    {“Size”:524228036,“Hash”:“hVwJ3ISuHNsq02146paalwp3TzrvVemvAu86uLqSWJo=”}
  • Jan 30, 2024 2:40 PM: get duplicati-i920b62a3bddb40f789503ec770534c32.dindex.zip
    {“Size”:616015,“Hash”:“HhPkJrL3cGV5vc+dv62krCU1bpcyk9MNQAIbliBLll4=”}
  • Jan 30, 2024 2:40 PM: get duplicati-20231221T180835Z.dlist.zip
    {“Size”:29364162,“Hash”:“Q7iGT6otubFctJvDGGyOs21I0M8Bvv3jmAG15Vu6UeQ=”}
  • Jan 30, 2024 2:40 PM: delete duplicati-b688d2ad4f4154a18a1e49fa9f550ed0b.dblock.zip
  • Jan 30, 2024 2:40 PM: delete duplicati-b5580708337c34d93ae2fa81873becc74.dblock.zip
  • Jan 30, 2024 2:40 PM: delete duplicati-b04a4107a66ab43d784d94ae88775a668.dblock.zip
  • Jan 30, 2024 2:40 PM: delete duplicati-bda562e6416ea464aab0a847556d9b948.dblock.zip
  • Jan 30, 2024 2:40 PM: delete duplicati-be1e7ee535f994756ade342d12af5c5a1.dblock.zip
  • Jan 30, 2024 2:40 PM: delete duplicati-b17febdeec5824f18ab93e4e7bad156cf.dblock.zip
  • Jan 30, 2024 2:40 PM: delete duplicati-b17f8b113b4684913be81213a06bb3772.dblock.zip
  • Jan 30, 2024 2:40 PM: list
  • Jan 30, 2024 2:34 PM: put duplicati-b17febdeec5824f18ab93e4e7bad156cf.dblock.zip
  • Jan 30, 2024 2:32 PM: put duplicati-b17f8b113b4684913be81213a06bb3772.dblock.zip

I mean what is displayed when clicking on this:

If you see nothing here, that may be that no job terminates. When you say ‘failing’, I understand ‘terminates with an error message’. If you mean ‘seems to hang and I kill the process’, well, that’s another problem and I did not understand it like that.

Tomorrow I will be travelling for nearly 3 weeks and won’t be able to work on this until I am back home.
Thank your understanding… .

Back home, I’ve tried again the REPAIR command from the GUI? and again nothing happens. In my browser I see “Running commandline entry” followed by a line “Running … stop now”.
Duplicati processes are using 0 cpu and 0 Disk.
I now use the Duplicati.CommandLine.exe in a Windows command prompt and that works.
Thanks

Err, this is not fully clear on what you want at this point. Do you need further support on the problem on not being able to do a repair from the Web UI, while you can from the command line (if I understand you correctly) ? Or is it ‘database repaired, end of story’ ?

Personally I do not need any further support on this problem. Using the command line is the better approach for me, seems to be more robust than the GUI, allows concurrent tasks, etc.
Nevertheless I think there might be a problem with the GUI at least in my environment.
Thanks for your assistance and quick replies.

Well, what can be done depends on your commitment to help the software to be better then. Can you at least explain if what you said in your first post (install ‘the latest Microsoft Visual C++’) was necessary to make the program work ? because that’s something I don’t remember having done when I tested Duplicati on Windows 10. OTOH maybe it could the reason for the problem :slight_smile: