Error: Unable to load information about paths from db settings; Duplicate folder ID
Hypertext-infused philosophy personal database software
Brought to you by:
jasonwinning
Menu
▾
▴
1 Attachments
#85 Error: Unable to load information about paths from db settings; Duplicate folder ID
Hey there,
I've been using the software for a good amount of time without further problems. However, as I updated it today to the newest version I faced the following problem:
First, I received this warning message when I executed the program (top part of the jpg file, just in case the file is not loading by the embedded link) which I've never received before informing that when I save changes the XML record data will be upgraded and will no longer be compatible with Hypernomicon v. 1.31.1 or older.
Given I just updated the current version, no problems until here, I suspect.
Then, I received the another warning (middle part of the jpg file), this time an error stating that it could not load information about paths from database settings file. The Error is "Duplicate folder ID".
Finally, I ended up with the interface unable to do anything (bottom part of the jpg file).
It seemed to me that it could have been some problem loading the database, so I tried to do it manually. However, it just went to the first image, the second and so on.
Thanks!
Hi Caio,
Assuming you weren't upgrading directly from a much older version of Hypernomicon (older than v1.19.4, which would date back to 2020), I would say the most likely cause is that your Settings.xml file in the XML folder of your database got corrupted somehow.
Before version 1.32, it wasn't checking for duplicate folder ID corruption. So the corruption actually might have been around for a while before that, not getting detected.
Reinstalling v1.31.1 should allow you to load the database again (just going back to the previous version which ignored duplicate folder IDs), but there will still be the matter of the duplicate folders, which could be problematic even if the database is able to load ok.
Could you attach the Settings.xml file from your XML database folder?
Jason
Actually I think I may know what happened. Did you at any point go into Tools -> Settings, select the Reassign Folders page, and change 2 of the folder settings to point to the same folder?
... Yep, I was able to reproduce this by going into there, setting Papers and Books to save to the same folder, exit and restart Hypernomicon, and I got the error message.
So instead of sending the Settings.xml file, you could confirm this is what is happening by installing v1.31.1, load the database, go into Tools -> Settings -> Reassign Folders, and let me know if any 2 folders are the same.
This is actually a bug: it is treating it as "corruption" if the Papers and Books folders (for example) are configured to be the same folder, but that should probably be treated as okay. If this is what is happening, I can release a new version soon that is more tolerant of duplicate folder settings, and v1.31.1 should work fine for you in the meantime.
Hey there,
I believe I might have done something similar. IIRC, an year or two ago I did some change in the main folder where the papers are to keep them in the same folder. But I'm not being able to find the "select the Reassign Folders page" option in Settings. If it is in the Folders page instead, I cannot access it since it's blocked for me.
Not sure if this will be helpful to you, but I tried to install the new version in another directory just to see if I would have any problems. For safety, I chose to install in my HD - as the other is in my SSD. Even doing this the error persists, which is weird since this version in theory has no previous changes in settings done by me, nor have I uploaded the database in it. Just as I've opened it presented the same error.
For now I'll do as you've suggested and download the 1.33.1 version. Finally, I've just saved some notes before installing the later version and facing this bug. Will I manage to recover it without any problems?
Thank you very much!
I have just released version 1.32.1 which fixes this issue. The bug should not have actually caused any data loss or data corruption. So if you download and install version 1.32.1, it should work as expected and your data should be unaffected.