Unable to add any Books to Calibre

[Alaa]

Hi,
I get an error when adding any books to my library.
The books are fine as I can open them with EPUBReader in Firefox.

Below is the error log.
Can anyone help?

calibre, version 4.10.1
ERROR: Errors while adding: Failed to add any books, click "Show details" for more information


----------------------------------------------------------------------
Failed to add the book: I, Alex Cross
V:\Books\Calibre (my books)\James Patterson\I, Alex Cross (245)\I, Alex Cross - James Patterson.epub
With error:
Traceback (most recent call last):
File "site-packages\calibre\gui2\add.py", line 414, in add_book
File "site-packages\calibre\db\legacy.py", line 225, in create_book_entry
File "site-packages\calibre\db\cache.py", line 62, in call_func_with_lock
File "site-packages\calibre\db\cache.py", line 1590, in create_book_entry
File "site-packages\calibre\db\cache.py", line 1310, in set_metadata
File "site-packages\calibre\db\cache.py", line 1136, in update_path
File "site-packages\calibre\db\backend.py", line 1606, in update_path
File "site-packages\calibre\db\tables.py", line 137, in set_path
File "site-packages\calibre\db\backend.py", line 874, in execute
File "c:\t\t\apsw-cjr7a2yu\src\cursor.c", line 236, in resetcursor
CantOpenError: CantOpenError: unable to open database file

[kovidgoyal]

something on your computer is blocking calibre from opening it databas efile, typically an antivirus program or similar or if you have your calibre library folder in a shared location such as dropbox or similar.

[theducks]

V: ???
Calibre is not designed to use on Networked, Mapped drives
Visit the FAQ at the main Calibre site

[JSWolf]

Originally Posted by theducks

V: ???
Calibre is not designed to use on Networked, Mapped drives
Visit the FAQ at the main Calibre site

But it works. I've been using Calibre with a mapped network drive for more then 10 years.

[stumped]

Originally Posted by JSWolf

But it works. I've been using Calibre with a mapped network drive for more then 10 years.

Both posts can be true
It ( networked drive )works for you, but it's not designed to work (for everyone else)

Yet we are reading too much into a drive letter maybe. I have all sorts of drive letters but they refer to local drives (internal or on a permanent usb link to a daddy )
And I used to start my custom letters with s, for ssd,

The error message is clear. Cannot open database file so it's a file permissions thing

[JSWolf]

Originally Posted by stumped

Both posts can be true
It ( networked drive )works for you, but it's not designed to work (for everyone else)

Yet we are reading too much into a drive letter maybe. I have all sorts of drive letters but they refer to local drives (internal or on a permanent usb link to a daddy )
And I used to start my custom letters with s, for ssd,

The error message is clear. Cannot open database file so it's a file permissions thing

Given that it's a networked drive, could it be that another copy of Calibre is running and using the same library? I've never run two instances of Calibre so I do not know if that can happen.

[stumped]

The op has still not said if it's a network drive or not.
But continuing with the idle speculation that it is... Windows can lose such drives sometimes. E.g. I have two Nvidia shield drives mapped to drive letters on my pc for file copying. Two different devices. Occasionally one or both stop working , in that windows reports it cannot reach them, for which I blame updates or glitches on the shields. Reliability depends on what is actually hosting the drive and how it is accessed from the pc, and most obviously if that device has not been accidentally switched off!

[DNSB]

Originally Posted by JSWolf

Given that it's a networked drive, could it be that another copy of Calibre is running and using the same library? I've never run two instances of Calibre so I do not know if that can happen.

The one time I played with running two copies of calibre against the same database using a mapped drive on a SAN, I didn't see any error message but I did manage to very rapidly corrupt the database.