gnucash dying

Dale Alspach alspach at math.okstate.edu
Sun Aug 1 16:59:55 EDT 2004


What I had was (in the uncompressed xml file) was some transactions that began like this:

<gnc:transaction version="2.0.0">
  <trn:id type="guid">9a84257ee45fb0050eb1e89fa7445cfa</trn:id>
  <trn:date-posted>
    <ts:date>2002-12-31 00:00:00 -0600</ts:date>
  </trn:date-posted>
  <trn:date-entered>
    <ts:date>2003-01-11 20:07:02 -0600</ts:date>
  </trn:date-entered>

instead of like this:

<gnc:transaction version="2.0.0">
  <trn:id type="guid">9a84257ee45fb0050eb1e89fa7445cfa</trn:id>
  <trn:currency>
    <cmdty:space>ISO4217</cmdty:space>
    <cmdty:id>USD</cmdty:id>
  </trn:currency>
  <trn:date-posted>
    <ts:date>2002-12-31 00:00:00 -0600</ts:date>
  </trn:date-posted>
  <trn:date-entered>
    <ts:date>2003-01-11 20:07:02 -0600</ts:date>
  </trn:date-entered>

I believe I saw in the archives that Linas had sent someone else a modification of the code
which would cause an identifier to be printed with the error message. I found mine by
diffing against an earlier uncorrupted file. Then I  wrote a quick and dirty perl script
to plug in the missing lines. I only have one currency so this was easy.

By the way I also these error messages for a while and then one day gnucash started
behaving weirdly. Shortly thereafter it basically would not do anything with the file.

Dale Alspach


More information about the gnucash-user mailing list