What it means
An archive run on a mail file, started by the client, a policy or server-side compact, stopped before it finished. Nothing after the failure point was archived.
Common causes
- Documents with a blank or damaged creation date when the criteria use an "older than" rule, often calendar entries imported from ICS files
- Damaged views or documents in the source mail file
- The archive database is missing, has moved, or would exceed its quota
- The server or signer cannot write to the archive database
Quick fixes
- Read the reason after the colon. For Entry not found in index, change the criteria to "not modified in more than" days, or find and remove the documents with no creation date
- Take a backup, then run fixup, compact and updall on the mail file and try again
- Check that the archive database exists where the archive settings point, has room under its quota and that the server can write to it
- Re-run a server archive with
load compact mail\user.nsf -aand check log.nsf