Jonathan,

Like I said on Thursday, that file is probably corrupted so you should use one 
of the backup files. I explained the naming scheme for those, it’s quoted 
below. Make sure that you understand it because after you make sure that you 
can open one of them you’ll want to rename it for future use; File>Save As is 
an easy way to do that.

Since you can’t get the file to open without crashing there’s no way to recover 
it.

Yes, you can replay log files to recover your basic transactions (business 
module information isn’t in them) using File>Import>Replay GnuCash Log File. 
Those are named similar to backup files except the final file extension is .log 
instead of .gnucash. I recommend that you do that one at a time and do a save 
after each one.

If you’re willing I’d like to examine your corrupted file to see if I can 
figure out what might have gone wrong. You can send it to me directly. I will 
of course not share it and delete it as soon as I’ve finished examining it.

Regards,
John Ralls

> On Dec 21, 2024, at 11:58 AM, Jonathan A. Cohen <jco...@urgrad.rochester.edu> 
> wrote:
> 
> John,
> 
> The crashing happens very quickly, either when opening the file (the 
> application never appears after the splash screen) or soon after when 
> entering a transaction.
> 
> I have tried uninstalling and installing 5.8, 5.9, and 5.10 and the behavior 
> is the same.
> 
> The oldest trace file (gnucash.trace.2J8JY2.log) shows modification date 
> 12/14, which based upon this string is after the issue started.  I have 
> enclosed it in case it helps.  I can grab them all and upload if that would 
> help.
> 
> Is there any way to identify the corruption in the file?  And fix it?  Or 
> should I open an older file from before the first crash?  I seem to recall 
> that I can then import the log files upto date to redo the transactions.  Or 
> will that cause the corruption to reappear.
> 
> This is a very serious issue, as I use GnuCash to manage my cash flow.
> 
> Thank you,
> Jonathan
> 
> PS  I wonder if there is a reason that you use the Temp AppDate folder 
> instead of dropping traces into a dedicated folder?  It would seem easier to 
> have them all in one place separate from other files put in there.
> ________________________
> Jonathan A. Cohen
> jco...@urgrad.rochester.edu
> 
> http://www.linkedin.com/in/jonathanaaroncohen
> 
> 
> 
> On Thu, Dec 19, 2024 at 5:26 PM John Ralls <jra...@ceridwen.us> wrote:
> By happened again do you mean that GnuCash crashed promptly after opening the 
> file? That version of the file is probably dead so use the backups. Be 
> mindful that when you save GnuCash renames the file, adding a timestamp, then 
> writes a new file with the old name. For example when you save 
> my_file.gnucash it will be renamed to my_file.gnucash.20241219141340.gnucash; 
> if you then open that with File>Open, make changes and save it will rename it 
> to my_file.gnucash.20241219141340.gnucash.20241219141447.gnucash and so on. 
> You might want to work from copies with different names to make cleaning up 
> easier.
> 
> It’s very likely that whatever was the original problem in 5.9 persists in 
> 5.10 so you might need to revert to 5.8. 
> 
> On Windows we append short random strings to trace files so that there’s a 
> history of them. Can you look through your collection for the last 2 weeks 
> and see when those errors started showing up? In the sessions from last week 
> where the register went blank do the tracefiles show the same errors or 
> different ones?
> 
> Regards,
> John Ralls
> 
> > On Dec 19, 2024, at 07:59, Jonathan A. Cohen <jco...@urgrad.rochester.edu> 
> > wrote:
> > 
> > Thanks.  I updated to 5.10 and it happened again.
> > 
> > 
> > ________________________
> > Jonathan A. Cohen
> > 26 Patriots Drive
> > Canton, MA 02021
> > 781-929-8204
> > jco...@urgrad.rochester.edu
> > 
> > http://www.linkedin.com/in/jonathanaaroncohen
> > 
> > 
> > 
> > On Thu, Dec 19, 2024 at 8:52 AM David Carlson <david.carlson....@gmail.com>
> > wrote:
> > 
> >> Hopefully one of the developers will find that useful.  Now that release
> >> 5.10 is out they may have time to look at it.
> >> 
> >> 
> >> 
> >> On Thu, Dec 19, 2024 at 7:13 AM Jonathan A. Cohen <
> >> jco...@urgrad.rochester.edu> wrote:
> >> 
> >>> * 13:54:00 ERROR <gnc.io> [gnc_xml_set_data()] Unhandled tag: trn:id
> >>> * 13:54:00 ERROR <gnc.io> [dom_tree_generic_parse()] gnc_xml_set_data
> >>> failed
> >>> * 13:54:00 ERROR <gnc.io> [dom_tree_handlers_all_gotten_p()] Not defined
> >>> and it should be: trn:id
> >>> * 13:54:00 ERROR <gnc.io> [dom_tree_generic_parse()] didn't find all of
> >>> the expected tags in the input
> >>> * 13:54:00 ERROR <gnc.io> [gnc_xml_set_data()] Unhandled tag: trn:id
> >>> * 13:54:00 ERROR <gnc.io> [dom_tree_generic_parse()] gnc_xml_set_data
> >>> failed
> >>> * 13:54:00 ERROR <gnc.io> [dom_tree_handlers_all_gotten_p()] Not defined
> >>> and it should be: trn:id
> >>> * 13:54:00 ERROR <gnc.io> [dom_tree_generic_parse()] didn't find all of
> >>> the expected tags in the input
> >>> * 13:54:00 ERROR <gnc.engine> void
> >>> qof_collection_insert_entity(QofCollection*, QofInstance*): assertion
> >>> 'col->e_type == ent->e_type' failed
> >>> * 13:54:00 ERROR <gnc.backend.file.sixtp> Tag <trn:id> not allowed in
> >>> current context.
> >>> * 13:54:00 ERROR <gnc.io> [gnc_xml_set_data()] Unhandled tag: trn:slots
> >>> * 13:54:00 ERROR <gnc.io> [dom_tree_generic_parse()] gnc_xml_set_data
> >>> failed
> >>> * 13:54:01 ERROR <gnc.io> [gnc_xml_set_data()] Unhandled tag: trn:slots
> >>> * 13:54:01 ERROR <gnc.io> [dom_tree_generic_parse()] gnc_xml_set_data
> >>> failed
> >>> * 13:54:01 ERROR <gnc.io> [gnc_xml_set_data()] Unhandled tag:
> >>> split:account
> >>> * 13:54:01 ERROR <gnc.io> [dom_tree_generic_parse()] gnc_xml_set_data
> >>> failed
> >>> * 13:54:01 ERROR <gnc.io> [dom_tree_handlers_all_gotten_p()] Not defined
> >>> and it should be: split:account
> >>> * 13:54:01 ERROR <gnc.io> [dom_tree_generic_parse()] didn't find all of
> >>> the expected tags in the input
> >>> * 13:54:01 ERROR <gnc.engine> int xaccTransGetSplitIndex(const
> >>> Transaction*, const Split*): assertion 'trans && split' failed
> >>> * 13:54:01 ERROR <gnc.io> [gnc_xml_set_data()] Unhandled tag: trn:slots
> >>> * 13:54:01 ERROR <gnc.io> [dom_tree_generic_parse()] gnc_xml_set_data
> >>> failed
> >>> * 13:54:01 ERROR <gnc.io> [gnc_xml_set_data()] Unhandled tag:
> >>> split:reconcile-date
> >>> * 13:54:01 ERROR <gnc.io> [dom_tree_generic_parse()] gnc_xml_set_data
> >>> failed
> >>> * 13:54:01 ERROR <gnc.engine> gboolean
> >>> qof_instance_get_destroying(gconstpointer): assertion
> >>> 'QOF_IS_INSTANCE(ptr)' failed
> >>> * 13:54:01 ERROR <gnc.engine> int xaccTransGetSplitIndex(const
> >>> Transaction*, const Split*): assertion 'trans && split' failed
> >>> 
> >>> 
> >>> ________________________
> >>> Jonathan A. Cohen
> >>> 26 Patriots Drive
> >>> Canton, MA 02021
> >>> 781-929-8204
> >>> jco...@urgrad.rochester.edu
> >>> 
> >>> http://www.linkedin.com/in/jonathanaaroncohen
> >>> 
> >>> 
> >>> 
> >>> On Wed, Dec 18, 2024 at 4:55 PM David Carlson <
> >>> david.carlson....@gmail.com> wrote:
> >>> 
> >>>> Jonathan,
> >>>> 
> >>>> What does the gnucash.trace file under "This PC > OS(C:) > Users >
> >>>> [yourusername] > AppData > Local > Temp" report?
> >>>> 
> >>>> 
> >>>> 
> >>>> On Wed, Dec 18, 2024 at 12:56 PM Jonathan A. Cohen <
> >>>> jco...@urgrad.rochester.edu> wrote:
> >>>> 
> >>>>> That worked for about a day.  Today it failed again.  Starting Gnu
> >>>>> Cash, the splash screen shows progress and when it is done, the 
> >>>>> application
> >>>>> stops.  The event viewer:
> >>>>> 
> >>>>> Faulting application name: gnucash.exe, version: 5.9.0.0, time stamp:
> >>>>> 0x66f9947e
> >>>>> Faulting module name: libgnc-engine.dll, version: 0.0.0.0, time stamp:
> >>>>> 0x66f9919f
> >>>>> Exception code: 0xc0000005
> >>>>> Fault offset: 0x000be263
> >>>>> Faulting process id: 0x0x95B4
> >>>>> Faulting application start time: 0x0x1DB517E318B3737
> >>>>> Faulting application path: C:\Program Files
> >>>>> (x86)\gnucash\bin\gnucash.exe
> >>>>> Faulting module path: C:\Program Files
> >>>>> (x86)\gnucash\bin\libgnc-engine.dll
> >>>>> Report Id: cae87769-5274-490a-b3a1-bff8175bf36b
> >>>>> Faulting package full name:
> >>>>> Faulting package-relative application ID:
> >>>>> 
> >>>>> Anyone have any ideas?
> >>>>> 
> >>>>> 
> >>>>> ________________________
> >>>>> Jonathan A. Cohen
> >>>>> 26 Patriots Drive
> >>>>> Canton, MA 02021
> >>>>> 781-929-8204
> >>>>> jco...@urgrad.rochester.edu
> >>>>> 
> >>>>> http://www.linkedin.com/in/jonathanaaroncohen
> >>>>> 
> >>>>> 
> >>>>> 
> >>>>> On Tue, Dec 17, 2024 at 11:10 AM David Carlson <
> >>>>> david.carlson....@gmail.com> wrote:
> >>>>> 
> >>>>>> That would be something to try.  I had a problem with a different
> >>>>>> application where the recommended procedure was to use the Windows
> >>>>>> Add/Remove programs feature to remove the program, then REBOOT the 
> >>>>>> computer
> >>>>>> and verify that certain folders had also been removed before 
> >>>>>> re-installing
> >>>>>> the program.
> >>>>>> 
> >>>>>> 
> >>>>>> 
> >>>>>> On Tue, Dec 17, 2024 at 8:07 AM Jonathan A. Cohen <
> >>>>>> jco...@urgrad.rochester.edu> wrote:
> >>>>>> 
> >>>>>>> I am thinking maybe this got corrupted:  C:\Program Files
> >>>>>>> (x86)\gnucash\bin\libgnc-engine.dll
> >>>>>>> 
> >>>>>>> When upgrading, I think it does not fully remove all components, so I
> >>>>>>> did a full uninstall and reinstall.  Will monitor for future problems.
> >>>>>>> 
> >>>>>>> I anyone thinks I am off-base, please let me know.
> >>>>>>> 
> >>>>>>> 
> >>>>>>> ________________________
> >>>>>>> Jonathan A. Cohen
> >>>>>>> jco...@urgrad.rochester.edu
> >>>>>>> 
> >>>>>>> 
> >>>>>>> On Mon, Dec 16, 2024 at 6:59 PM Jonathan A. Cohen <
> >>>>>>> jco...@urgrad.rochester.edu> wrote:
> >>>>>>> 
> >>>>>>>> I captured the following from Windows event manager:
> >>>>>>>> 
> >>>>>>>> Faulting application name: gnucash.exe, version: 5.9.0.0, time
> >>>>>>>> stamp: 0x66f9947e
> >>>>>>>> Faulting module name: libgnc-engine.dll, version: 0.0.0.0, time
> >>>>>>>> stamp: 0x66f9919f
> >>>>>>>> Exception code: 0xc0000005
> >>>>>>>> Fault offset: 0x000be263
> >>>>>>>> Faulting process id: 0x0x9964
> >>>>>>>> Faulting application start time: 0x0x1DB5010DDA488C8
> >>>>>>>> Faulting application path: C:\Program Files
> >>>>>>>> (x86)\gnucash\bin\gnucash.exe
> >>>>>>>> Faulting module path: C:\Program Files
> >>>>>>>> (x86)\gnucash\bin\libgnc-engine.dll
> >>>>>>>> Report Id: 3044f93f-b0fe-42c2-9705-e6a0405e0cdb
> >>>>>>>> Faulting package full name:
> >>>>>>>> Faulting package-relative application ID:
> >>>>>>>> 
> >>>>>>>> 
> >>>>>>>> 
> >>>>>>>> ________________________
> >>>>>>>> Jonathan A. Cohen
> >>>>>>>> 26 Patriots Drive
> >>>>>>>> Canton, MA 02021
> >>>>>>>> 781-929-8204
> >>>>>>>> jco...@urgrad.rochester.edu
> >>>>>>>> 
> >>>>>>>> http://www.linkedin.com/in/jonathanaaroncohen
> >>>>>>>> 
> >>>>>>>> 
> >>>>>>>> 
> >>>>>>>> On Sat, Dec 14, 2024 at 7:14 PM Jonathan A. Cohen <
> >>>>>>>> jco...@urgrad.rochester.edu> wrote:
> >>>>>>>> 
> >>>>>>>>> Thank you, David. I'm not having any resources issues.
> >>>>>>>>> 
> >>>>>>>>> __________________
> >>>>>>>>> Jonathan Cohen
> >>>>>>>>> +1-781-929-8204
> >>>>>>>>> 
> >>>>>>>>> On Sat, Dec 14, 2024, 6:14 PM David Carlson <
> >>>>>>>>> david.carlson....@gmail.com> wrote:
> >>>>>>>>> 
> >>>>>>>>>> Jonathan,
> >>>>>>>>>> 
> >>>>>>>>>> One of the possible causes of such behavior is inadequate
> >>>>>>>>>> resources.  Are you having issues with other programs, 
> >>>>>>>>>> particularly web
> >>>>>>>>>> browsers?
> >>>>>>>>>> 
> >>>>>>>>>> On Sat, Dec 14, 2024 at 3:21 PM Jonathan A. Cohen <
> >>>>>>>>>> jco...@urgrad.rochester.edu> wrote:
> >>>>>>>>>> 
> >>>>>>>>>>> Upgraded to 5.9 last week.  After a few days a behavior started:
> >>>>>>>>>>> the view
> >>>>>>>>>>> would suddenly no longer show the transactions in any account.
> >>>>>>>>>>> Save and
> >>>>>>>>>>> restart worked.  As the days went on, this behavior happened
> >>>>>>>>>>> faster after
> >>>>>>>>>>> opening.
> >>>>>>>>>>> 
> >>>>>>>>>>> Today, opened GnuCash and got the warning that the file is
> >>>>>>>>>>> locked.  Open
> >>>>>>>>>>> anyways and the opening proceeded.  But once the program start
> >>>>>>>>>>> progress bar
> >>>>>>>>>>> completed, it disappeared.  The file is locked again.  Opening
> >>>>>>>>>>> wayway does
> >>>>>>>>>>> not work.  The program will not open now at all.
> >>>>>>>>>>> 
> >>>>>>>>>>> I tried backing out to 5.8 but it still won't open.  Upgrade back
> >>>>>>>>>>> to 5.9
> >>>>>>>>>>> same behavior.
> >>>>>>>>>>> 
> >>>>>>>>>>> Windows 11.
> >>>>>>>>>>> 
> >>>>>>>>>>> 
> >>>>>>>>>>> ________________________
> >>>>>>>>>>> Jonathan A. Cohen
> >>>>>>>>>>> jco...@urgrad.rochester.edu
> >>>>>>>>>>> _______________________________________________
> >>>>>>>>>>> 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.
> >>>>>>>>>>> 
> >>>>>>>>>> 
> >>>>>>>>>> 
> >>>>>>>>>> --
> >>>>>>>>>> David Carlson
> >>>>>>>>>> 
> >>>>>>>>> 
> >>>>>> 
> >>>>>> --
> >>>>>> David Carlson
> >>>>>> 
> >>>>> 
> >>>> 
> >>>> --
> >>>> David Carlson
> >>>> 
> >>> 
> >> 
> >> --
> >> David Carlson
> >> 
> > _______________________________________________
> > 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.trace.2J8JY2.log>

_______________________________________________
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