#1035 Database corrupted in 2.20

closed
nobody
None
5
2012-09-23
2012-09-23
No

I recently switched to 2.20 and since then have had the database corrupted twice. After the first time, I restored the database. A few days later it was corrupted again and I restored it again, then rolled back to 2.19. After rolling back to 2.19 it has been stable so far.

I am keeping the database on a Dropbox folder but I don't have any other location where i edit the database. Also, the Keepass 2.20 database is no longer readable from my Keepass app on the (Android) phone. I'm not sure that this is a related problem but I just mention it here.

It took about a week of use (and 3 or 4 saves) for the database to corrupt.

Discussion

  • Dominik Reichl

    Dominik Reichl - 2012-09-23

    A KeePassDroid update is required to properly support KDBX files created by KeePass 2.20.

    Best regards
    Dominik

     
  • Dominik Reichl

    Dominik Reichl - 2012-09-23
    • status: open --> closed
     
  • Ronald Kunenborg

    Hi,

    I only added the keepassdroid mention as a related note, it's not the primary issue. The primary issue is that I switched to 2.20 and had my database corrupted twice in 9 days. But thanks for the heads-up on keepassdroid :)

     
  • Dominik Reichl

    Dominik Reichl - 2012-09-23

    I cannot reproduce the corruption issue and also cannot imagine what could cause it. If you find a way how to reproduce it, please post a sample database, your configuration file and detailed steps what you're doing.

    Thanks and best regards
    Dominik

     

Log in to post a comment.