Menu

"File in use" error when syncing on open

2015-01-05
2015-01-27
  • Giacomo Ciani

    Giacomo Ciani - 2015-01-05

    When I set "sync on open", about half of the time I get a error:
    "The process cannot access the file xxx because it is being used by another process".
    xxx is the temporary file downloaded from Google Drive for synchronization purposed.
    Not only the synchronization does not happen, but the temporary file is left in the folder. As said, this happens about half of the time, both when Keepass opens the db on startup, or when I open it manually from inside Keepass.
    Also, after the error appeared I used an utility (Unlocker) to check if there were any handles on the file, and I found none (that doesn't mean that there weren't at the time the error was generated). I don't know which process is using the file, but it seems to be releasing it shortly after, so maybe an automatic retry could do the trick?

     
    • Uranium235

      Uranium235 - 2015-01-06

      Do you use any anti virus background scanners? Please try to disable it temporarily to confirm if that is the cause.

      If it is, for now I can only advise you to exclude *.kdbx files or the folder where you store your database from scanning.

      If it is not, you might have some strange windows explorer handler that is trying to read the file. Do you have the Explorer windows where the files are stored open while synchronizing? Try closing that window before opening KeePass. Try to not open a database via double clicking, but rather using the open database menu from within KeePass and see if any of those methods make any difference.

       
  • Giacomo Ciani

    Giacomo Ciani - 2015-01-27

    Hi, sorry for the long delay.
    I did try to disable the only antivirus I have (Microsoft Security Essentials) and closing all explorer windows. I also did not use double click to open the file (I run Keepass and it remembers it from the last time I used it). The problem is still there.

    Any idea for further debug?

    Giacomo

     
  • Giacomo Ciani

    Giacomo Ciani - 2015-01-27

    Ok, never mind. I hadn't thought that I had the file in a folder that was auto-synced with Bitcasa. Since Bitcasa monitors the folder for any change, it was accessing the file as soon as it was created to keep in in sync with the online folder.
    Shutted down Bitcasa and now everything works. Sorry for the false alarm!

    Giacomo

     

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.