In a windows environment, one can end up with this issue on a clean install with the Calibre folder attached at the root of a drive. (ie, d:\calibre as the database) This is because, by default, Windows makes non-adminstrators have read-only access to the root of the drive, and calibre runs (as it _should_) without elevating privilege.
I ran into this recently when I virtualized the server that was hosting my calibre database, and forgot to reset the permissions. Duh.
Result? A complaint about a corrupted database. Sigh. Once I changed the permissions to give 'users' write permission, all was well.
|