Problem opening KMM file

[Brendan Coupe]

Thanks. The transactions are from 2009. The investment account they are 
in is closed. When I reopen it and try to open any of the investments in 
the account I get:

KMyMoney does not support to edit transaction that reference closed 
accounts. This could be worded better:

How about "KMyMoney does not support editing transactions that reference 
closed accounts."

I have no idea how to fix this.

grep  A000432 MyMoney.kmy  | grep '<ACCOUNT>'

returns nothing.

grep  A000432 MyMoney.kmy  | wc

returns 9 lines but there are many more investments in the brokerage 
account than 9. It appears that every equity and CD in that account 
returns the same error.

This is frustrating since I have 20 years of data that I can no longer 
access. It passes the consistency check with the August version. It 
seems like it should have failed the consistency check with some 
guidance on how to fix it before KMM refused to open the file.

**
*Brendan Coupe*
*3 at Coupe7.com*


On 2025-09-09 12:24 PM, Jack via KMyMoney-devel wrote:
> On 9/9/25 2:21 PM, Jack via KMyMoney-devel wrote:
>> On 9/9/25 2:08 PM, Brendan Coupe via KMyMoney-devel wrote:
>>> When I compile either the 5.2 or the master branch I get the 
>>> following error when trying to open my file:
>>>
>>> Corrupted data: transaction '', split 'S0002' references unknown 
>>> account id 'A000432' 
>>> /usr/local/src/kmm/kmymoney-2025.09.09-11.47.31-GIT-MASTER/kmymoney/plugins/xml/mymoneyxmlreader.cpp:771
>>>
>>> Since my file is encrypted, the first thing I tried was decrypting 
>>> the file. I got the same error. When I switch back to the version I 
>>> compiled on August 21, the file opens as expected. The first time 
>>> this happened was about a week ago but I didn't try decrypting the 
>>> file first until today.
>>>
>>> Something in the past few weeks seems to have caused this problem. 
>> I think this has been reported by someone else recently, but can't 
>> currently find the reference. 
> https://discuss.kde.org/t/kmm-5-2-1-cannot-open-file/39428
>> It seems to be due to a new check that has been added recently.  What 
>> you can do is grep for that account number in your data file after 
>> decrypting and find what transaction contains that split.  Then open 
>> that transaction in an older working version and check if the 
>> category is valid.  If not, change it to a valid Category.  You may 
>> then find a different transaction with the same problem, so you will 
>> need to repeat the process.  Apparently at some point in the past, it 
>> was possible to delete a Category without deleting or reassigning all 
>> transations/splits which referred to it.