Menu

#336 Corrupted database

v1.0_(example)
closed
5
2012-10-10
2012-03-02
No

Seem to have a corrupted Password Safe Database and really cant afford
loosing all the passwords. HELP!

Would appreciate any advice or tip on how to access the database.

The version of the PS is 3.17 and I cant open the psafe3 file nor the
.ibak file.

Was turning of the laptop using the hibernate option and instead of
powering off the laptop started booting up so I powered it off,
really big misstake

When trying to open PS i get error message - incorrect passkey, not a
passwordsafe database, or a corrupt database.

Im totally certain that the correct password is beeing used.

If not beeing able to repair the database file... is their any other
way of accessing the information in the file?

The information/passwords in the database is totally critical for me
to access as there are passwords to systems that arent
possible for me to change/recreate.

Been running error-checking on the harddrive but still the same issue.

Also renamed the -ibak file to .psafe3, cretaed a new database and tried to make a restore, downloaded thelates version on another computer using the old database but still no luck.

Any tip to get me in the right direction is VERY appreciated!!!

Discussion

  • Patrik Delén

    Patrik Delén - 2012-03-02

    Also.... .ibak and .psafe3 file has the same size.

    Kind regards
    Patrik

     
  • Rony Shapiro

    Rony Shapiro - 2012-03-02

    Hi Patrik,

    3.17 is a bit old. My first thought was to suggest you download the latest version (3.28) and try opening your database with that, but if you get an error message after entering the password, I doubt that would help.
    If the size of your files is relatively small (a couple of hundred bytes or so), then I'm afraid there's not much I can do. You might want to see if you have another copy of your database, perhaps on a different machine.
    If the size of the file is larger, then perhaps we can recover some data - contact me directly at
    ronys at users dot sourceforge dot net.

    Rony

     
  • DrK

    DrK - 2012-03-02

    Sorry but my comments may not help you now but might later. As Rony has said, if the size if small, then it might just be an empty database.

    We have done a lot of work on making PWS handle unexpected closures in the 11 releases since the one you used but we cant force people to check for new versions and upgrade.

    You say that "The information/passwords in the database is totally critical" for you - so you must have a backup copy somewhere else - another PC or at least a USB stick! Mechanical things fail - hard disks are mechanical - they do fail. Viruses can wipe files (not that I am suggesting that happened this time), disk defragmenters can corrupt files - there are all sorts of ways data can get lost, damaged or changed. The important rule is have multiple backups of all your important data somewhere safe and also to take regular backups.

    When you said you "Also renamed the -ibak file to .psafe3", I am hoping that you copied it and renamed the copy so that anything in the original intermediate backup file was saved?

    Lastly, as I have said, we have done a lot of work on trying to catch unexpected closing of the PC/laptop. We can't say that we have caught every possible circumstance. However, this will be true of any application you may run - even other password managers. Bad things do happen. The important point is to keep backups of your important/critical data in more than one place!

    David

     
  • Rony Shapiro

    Rony Shapiro - 2012-10-10
    • status: pending --> closed
    • milestone: --> v1.0_(example)
     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.