Release: 2.0.9.109 (Canary) 2024-11-06

[kenkendk]

@Taomyn

I reinstalled on my Windows server and those event log messages have gone. However, I think the MSI installer is broken again as this is what I saw when I went to uninstall it

I have no idea how that is even possible. The documentation clearly states that only one version with the same upgrade-code can be installed at a time. The upgrade code has not been changed since the MSI’s were first published.

@ollibraun

I switched from.208 to.209. Not sure if this has something to do with the previous one, but on my Windows machine, opening the web interface brings up an error message and the logs cannot be opened.

Could it be the same as @Taomyn experienced, where you have two versions installed?

@ollibraun

Editing the jobs is only partially possible – the destination and source data remain empty, while the schedule and options display values.

That is caused by the slow loading, a fix is ready soon.

[Taomyn]

@kenkendk

I have no idea how that is even possible. The documentation clearly states that only one version with the same upgrade-code can be installed at a time. The upgrade code has not been changed since the MSI’s were first published.

Me neither as 108 was installed over 107 without issue, but I just had the exact same thing on two other Win2k22 servers so needed to reinstall on those. I still have two Win11 machines to check out when I get home so I will let you know, but if you want me to grab any extra information from them before I try to fix them, let me know.

[ts678]

@Taomyn

I removed .108 then .109 and ran my MSI installer script again which runs it with the parameter "FORSERVICE=“true” and it looks fine now

The “again” sounds like failed upgrade did that. Have normal upgrades worked?

@kenkendk

The upgrade code has not been changed since the MSI’s were first published.

Kind of vague. There have been MSI releases for lots of years. A recent change:

Remove existing product before install for MSI #5538

I’m thinking that’s what About → Changelog shows as:

2024-09-11 - 2.0.9.107_canary_2024-09-11
Another fix for MSI packages breaking on upgrade

2.0.9.106 had this:

- Fixed MSI packages failing to upgrade
- Re-added the `FORSERVICE=true` flag to MSI packages

with that used by the user script, and me asking if it matters for fails.

Maybe I’ll test some upgrades, but I’m not sure what I should target.

[kenkendk]

@ts678

Kind of vague

Unfortunate clash of terminology. I was referring to the MSI field named “UpgradeCode”.

@ts678

Maybe I’ll test some upgrades, but I’m not sure what I should target.

That is the big question. I have tried various approaches to replicate this, but I have not succeeded.

The fixes you found are changing the way the previous product (meaning MSI) is uninstalled.
The “fix” is to remove everything before even attempting to start the installation.
This has the downside that files that are already present in the correct version (i.e., not changed between versions) will now be removed and copied in again.

But that does not explain how/why the previous version is still listed as “installed”.

[Taomyn]

No, there was no failed upgrade mentioned, it just didn’t perform what was expected and I didn’t look for this as an issue because I thought it had been fixed.

@kenkendk I just remembered, I left the setting that would keep MSI logs for each run, so here’s the last 3 upgrades, to .108 and then for the two recent to .109, perhaps this can shed some light on it.

MSI-Logs.zip (601.9 KB)

[drwtsn32]

@kenkendk

I can confirm that the icon does not appear on Debian 12.5, but I think 12.7 is the latest release?

I’m running Debian testing (trixie) on this particular machine.

@kenkendk

sudo apt install gnome-shell-extension-appindicator

If I do that, it wants to install 191 dependencies (probably because I’m running KDE Plasma) and remove pulseaudio packages. I don’t think I want to proceed with that test. Doesn’t sound like it solves the issue for you anyway with .109.

[kenkendk]

@drwtsn32

If I do that, it wants to install 191 dependencies (probably because I’m running KDE Plasma) and remove pulseaudio packages. I don’t think I want to proceed with that test. Doesn’t sound like it solves the issue for you anyway with .109.

It could be different for KDE, but Gnome at least, I had to add the shell extensions to get it working. For .109 it still crashes due to the Tmds version problem.

I have put up a new version that fixes the issues reported in this topic (except the lingering update notification from @ts678 which is registered as an issue).

[ollibraun]

@kenkendk

@ollibraun

I switched from.208 to.209. Not sure if this has something to do with the previous one, but on my Windows machine, opening the web interface brings up an error message and the logs cannot be opened.

Could it be the same as @Taomyn experienced, where you have two versions installed?

@ollibraun

Editing the jobs is only partially possible – the destination and source data remain empty, while the schedule and options display values.

That is caused by the slow loading, a fix is ready soon.

I only had the.209 installed. Version.210 solved the problem for me, everything works as expected. Thank you very much!

[ts678]

@kenkendk

I have no idea how that is even possible.

I found a repro, but be careful, as I also found a way (maybe user error) to accidentally restart PC.

I intentionally tried to upgrade with a 2.0.9.107 Windows service running, and I did it with msiexec.

I’ve seen posts talking about FORSERVICE=true with variations on use of quotes and whitespace.

This just popped up the GUI, and I was expecting a silent install. I added /quiet and got a reboot.

