Sorry, John, I’m floundering a bit here. Opening with the debug switch doesn’t provide anything different visually so I’m assuming I need to check the trace file. What’s that file called and where does it live? The only files with trace in the name I can find are trace.go and trace.scm, but they are both old.
From: John Ralls <jra...@ceridwen.us> Sent: 14 May 2018 15:52 To: Anthony Marrian <anth...@gardensmontessori.com> Cc: gnucash-user@gnucash.org Subject: Re: [GNC] There was an error parsing the file On May 14, 2018, at 4:41 AM, Anthony Marrian <anth...@gardensmontessori.com<mailto:anth...@gardensmontessori.com>> wrote: GnuCash 3.1, Windows 10 Pro 64bit. Please advise how to proceed? Look in the trace file [1] for an error. That may provide a clue about where the problem is. It’s most likely a date outside of the years 1400-9999; 208 or 218 instead of 2018 seems to be a popular typo. If there’s no error or not enough context to understand what was getting loaded when the error occurred, start GnuCash 3.1 from the command line with the debug option enabled: “C:\Program Files (x86)\gnucash\bin\gnucash” --debug That will insert a lot more detail about what GnuCash is doing and should help you figure out where to look for the problem in the file. Now reinstall the 2.6.x of your choice and open the file. Look for the error based on your analysis of the trace file. Regards, John Ralls [1] https://wiki.gnucash.org/wiki/Tracefile _______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
