What it means
A lookup searched a view for a key and didn't find it, or the view's index is damaged.
Common causes
- The key in
@DbLookup or GetDocumentByKey isn't in the view (spelling, extra spaces, changed values)
- The view's first column is no longer sorted, or the view design changed
- An out-of-date or corrupt view index
- Readers fields hiding the document from the user or server running the lookup
Quick fixes
- Check the key exists in the view's first sorted column
- Rebuild the index: Shift+F9 in the view, or
load updall path\db.nsf -r
- Handle "not found" in code (
@IsError, or check for Nothing in LotusScript)
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.