[GNC] Maddening!!!!!!!!

[Jim DeLaHunt]

Jack:

On 2024-01-11 09:11, Jack Slater wrote:
> 90 minutes of reconciling down the drain with a crash near the end of the
> final account....
My commiserations. Yes, it is maddening to lose 90 minutes of work when 
the tech decides to fail you.
> ... Oddly, even though GnuC auto saves periodically, it seems
> none of any add/delete/balance transactions were saved in any account! Why
> would that be????

I can think of several interesting directions you could take this thread:

Why didn't GnuCash seem to preserve any of the changes in my 90 minutes 
of work?

How can I change my workflow so that I lose less work when the tech 
decides to fail me?

How can I improve the way I write message to this list, so that I get 
more helpful answers?

How can I stop these tech failures from happening?

On that last point, I can offer two concrete suggestions:

1. GnuCash has a "Check and Repair" feature which is useful to try when 
you are concerned about "rogue" transactions and such. Try going to the 
Accounts tab of the main window, and select menu item Actions -- Check 
and Repair -- Repair All. This menu is described a little in the GnuCash 
manual, section 4.2.1.4. "Account Tree - Actions Menu", at 
<https://www.gnucash.org/docs/v5/C/gnucash-manual/gui-acct-tree.html#AccTree-actions-menu>.

2. The text in your "Entry Point Not Found" dialogue, which GnuCash 
displays when it crashes, has been discussed on this list recently.  It 
is described in a bug report at 
<https://bugs.gnucash.org/show_bug.cgi?id=799170>. It is suspected to be 
problem from GnuCash 5.4 leaving pieces behind when GnuCash 5.5 
installs. There is a workaround there:

a. Use the File Explorer to open "C:\Program Files (x86)\gnucash\bin\"

b. If there is a file named "libxmlsec1.dll" present, but no file named 
"libxmlsec.dll", then rename file "libxmlsec1.dll" to the name 
"libxmlsec.dll" (without the trailing "1").

I do not use GnuCash on Windows, so I have no experience with this 
problem. I only know what I read. If you ask this list directly about 
how to work around this bug, Windows users may be able to give you 
better help.

I hope this helps,
      —Jim DeLaHunt