Are you using the SQLite3 backend? If so and it's really corrupted see 
https://www.sqlite.org/recovery.html. Good luck.

Regards,
John Ralls



> On Mar 8, 2024, at 22:43, David H <hell...@gmail.com> wrote:
> 
> Eric,
> 
> Are you sure you haven't got a more recent backup?  I have multiple backups
> (currently 77 - e.g. <gnucash file name>.gnucash.20240208183810.gnucash) in
> the folder where my usual gnucash data file lives from the last time I
> opened it - you should be able to open the one with the most recent date
> and time stamp in the name and then save as you LLC file proper. .  It
> seems you are opening this file directly in the cloud - I've never been a
> fan of that ? I always copy my file to my local pc (1 of about 5 running
> Win10/11, Ubuntu, MacOS) using FreeFileSync before I open it and then copy
> it back when I'm done which works well for me.  Hope you can get it sorted.
> 
> Cheers David H.
> 
> 
> On Fri, 8 Mar 2024 at 23:59, Eric H. Bowen via gnucash-user <
> gnucash-user@gnucash.org> wrote:
> 
>> I use two separate GnuCash books, one for my personal funds and another
>> for my LLC. These files are saved on a cloud drive and I access them
>> from a few different computers. Some of the computers run Windows 10,
>> while some run Ubuntu Studio 22.04 LTS. The computer on which this first
>> happened was running Windows 10 and GnuCash 5.4+ with sqlite backend,
>> but all computers are now responding the same way.
>> 
>> The day before yesterday I was updating and making some entries in the
>> book for my LLC; GnuCash was working normally. Then, with the work
>> completed, I attempted to switch from the LLC book to my personal book.
>> However, apparently the file was still open on a remote computer because
>> I received the error message that the .lock file could not be received.
>> I elected to close the file and exit GnuCash. Well and good. When I got
>> home that evening I closed the open instance of GnuCash running the
>> personal book. Well and good.
>> 
>> This morning I reopened the personal book and it opened and operated
>> normally. Okay so far. Then, I closed it and attempted to open the book
>> for the LLC. It would not open; I got a pop-up error message reading,
>> "GnuCash could not complete a critical test for the presence of a bug in
>> the "libdi" library. This may be caused by a permissions
>> misconfiguration of your SQL database. Please see
>> https://bugs.gnucash.org/show_bug.cgi?id=645216 for more information."
>> 
>> I went to the bug tracker website, found the entry, and attempted to
>> follow the procedure which others said worked for them, of making a copy
>> of the GnuCash file and opening/closing it. However, the copied file(s)
>> were also corrupt and would not open. I do have a backup, but it's a few
>> weeks old and I'd have to reconstruct the invoices and bills since then.
>> Not a major undertaking, but if possible I'd like to recover this file.
>> The personal book, by the way, continues to work perfectly. Thanks for
>> any assistance----Eric.
>> 
>> 
>> _______________________________________________
>> gnucash-user mailing list
>> gnucash-user@gnucash.org
>> To update your subscription preferences or to unsubscribe:
>> https://lists.gnucash.org/mailman/listinfo/gnucash-user
>> -----
>> Please remember to CC this list on all your replies.
>> You can do this by using Reply-To-List or Reply-All.
>> 
> _______________________________________________
> gnucash-user mailing list
> gnucash-user@gnucash.org
> To update your subscription preferences or to unsubscribe:
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> -----
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.

_______________________________________________
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Reply via email to