Apparently I should have also added /norestart, although I don’t know if my running service was part of why it saw need to restart. Maybe it would have anyway. Maybe it’s an old bug. Don’t know.

System event log:

The process msiexec.exe has initiated the restart of computer HP4 on behalf of user NT AUTHORITY\SYSTEM for the following reason: No title for this reason could be found
Reason Code: 0x80030002
Shutdown Type: restart
Comment: The Windows Installer initiated a system restart to complete or continue the configuration of ‘Duplicati’.

EventID 1074

EDIT 1:

From above, you can see that I actually used 2.0.9.111 (per Duplicati offer), but discussion is here.

EDIT 2:

Actual Program Files folder is 182 MB per Explorer, unlike the Apps listing claim of being 57.6 MB.

EDIT 3:

Explorer says mentioned WinMerge difference files are about 13 MB. Not sure where 57.6 is from.

With all the Avalonia differences, I kind of expected a TrayIcon start to complain, and so it did, like:

C:\Program Files\Duplicati 2>Duplicati.GUI.TrayIcon.exe

C:\Program Files\Duplicati 2>No database encryption key was found. The database will be stored unencrypted. Supply an encryption key via the environment variable SETTINGS_ENCRYPTION_KEY or disable database encryption with the option --disable-db-encryption
Server has started and is listening on port 8400
Unexpected error: System.IO.FileNotFoundException: Could not load file or assembly 'Avalonia.Controls, Version=11.2.0.0, Culture=neutral, PublicKeyToken=c8d484a7012f9a8b'. The system cannot find the file specified.
File name: 'Avalonia.Controls, Version=11.2.0.0, Culture=neutral, PublicKeyToken=c8d484a7012f9a8b'
   at Duplicati.GUI.TrayIcon.AvaloniaRunner.SetMenu(IEnumerable`1 items)
   at Duplicati.GUI.TrayIcon.TrayIconBase.Init(String[] args)
   at Duplicati.GUI.TrayIcon.AvaloniaRunner.Init(String[] args)
   at Duplicati.GUI.TrayIcon.Program.StartTray(String[] _args, Dictionary`2 options, HostedInstanceKeeper hosted, String password, String acceptedHostCertificate)
An error occurred on server tear down: System.ObjectDisposedException: Cannot access a disposed object.
Object name: 'IServiceProvider'.
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.ThrowHelper.ThrowObjectDisposedException()
   at Microsoft.Extensions.DependencyInjection.ServiceProvider.GetService(ServiceIdentifier serviceIdentifier, ServiceProviderEngineScope serviceProviderEngineScope)
   at Microsoft.Extensions.DependencyInjection.ServiceProvider.GetService(Type serviceType)
   at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService(IServiceProvider provider, Type serviceType)
   at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService[T](IServiceProvider provider)
   at Duplicati.Library.RestAPI.FIXMEGlobal.get_WorkThread()
   at Duplicati.Server.Program.<>c.<Main>b__60_12()
   at Duplicati.Server.Program.Main(String[] _args)

C:\Program Files\Duplicati 2>Duplicati.Server.exe
No database encryption key was found. The database will be stored unencrypted. Supply an encryption key via the environment variable SETTINGS_ENCRYPTION_KEY or disable database encryption with the option --disable-db-encryption
Server has started and is listening on port 8200

(Ctrl-C to stop it)

C:\Program Files\Duplicati 2>Duplicati.GUI.TrayIcon.exe

C:\Program Files\Duplicati 2>No database encryption key was found. The database will be stored unencrypted. Supply an encryption key via the environment variable SETTINGS_ENCRYPTION_KEY or disable database encryption with the option --disable-db-encryption
Server has started and is listening on port 8200
Unexpected error: System.IO.FileNotFoundException: Could not load file or assembly 'Avalonia.Controls, Version=11.2.0.0, Culture=neutral, PublicKeyToken=c8d484a7012f9a8b'. The system cannot find the file specified.
File name: 'Avalonia.Controls, Version=11.2.0.0, Culture=neutral, PublicKeyToken=c8d484a7012f9a8b'
   at Duplicati.GUI.TrayIcon.AvaloniaRunner.SetMenu(IEnumerable`1 items)
   at Duplicati.GUI.TrayIcon.TrayIconBase.Init(String[] args)
   at Duplicati.GUI.TrayIcon.AvaloniaRunner.Init(String[] args)
   at Duplicati.GUI.TrayIcon.Program.StartTray(String[] _args, Dictionary`2 options, HostedInstanceKeeper hosted, String password, String acceptedHostCertificate)

I’m not sure why the two failures differ in the chosen LISTEN port and the details of the stack trace.
From an Avalonia.Controls view 11.2.0.0. is indeed the latest, but incomplete update has 11.0.10.0.

I haven’t played with variations on test case, but at least it seems like an advance to have anything.

EDIT 4:

Restart options on Microsoft msiexec page has a vague notice that-use files might cause a restart.