Domino & Notes error

Error archiving documents from [database]: [error]

The text after the colon is the real reason, for example Entry not found in index or a quota error. With archive debugging on, earlier log lines such as Error selecting documents for archiving, pruning and deleting give more detail.

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

  1. 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
  2. Take a backup, then run fixup, compact and updall on the mail file and try again
  3. Check that the archive database exists where the archive settings point, has room under its quota and that the server can write to it
  4. Re-run a server archive with load compact mail\user.nsf -a and check log.nsf

Need a hand with this?

Paste your exact message into What's That Error? for a plain-English explanation, or get in touch. I've been supporting Domino and Notes for 28 years.

Disclaimer

The errors, causes and fixes on this site are carefully researched, drawing on HCL documentation and 28 years of hands-on Domino and Notes experience. Every environment is different, though, and a solution that works in one may not be right for yours. Exact wording can also vary between Domino and Notes versions.

This information is general guidance only and is provided without warranty of any kind. Always back up your data and test changes on a non-production system first. To the extent permitted by law, Bruinsma Services Pty Ltd accepts no responsibility or liability for any loss, damage, downtime or other consequence arising from use of this information. For advice specific to your environment, please contact me.