[GNC] Gnucash 3.7 freezes on any report after update from 2.6

[Adrien Monteleone]

Andrew,

See the wiki about obtaining a tracefile on Windows. Make sure to check the tracefile before re-starting GnuCash after a freeze. (it gets overwritten on subsequent runs)

Also, check the wiki for running GnuCash from the command line. (cmd.exe) Some errors or warnings are sent back to the command window that way.

You might not get anything of use, but both are worth checking out.

In the meantime...

Can you run other reports, such as P&L (Income Statement), Balance Sheet, Cash-Flow, et cetera?

Can you try running the offending reports and narrow down the expense accounts? Perhaps one or more has some sort of bad transaction info or is corrupted.

Try the Transaction Report on those (or various) expense accounts and see if it freezes as well.

The goal here is to narrow down which (or if all) reports choke, and then trying to find out what they are choking on.

Of course, make a backup of your datafile before proceeding.

You shouldn’t have to stay on 2.6 forever, and you shouldn’t need to make a new file. But this might take some sleuthing.

Regards,
Adrien

> On Oct 20, 2019 w43d293, at 12:51 PM, andrewTE <aos at aoselectronics.com> wrote:
> 
> I have just upgraded my 2.6 installation to 3.7 (Windows 10) and the gnucash
> would freeze immediately if I click on any report (there were 2 opened tabs
> by default as carried over from how I had it on 2.6). Thinking this was
> caused by incompatible reports, I managed to close them with "X" while they
> were not yet active, saved, reopened gnucash. Then I created brand new
> report. First time it worked but then as soon as I changed report to show 15
> items versus default, was it 8?, it froze. Second and subsequent time,
> trying to create ANY report immediately freezes the gnucash. Basically it is
> impossible to create any reports, at least not expense reports. I did wait a
> number of minutes (10+) but it just doesn't come back from complete freeze.
> 
> Is there a way around this? Or are my only options to either stick to 2.6
> forever or start a completely new file at the beginning of next year for new
> data and keep 2.6 installed on another PC (as they cannot coexist on
> windows?)? Keep in my that my existing file has more than 10 years of
> history of daily transactions so it's pretty large.
> 
> Thanks for any suggestions.