View Single Post
Old 04-24-2020, 01:11 PM   #2
gbm
Wizard
gbm ought to be getting tired of karma fortunes by now.gbm ought to be getting tired of karma fortunes by now.gbm ought to be getting tired of karma fortunes by now.gbm ought to be getting tired of karma fortunes by now.gbm ought to be getting tired of karma fortunes by now.gbm ought to be getting tired of karma fortunes by now.gbm ought to be getting tired of karma fortunes by now.gbm ought to be getting tired of karma fortunes by now.gbm ought to be getting tired of karma fortunes by now.gbm ought to be getting tired of karma fortunes by now.gbm ought to be getting tired of karma fortunes by now.
 
Posts: 2,195
Karma: 8888888
Join Date: Jun 2010
Device: Kobo Clara HD,Hisence Sero 7 Pro RIP, Nook STR, jetbook lite
Quote:
Originally Posted by DrW View Post
I'm in the process of moving over to a new PC and have hit an issue when it come to moving Calibre over. I've had a look through the forums but haven't found any solution, so I was hoping that someone might have encountered something similiar before.

I did the export on the old machine, installed the same version of Calibre on the new machine (4.11.2 64-bit), hoping that would cause fewer issues.

Ran the import on the new machine and everything seemed to go okay but, when it had completed, there were no books showing up in the library. All the plugins seem to have gone in okay though.

I restarted Calibre and this error popped up:
Code:
calibre, version 4.14.0
Corrupted database: The library database at C:\Users\Mike\Documents\Calibre Library 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 304, in initialize_db
  File "site-packages\calibre\db\legacy.py", line 82, in __init__
  File "site-packages\calibre\db\legacy.py", line 47, in create_backend
  File "site-packages\calibre\db\backend.py", line 408, in __init__
  File "site-packages\calibre\db\schema_upgrades.py", line 19, in __init__
  File "site-packages\calibre\db\backend.py", line 874, in execute
  File "c:\t\t\apsw-cjr7a2yu\src\cursor.c", line 236, in resetcursor
ReadOnlyError: ReadOnlyError: attempt to write a readonly database
I set it rebuilding the database, but after two hours nothing seemed to have happened (my library isn't that big, only 514 books).

One thing I have noticed, is that the error mentions that the database is in C:\Users\Mike\Documents\. 'Mike' was the user account on the old machine: the new one is 'mikef'.

Could that be the issue? Or have I missed something else very obvious?

I've just noticed that the error is showing "calibre, version 4.14.0". I did put the most recent version on first but then, when I had problems, realised it was the 32-bit version, so uninstalled that and went back to 4.11.2 64-bit. It obviously didn't fix the problem.
Check under C:\Users\mikef\Documents\ for calibre library.

bernie
gbm is offline   Reply With Quote