Since this morning, I am not able to login to my portfolio. I get the following error code:
Wed Aug 27 11:06:07 CEST 2025 Unable to add transaction ‘Feb 5, 2025 TRANSFER_IN USD 1.57 IBKR (USD)’ to account ‘IBKR (CHF)’ (uuid 7160c6bf-4f6d-4f38-95fc-d801e1b3c345): CHF <> USD
java.lang.IllegalArgumentException: Unable to add transaction ‘Feb 5, 2025 TRANSFER_IN USD 1.57 IBKR (USD)’ to account ‘IBKR (CHF)’ (uuid 7160c6bf-4f6d-4f38-95fc-d801e1b3c345): CHF <> USD
at name.abuchen.portfolio.model.Account.addTransaction(Account.java:142)
at name.abuchen.portfolio.model.AccountTransferEntry.insert(AccountTransferEntry.java:125)
at name.abuchen.portfolio.model.ProtobufWriter.loadTransactions(ProtobufWriter.java:428)
at name.abuchen.portfolio.model.ProtobufWriter.load(ProtobufWriter.java:126)
at name.abuchen.portfolio.model.ClientFactory$Decryptor.load(ClientFactory.java:366)
at name.abuchen.portfolio.model.ClientFactory.load(ClientFactory.java:584)
at name.abuchen.portfolio.ui.editor.LoadClientThread.run(LoadClientThread.java:34)
My configuration is the following:
Version: 0.78.1 (August 2025)
Platform: win32, x86_64
Java: 21.0.5+11-LTS, Azul Systems, Inc.
I cannot modify my xml file from a text editor because it is encrypted by a password.
I have the same problem with the backup file.
I reinstalled the software but without any success. I also tried to install an older version (0.71) but also without any success.
When even your backup file isn’t working, the only feasible option remaining is eclipse.
Therefore, you need a running dev. environment.
Or @AndreasB has some spear time, but in this case, you need to send him the whole file via email.
@AndreasB we might need to think about a solution for issues with encrypted files… Probably something like a mandatory validity check before a file gets saved. At least for the encrypted onces.
There appears to be an invalid transaction in the data. And PP ist not handling this nicely and stops instead of skipping this transaction.
First, I have created a version which skips this transaction and should continue. Download it, unzip it somewhere, open your file, save your file again. The file should then be fixed. If not, let me know here. I suggest not to continue to use this version from PP (easier for the online updates). The next version will then contain a more elaborate fix.
Second, I would be super interested in to learn more how this transaction was created. It is a transfer on 5 February. Do you remember? Did you create it manually? Was it the IBFlex importer? Because I would like to fix the bug that caused this situation…
Yep. We need to strengthen both - check before adding data and fail more nicely if reading bad data.
Thanks a lot for the fast fix. Your version worked to recover the inaccessible portfolio.
This transaction has probably been done manually. I tried to upload the Flex query previously created (I have done it once only) and discovered that three transactions were not imported. I probably tried to enter it manually to correct something that was not well imported from IBKR but you may have corrected it already in the meantime. This specific transaction was about some interests payment in USD but converted automatically to CHF…
I have a theory where such transactions could be created through a Flex query import. But in your case, that would have to have happened in your last PP session (= decrypt the file with password and then close PP). I am not sure how long you keep PP running…
I’ll do some more investigations.
P.S.: @Sn1kk3r5 Thinking about it, I am pretty sure that the “backup-after-open” file would also still work. It is a filesystem copy of the last file that was successfully opened. That file cannot contain the bad transaction. The fix is of course better because as it has fewer lost changes.
I didn’t have any “backup-after-open” file, only a “backup” one. Maybe because I did not reopen the file between the time I created all the transactions and the time I could not open it anymore because of the corrupted transaction?