[ownedbycats]

Originally Posted by JimmXinu

Okay, this is weird.

I just got a similar error to ronnie0602, occurring a couple lines earlier while setting most of the other book metadata.

Except I'm on Win10 with Calibre 6.22.

PermissionError: [WinError 32] The process cannot access the file because it is being used by another process: 'C:\\Users\\USER\\Documents\\Library\\Andrew Joshua Talon\\Paint and Powder (10896)'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "calibre_plugins.fanficfare_plugin.fff_plugin", line 1798, in update_books_loop
  File "calibre_plugins.fanficfare_plugin.fff_plugin", line 2268, in update_metadata
  File "calibre\db\legacy.py", line 588, in set_metadata
  File "calibre\db\cache.py", line 85, in call_func_with_lock
  File "calibre\db\cache.py", line 1691, in set_metadata
  File "calibre\db\cache.py", line 1686, in set_field
  File "calibre\db\cache.py", line 1481, in set_field
  File "calibre\db\backend.py", line 1726, in windows_check_if_files_in_use
  File "calibre\utils\copy_files.py", line 250, in windows_check_if_files_in_use
  File "calibre\utils\copy_files.py", line 136, in __enter__
  File "calibre\utils\copy_files.py", line 132, in open_all_handles
  File "calibre\utils\copy_files.py", line 123, in _open_file
  File "calibre\utils\copy_files.py", line 112, in _open_file
PermissionError: [WinError 32] The process cannot access the file because it is being used by another process: 'C:\\Users\\USER\\Documents\\Library\\Andrew Joshua Talon\\Paint and Powder (10896)'

And trying to change the title of that book with Calibre's Edit dialog gives the same error, so it's not just FFF. But it doesn't happen for other books, so it's not the whole library, either.

Rebooting the OS seems to have cleared it. Unfortunately, I didn't find a good way to determine which processes have a file open until after I rebooted. Really wish I'd found that first.

I'd chalk it up to weirdness from installing a JDK and an IDE this morning, but the similarity of ronnie0602's issue is concerning...

There were some changes to file-locking starting with 6.20 (and additional changes in 6.21 to fix a data-loss bug), so maybe ask Kovid. Obviously this wouldn't affect someone using 3.48 though.