Just a quick update. Situation seems to have been resolved after several reboots of the laptop. Not really sure what has happened I suspect that the key file had somehow been locked, preventing Keepass from accessing it. Anyway, all is well now!!! Keith
Thanks for taking a look. My gut instinct tells me its a key file access/permission error although looking at the folder/file permissions there shouldn't be a problem. As to the cause, it may be due to a recent Windows update (W10, x64) which happened around the same time as the issue. The desktop is also W10 but x32 so that may be why it's not a problem on the desktop. There are no issues on Android either via my Samsung S7 using Keepass2Android. Keith
Thanks for taking a look. My gut instinct tells me its a key file access/permission error although looking at the folder/file permissions there shouldn't be a problem. As to the cause, it may be due to a recent Windows update (W10, x64) which happened around the same time as the issue. The desktop is also W10 but x32 so that me be why it's not a problem on the desktop. There are no issues on Android either via my Samsung S7 using Keepass2Android. Keith
Double check the path and determine that the file does exist at the specified location The database file (.kdbx) has been selected from the list of files generated via the 'Open from Cloud Drive' dialogue box linked to the appropriate Google Account so it must exist. The resulting file name is also identical to the .kdbx file loaded correctly from the desktop. The key file (.key) has also been selected from the dialogue box created via 'Open Database' dialogue which automatically loads after selecting...
Double check the path and determine that the file does exist at the specified location The database file (.kdbx) has been selected from the list of files generated via the 'Open from Cloud Drive' dialogue box linked to the appropriate Google Account so it must exist. The resulting file name is also identical to the .kdbx file loaded correctly from the desktop. The key file (.key) has also been selected from the dialogue box created via 'Open Database' dialogue which automatically loads after selecting...
Double check the path and determine that the file does exist at the specified location The database file (.kdbx) has been selected from the list of files generated via the 'Open from Cloud Drive' dialogue box linked to the appropriate Google Account so it must exist. The resulting file name is also identical to the .kdbx file loaded correctly from the desktop. The key file (.key) has also been selected from the dialogue box created via 'Open Database' dialogue which automatically loads after selecting...
(Apologies for duplicate post - also now posted it in Help forum but couldn't figure out how to delete it from this forum after incorrectly posting it here - admins please delete from Open Discussion forum if apporpriate) Hi, I have a keepass database stored in the cloud on Google Drive. It uses a Master Key and a key file stored on each device locally. I have been using keepass flawlessly between my desktop, laptop and Android mobile (using Keepass2Android) for several years. However, I tried to...
(Apologies for duplicate post - incorrectly posted it in Open Discussion but couldn't figure out how to delete it from there - admins please delete from Open Discussion if apporpriate) Hi, I have a keepass database stored in the cloud on Google Drive. It uses a Master Key and a key file stored on each device locally. I have been using keepass flawlessly between my desktop, laptop and Android mobile (using Keepass2Android) for several years. However, I tried to open the database from my laptop today...