Contents | Start | End | Previous: KB0110: Why is Jutoh slow to load a document created by Google Docs? | Next: KB0112: Navigation goes to the wrong section on Kindle
See also:
Is Jutoh compatible with Dropbox, Google Drive, OneDrive, Amazon Drive and iCloud?
Why does Windows complain that files cannot be found, opened or written?
If your project file becomes corrupted, you may see error messages like this:
SQLITE_CORRUPT[11]: database disk image is malformed
Corruption might happen if you are using a USB drive (lower reliability), or Dropbox or similar utilities since they don't like incremental writes to SQLite files. Jutoh has a workaround for this via Preferences/Project/Edit in temporary folder, where you can specify for which folders Jutoh should first copy the file to a temporary folder, and only copy the file back to the original folder when the project is closed.
Here are some things you can try to fix corrupted files:
If a .jutohbak file is available, try copying it to a .jutoh project with a different name than the original, and seeing if it works better.
Before making any further edits, you could try sending it to a colleague or editing it on a different machine, because it could be a problem specific to your system that is causing saving to fail, such as a system failure or third party software accessing the file.
If loading and compiling documents works, but when trying to save an edited document you see an error message saying that Jutoh is unable to save it, something in the project file has become corrupt, perhaps during a file transfer. You may be able to fix this simply by compacting the project using File | Compact Project. This operation writes out all the project data to a new copy, and then renames the copy back to the original name, so it can fix some file corruption problems.
If the above doesn't apply or doesn't work, you may need to delete a document within the project that has been corrupted and crashes Jutoh when loading. If you have difficulty deleting a document, you can use Preferences/Projects/Project Maintenance to delete it without having to open it first. You may also need to clear Preferences/Projects/Open last viewed document before opening the project so that Jutoh doesn't try to show a potentially corrupt document.
Before deleting a particular document, you can first check whether it might be an image that is causing the crash. Clear the option Preferences/Advanced/Enable images and try viewing the document. If it successfully opens, you can delete one or more images that may have become corrupted, before enabling images again.
If you get a corruption error whenever you open the Jutoh project, and can't get rid of it, try creating a new blank project and then importing the old one into it using File | Import | Import from Project. Click Import Options and check everything you want to import (usually everything).
If you have a backup of your project that works, and want to restore text from a single document, you can open both projects simultaneously (check Preferences/Project/View multiple projects first) and copy all or some of the original document to the latest project.
If you cannot recover your Jutoh project, but still have an Epub, Kindle, or ODT file, you can import that into a new Jutoh project. To import a Kindle (.mobi) file, install the third-party software Calibre and configure Jutoh with the Calibre folder in Preferences/Helpers.
One Jutoh user who experienced problems saving documents on Windows found that the problems went away after running a registry cleaner utility.
Another Jutoh user running Linux who accidentally overwrote some data managed to recover the text from an older Jutoh file, using the recovery software R-Linux. In particular he found old versions of the file in a .debris folder.
Contents | Start | End | Previous: KB0110: Why is Jutoh slow to load a document created by Google Docs? | Next: KB0112: Navigation goes to the wrong section on Kindle