Errors when closing KMyMoney

[aga]

On 27/02/16 17:18, Jack wrote:
> On 2016.02.27 11:35, Thomas Spuhler wrote:
>> On Friday, February 26, 2016 01:03:26 PM Jack wrote:
>> > On 2016.02.26 12:22, Thomas Spuhler wrote:
>> > > On Friday, February 26, 2016 11:54:29 AM aga wrote:
>> > > > On 25/02/16 23:13, Thomas Spuhler wrote:
>> > > > > On Wednesday, February 24, 2016 07:23:15 PM Thomas Baumgart
>> wrote:
>> > > > >> On Tuesday 23 February 2016 14:58:24 Thomas Spuhler wrote:
>> > > > >>> I got again an error (crash) when exiting KMyMoney
>> > >>>>>
>> > >>>>> Unknown account id 'A000101' in file
>> > >>>>>
>> /home/iurt/rpmbuild/BUILD/kmymoney-4.7.2/kmymoney/mymoney/storage/mymo
>> > >>>>> ne
>> > >>>>> ys eq accessmgr.cpp line 146
>> > >>>>
>> > >>>> Hmm, looks like the application is trying to access an account
>> > >>>> that is not present (anymore).
>> > >>>>
>> > >>>> Can you try to take a look at the file (it's compressed XML) and
>> > >>>> see where the pattern A000101 is referenced?
>> > >>
>> > >> I'm pretty certain Thomas was referring to your data file, rather
>> > >> than the source code, as he wanted you to search for an account id
>> > >> 'A000101' which, it is hoped, will be found in your data file
>> > >> (xxx.kmy).
>> > >
>> > > Allan, I don't think I have such a file, but found the information in
>> > > the database file This is the line in table  kmmAccounts
>> > >
>> > >
>> ('A000100',NULL,'A000098',NULL,NULL,'2010-12-19',NULL,'12','Income','N','S
>>
>> > > hort
>> > >
>> Term',NULL,'USD','0/1','0',0),('A000101',NULL,'AStd::Income',NULL,'2016-0
>> > > 2-23
>> > I don't think we knew you were using a database and not the file
>> > backend.  It might help if you did a "Save As" and save as a regular
>> > KMyMoney file, such as kmm.kmy.  Then rename that file to kmm.xml.gz
>> > and gunzip it.  That will give you the XML file we have been talking
>> > about.
>> >
>> > There is something funny in the line you give above, as it seems like a
>> > record and a half.
>> The e-mail just makes two lines out of one


> It's not an issue of physical lines, it is about partial or complete
> records, since it apparently comes from a database query.  If you look,
> it starts with ('A000100', and there is a matching ) followed by a comma
> and then ('A000101', but no closing parenthesis.  That second part is
> the beginning half of the record you post below from the file.

<snip>
Quite recently, I saw an example of a user's file where the formatting 
had gone awry.

In that case, it was related to payee names which included the '<' or 
'>' character.  These characters are used as delimiters in XML files, 
and the extra, unexpected ones were screwing the parsing of the file on 
input. [1] It wouldn't do any harm to check your XML file in this area, 
although it is a bit of a long shot.  It could potentially affect fields 
other than payee name, too.

[1] The characters "<" and "&" are key syntax markers and may never 
appear in content outside a CDATA section.

Allan

>> > We still need to see the rest
>> > of that line, and any other line in the file that refers to that
>> > account.  The easiest way is to just do "grep A000101 kmm.xml" once you
>> > have decompressed the saved file.
>> >
>> > Jack
>>
>> I get 256 lines, all except 2 have data I cannot post.
> You could post them if you remove or replace the sensitive information.
> I assume all those lines are deposits of earned interest into that
> account or withdrawals or transfers out.  However, I don't think that is
> necessary to post them here.  The original error message you posted was
> "Unknown account id 'A000101'" and that account is clearly present in
> the file.
>
>> These are the first two lines:
>>    <SUBACCOUNT id="A000101"/>
>>   <ACCOUNT currency="USD" description="" parentaccount="AStd::Income"
>> opened="2010-12-19" number="" lastmodified="2016-02-23" type="12"
>> id="A000101"
>> lastreconciled="" institution="" name="Interest Earned">
>
> Are you still getting that original error?  Is it the same using the
> database and using the file?  If so, then the next step would be to do a
> save as, saving as an anonymized file.  This removes all the identifying
> information, and uses random amounts in all the transactions.  If you
> still get the error with that file, then you could post it without given
> away any private information.  However, I would wait until one of the
> developers responds before doing that.
>
> Jack