Menu

Can't open my DB with master password after Master Password change

Vadym
2019-03-19
2019-03-20
  • Vadym

    Vadym - 2019-03-19

    Hi.

    I store my DB at Google Drive. I use KeeAnywhere plugin for it. I changed Master Password and saved the DB, after that I could not open it from home computer neither with new not with old passwords. The rest of the options like Key File and Windows User Account were never used. I managed to resave the DB with new password from work computer and that time DB on home computer opened successfully with a new password.

    Then my laptop at work rebooted because of Windows updates and it seems I've lost access to my DB, can't open it with new or old passwords. I tried to save the file locally but it didn't help.

    Currently I have the next error (attached).

    Did someone experiences the same problems? Maybe you have some hints what can I try to restore access?

     
  • John Jones

    John Jones - 2019-03-19

    If you can open it from any device, just copy it manually to the problematic device.
    sounds like the DB got corrupted because of windows updates.

     
  • wellread1

    wellread1 - 2019-03-19

    The error message means that you are entering the wrong database master key. Your description also suggests that you are saving your database directly to Google Drive.

    It seems likely that you may have made a mistake changing the master key. Google Drive may have exacerbated the problem by creating conflicted copies of the database. If you can identify one or more conflicted copies of your database on Google Drive, you should be able to open one or more of them with one of the master keys that you have used recently.

    If you can't find a conflicted database copy that opens, you may be able to restore a recent version of your database and open it with the old master key. See https://support.google.com/drive/answer/2409045?co=GENIE.Platform%3DDesktop&hl=en.


    All cloud sync services work by replicating ordinary files1. Occasionally, the cloud sync service encounters different copies of the same file and cannot tell which is the "correct" copy. When this happens, the cloud sync service creates a conflict copy. A conflicted copy can occur when a user edits the same file at different locations at the "same time" or if a device is offline for a period e.g. if a computer reboots and there are changes pending.

    1. There are certain classes of documents that certain cloud services can handle more intelligently. These are typically file types developed by the respective cloud service provider, e.g. Google Docs, or MS Office.

    • KeePass can be configured to use with cloud services so that conflicted copies are not important. See the How it works description of the Synchronizing with Dropbox / other PC synchronization software. The described configuration can be implemented manually or with the example trigger.

    • Backup your database regularly. It is not a good idea to rely on features of free services for backup. See the KeePass Backup Wiki

     

    Last edit: wellread1 2019-03-19
  • Vadym

    Vadym - 2019-03-19

    Thank you for help, I managed to restore the previous version of the file using these instructions: https://support.google.com/drive/answer/2409045?co=GENIE.Platform%3DDesktop&hl=en

    None of the last versions (at least 7 of them) could have been opened either with new or old passwords. It seems that they have been broken somehow. Maybe there was some conflict because when I changed master password and saved the file to Google drive the same DB can have been opened on another machine with an old password.

    Anyway it was my fault, it was a stupid method of a master password changing . To restore everything I saved the last working copy locally, opened it with previous password, saved it into a new file, changed master password, uploaded to the Google Drive. Now it seems to work fine.

     
    • John Jones

      John Jones - 2019-03-20

      that's good, always keep multiple backups for these scenarios exactly.

       

Log in to post a comment.

MongoDB Logo MongoDB