corrupted database

Bug #759310 reported by William T. Raiguel
28
This bug affects 5 people
Affects Status Importance Assigned to Milestone
calibre
Undecided
Unassigned

Bug Description

I get the corrupted database error message uponj opening Calibre program. I have uninstalled, searched for all remaining calibre and metadata files and deleted them after uninstall. Upon consistent reinstalls, the error message repeats and will state failed to fix and will not accept a different locatation. The program then quits. I did not have the problem until installing v7.5.4. I am running Windows 7.

I tried to report this as a bug, but get the messaage, "1 error."

Martin Pool (mbp)
affects: launchpad → calibre
Revision history for this message
Kovid Goyal (kovid) wrote :

If your database is corrupted then you need to delete it. Look for the file metadata.db in the folder you chose for you calibre library and delete it. Then start calibre.

Then click the arrow next to the calibre icon and choose Library Maintenance->Restore database to get back the list of books.

Changed in calibre:
status: New → Fix Released
Revision history for this message
William T. Raiguel (wraiguel) wrote :

I appreciate the response and attention I received within a few hours of reporting the issue. Deleting the metadata.db had no effect, nor did restarting the computer after uninstalling, and then reinstalling Calibre. I finally was able to get the program to open with the corrupted database error message. I then chose to restart the program from the pull down preference d-bug option. This created a script which appears to have corrected the problem, as the program now opens without issue.

Revision history for this message
Stephan (a.s.a) wrote :

This is the failure message to this bug. I used windows 10. The Update (Version 3.150 caused the problem

Revision history for this message
Kovid Goyal (kovid) wrote : Re: calibre bug 759310

No, it did not. But feel free to downgrade to a previous version if it
makes you feel better.

Revision history for this message
BlackStoneD (jayet-pierre) wrote :

The only way I found to turn around the bug is to execute Calibre in admin mode.

Revision history for this message
Raven Saint (ravensaint) wrote :
Download full text (3.8 KiB)

I use a clean folder with no data or files within it. So no database to delete. I tried to downgrade to previous version from 3.27.1
The Error Details for the retry on 3.26.1 are this for me:

calibre, version 3.26.1
Corrupted database: The library database at C:\Users\usmcs_000\Documents\My Kindle Content\CalibreBooks appears to be corrupted. Do you want calibre to try and rebuild it automatically? The rebuild may not be completely successful. If you say No, a new empty calibre library will be created.

Traceback (most recent call last):
  File "site-packages\calibre\gui2\main.py", line 312, in initialize_db
  File "site-packages\calibre\db\legacy.py", line 81, in __init__
  File "site-packages\calibre\db\legacy.py", line 48, in create_backend
  File "site-packages\calibre\db\backend.py", line 378, in __init__
  File "site-packages\calibre\db\backend.py", line 1123, in fget
  File "site-packages\calibre\db\backend.py", line 836, in conn
  File "site-packages\calibre\db\backend.py", line 267, in __init__
CantOpenError: CantOpenError: unable to open database file

calibre, version 3.26.1
ERROR: Bad database location: Bad database location u'C:\\Users\\usmcs_000\\Documents\\My Kindle Content\\CalibreBooks'. calibre will now quit.

Traceback (most recent call last):
  File "site-packages\calibre\gui2\main.py", line 291, in initialize_db_stage2
  File "site-packages\calibre\db\legacy.py", line 81, in __init__
  File "site-packages\calibre\db\legacy.py", line 48, in create_backend
  File "site-packages\calibre\db\backend.py", line 378, in __init__
  File "site-packages\calibre\db\backend.py", line 1123, in fget
  File "site-packages\calibre\db\backend.py", line 836, in conn
  File "site-packages\calibre\db\backend.py", line 267, in __init__
CantOpenError: CantOpenError: unable to open database file

3.27.1 details are this:

calibre, version 3.27.1
Corrupted database: The library database at C:\Users\usmcs_000\Documents\My Kindle Content\CalibreBooks appears to be corrupted. Do you want calibre to try and rebuild it automatically? The rebuild may not be completely successful. If you say No, a new empty calibre library will be created.

Traceback (most recent call last):
  File "site-packages\calibre\gui2\main.py", line 312, in initialize_db
  File "site-packages\calibre\db\legacy.py", line 81, in __init__
  File "site-packages\calibre\db\legacy.py", line 48, in create_backend
  File "site-packages\calibre\db\backend.py", line 378, in __init__
  File "site-packages\calibre\db\backend.py", line 1123, in fget
  File "site-packages\calibre\db\backend.py", line 836, in conn
  File "site-packages\calibre\db\backend.py", line 267, in __init__
CantOpenError: CantOpenError: unable to open database file

calibre, version 3.27.1
ERROR: Bad database location: Bad database location u'C:\\Users\\usmcs_000\\Documents\\My Kindle Content\\CalibreBooks'. calibre will now quit.

Traceback (most recent call last):
  File "site-packages\calibre\gui2\main.py", line 291, in initialize_db_stage2
  File "site-packages\calibre\db\legacy.py", line 81, in __init__
  File "site-packages\calibre\db\legacy.py", line 48, in create_backend
  File "site-packages\calibre\db\backen...

Read more...

Revision history for this message
kryane (kryane) wrote :

Same error.
I updated from 3.23.0 to 3.27.1, and I got Corrupted database error.
After uninstalling 3.27.1 and installing again 3.23.0, calibre start

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related questions