Checking the integrity of the database I was returned this error, which I can’t figure out what it is. The files in question (indexed) are available and open as usual.
08/08/22, 10:00:48: Ricerca Verified integrity of 1816 files successfully, checksum of 2 files different.
08/08/22, 10:05:42: Ricerca > Mellel > Topology Invalid File Integrity, checksum is different.
08/08/22, 10:05:55: Ricerca > Attachments > Saini & Khari 2022
I could not find any references in the Handbook. Any help?
Is there a way to tell DEVONthink to recompute checksums on imported files?
I had a bad checksum problem tonight, not for the first time but not DEVONthink’s fault.
An incompetent junior archivist who ought to get sacked (me), made changes to a document in an external editor and closed DEVONthink before closing the file in the external editor.
My cure was to run File->Check file integrity, right click the message about the offending file in the log window, and reveal the file.
Drag the file out of DEVONthink. Delete it in DT and empty the trash. Drag the file back into DT, causing the checksum to be recalculated.
All good, but a complex solution if replicants or tags are involved.
Mellel word processing document. I have two habits I try to stick to. Before I close a DT database, I look for apps that could have files open, and I do a synchronize all.
With automatic syncing turned on, the manual sync isn’t necessary. Nor, come to think of it, is that salt I throw over my shoulder by light of the moon. I’ll have to rethink that.
FYI: Came here when searching for a solution for my 17 Invalid file integrity, checksum is different error messages. Verify & Repair Database did not show any errors. Update items did not resolve the issue. All 17 files were/are small markdown files. I had to Rebuild Database to resolve the issue.
I see this every once in a while, and you’re right, Rebuild is the cure.
First create a backup. I’ve never had a problem with this. A backup is still a good idea.
Use Window->Log to display the log output, which you would have probably seen, anyway.
Select the database with the problem in the sidebar. Click File->Check File Integrity.
The log window will show the file(s) Devonthink believes have changed.
That will let you know what’s getting flagged with a different checksum. Now that you know what files are involved, rebuild the database.
The way this happens to me is when I open a file with an external editor, update it, and close Devonthink before saving the file. For instance, a word processing file. I like to see which files caused the error message. It’s never indicated a loss of data.
Opening the document with the DEVONthink editor and making a (small) change resolves the issue.
Since my last post I had 104 modified files and DEVONthink reported 5 of those with Invalid file integrity.... All those files are Markdown notes which I manage in Obsidian and which are indexed by DEVONthink. I am almost sure that I edited these files (in Obsidian) with DEVONthink running, just because I always have both apps running all the time.
Anything else I can report to help resolve the issue?