View Single Post
Old 07-14-2012, 02:18 AM   #10
chaley
"chaley", not "charley"
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 5,250
Karma: 821512
Join Date: Jan 2010
Location: France
Device: Many android devices
Another thing you can try: use the command line version of restore. This method ensures that no part of calibre (content server, etc) can accidentally have the replacement DB open.

The documentation is at http://manual.calibre-ebook.com/cli/...store-database.

A quick synopsis, assuming that the correct library is chosen when you start calibre. If you are using calibre portable or if you are using environment variables, the following won't work. It also probably won't help if the problem is caused by some program other than calibre (e.g., an antivirus program or something else) holding the database open, although it might because the timing is very different.

1) open a command box. One way to do this is Start -> Run. Type cmd and press return.
2) type "calibredb restore_database --really-do-it" (without the quotes).
3) watch the messages go by while you wait ...
chaley is offline   Reply With Quote