06/24 06:35:52 Error: [broker] failed to read local time offset from registry: System.OverflowException: TimeSpan overflowed because the duration is too long.
at System.TimeSpan.IntervalFromDoubleTicks(Double ticks)
at System.TimeSpan.Interval(Double value, Double scale)
at System.TimeSpan.FromMinutes(Double value)
at Sooloos.Broker.ApiRoot..ctor(State state)
Errors in the server.log when I start it and it never gets out of the “Initializing…” Status - same as before
Thanks so much for staying on top of this — we really appreciate your patience.
Just to confirm, have you had a chance to test things with a completely fresh database on your Nucleus? You can do this by going to the web UI and selecting the “Reset” option under the database section. Please note that this step will fully wipe your existing database, including any saved settings and library curation — so it’s definitely not ideal, but it might allow you to regain access to your Nucleus in the meantime.
That said, our team has flagged your issue as a priority, and we’re actively working toward a more complete and lasting solution. We’ll follow up as soon as we have more to share.
No need to worry about keeping this thread open. We have it tracked internally now and will be sure to reopen the thread and follow up here as soon as there are any updates to share.
While the ticket is at our R&D for solving we would like to ask you whether you have some of your older backups taken from the same windows machine ?
If so, can you please revert the locale to what it used to be like at the moment when you created the backup → reinstall roon → restore the backup → change the locale to dot instead of comma → get backup again and restore on Roon.
This is some sort of workaround that might help.
please let us know whether it is suitable for you.
We’re sorry once again for making you push through this hassle.
The locale has always been like that on my Windows machine - there is no backup from “before I changed it”. I tried changing my locale on windows and importing a backup as well as changing the locale on the already running roon-version - both times I get the same errors with the server-software that I have with the nucleus.
I wonder if this error could be because you didn’t clear out the previous Roon Server when you tried this test? To set up a fresh database for this test:
Create a Backup of your current database (if needed)
Find the folder that says “Roon Server” and “Roon”
Rename the “RoonServer” folder to “RoonServer_old” and “Roon” to “Roon_old”
Reinstall the Roon App from our Downloads Page to generate a new Roon folder
Verify if the issue persists on a fresh database before restoring the backup
Here is the process outlined from a Windows machine:
I also wonder if there’s a way to manually fix this. You might be able to restore the backup, exit Roon, navigate to RoonServer/Database/Registry/Core, move the local_time_offset_from_utc file to another location (like your desktop,) and try to restart RoonServer.
Running it freshly from a reset Installation never was the problem - it always crashed when I reimported the backup.
The advice with removing the local_time_offset_from_utc from the folder helped though. I shut down my Roon Server on my Desktop, changed the decimal separator to what the Nucleus was expecting, removed that file from my AppData-Folder and rebooted the server on my Desktop. I then created a new backup from that running instance and this backup finally could be imported correctly on my Nucleus One.
I hope all is well! I wanted to follow up on this thread to let you know we’ve released a fix for this issue over on our Early Access branch of Roon.
I realize this issue doesn’t affect your everyday use of Roon, so there isn’t any specific action needed on your end - we’ll eventually push this fix over to our main Production version of Roon, and at that point, you shouldn’t have any issues restoring backups!
