Menu

Syncronize skipping entry

Tom Giles
2016-06-02
2016-06-02
  • Tom Giles

    Tom Giles - 2016-06-02

    I am running KP 2.30 on Windows 10 and I had a Entry dissapear.
    It was not in the Recycle Bin but fortunately had the Entry in another file

    I tried to Syncronize the two files but it did not pick it up. I created another new
    Entry and reran the Syncronize and it picked it up but not the missing one.

    Is there a configuration or setting I should look for in the Entry to cause it to skip?

    Thanks
    tomzak

     
  • wellread1

    wellread1 - 2016-06-02

    Synchronization does not require configuration. It is possible that entry was picked up you just didn't find it.

    Was the entry that wasn't picked up newly created or a pre-existing one?
    Was the database that you were synchronizing with, once related to the database that contains the entry that wasn't picked up?

    What version of KeePass are you using?

    Can you clarify what do you mean by not picked up? Was it deleted from both databases? Did you search both databases for the UUID of entry? To search for a UUID:

    1. display the UUID: select UUID in 'View>Configure Columns...'
    2. Open both databases
    3. Copy the UUID of the entry that you are trying to synchronize by double clicking on the UUID
    4. paste it into the quick search field and execute the quick search in each database.
     
  • T. Bug Reporter

    T. Bug Reporter - 2016-06-02

    Every entry you create has a UUID (basically, a randomly generated serial number) assigned to it when it is created, and duplicating the other information in the record does not duplicate the UUID. If you delete a record, even if you remove it from the Recycle Bin, a record of that UUID is still kept in the database, so that if you sync with an older copy of the file, the old records that you've since deleted won't get recopied to the newer file - and the fact that you've deleted those records gets propagated to the old file.

    If you've successfully reconstructed the info in that record, my suggestion would be to just forget that the old record existed.

     

Log in to post a comment.

MongoDB Logo MongoDB