made me think there was nothing on the failure. Is that right? On my Command Prompt tests yesterday, my attempted start logged lots to the terminal, and event log got busy (too busy?).
For an example, I got this in chronological order. The first is reasonable, not sure of next two:
Application: Duplicati.GUI.TrayIcon.exe
CoreCLR Version: 8.0.624.26715
.NET Version: 8.0.6
Description: The process was terminated due to an unhandled exception.
Exception Info: Duplicati.Library.Interface.UserInformationException: Server crashed on startup
...
Faulting application name: Duplicati.GUI.TrayIcon.exe, version: 2.1.0.2, time stamp: 0x66470000
Faulting module name: KERNELBASE.dll, version: 10.0.19041.5198, time stamp: 0xd1eefc71
Exception code: 0xe0434352
Fault offset: 0x000000000003b699
Faulting process id: 0x3430
Faulting application start time: 0x01db560b963957f6
Faulting application path: C:\Duplicati\duplicati-2.1.0.2_beta_2024-11-29-win-x64-gui\Duplicati.GUI.TrayIcon.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: df3e9bbc-9de7-4d57-9eee-3b4f2456ba7e
Faulting package full name:
Faulting package-relative application ID:
Fault bucket 1852649600498824582, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: Duplicati.GUI.TrayIcon.exe
...

Does it really need to crash after giving useful message? That seems like it could be improved.
I had tried this standalone without luck, but using the encryption key solved that. It’s in the docs, however it’s stricter than it used to be, and I guess if you lose the key then too bad, which is like situation with a backup encryption password. At least I think I see how this one can be changed.
How much does that interfere with ServerUtil use, and is creating such interference good or bad from a legitimate administrative point of view? Want to impede attackers, but still admin things…
Server authentication model spoke to a concern I had, which is whether having DB read access allowed one to get in and do things. Maybe there’s a right order, e.g. set up before locking down.