Mac upgrade, "There was an error parsing the file ..."
Geert Janssens
janssens-geert at telenet.be
Fri Jun 18 02:44:43 EDT 2010
On Friday 18 June 2010, David Dannemiller wrote:
> On Jun 17, 2010, at 8:25 AM, David Reiser wrote:
> > You probably have a corrupt scheduled transaction and have "Run when data
> > file opened" under Since Last Run under Scheduled transactions
> > preferences. Turn that off, open the data file again, and examine your
> > scheduled transactions for obvious errors. There might be something
> > listed in the gnucash.trace file that could guide you, too. You shouldn't
> > have to recreate all your SX's, but you'll have to look for the one or
> > two that are choking the new version.
>
> I didn't have much time to work on this tonight, but I did look at the
> trace file. Two questions:
>
> 1) The trace file is absolutely huge. It looks like it has entries for
> every account and transaction. Is that expected?
>
Yes, that's normal. The sql backend still has debug logging enabled for now.
So you will get such a detailed log in /tmp/gnucash.trace.
This should be disabled before we go 2.4.
> 2) If my problem is an corrupt scheduled transaction, what is the signature
> I should look for in the trace file?
>
No idea, I'm afraid.
Geert
More information about the gnucash-user
mailing list