Michael A Stokes 15 October 2012 01:16:51 PM
Recent issue I came across with a customer reporting one server continually reporting an error - Entry not found in index
The console and associated logs were filled with errors similar to this:
[10790:00015-3946838896] 11/10/2012 15:20:10 Database collection error: /domino/dom/server/data/ddm.nsf: Entry not found in index
[10790:00016-3946572656] 11/10/2012 15:20:13 Database collection error: /domino/dom/server/data/events4.nsf: Entry not found in index
[10790:00012-3946572656] 11/10/2012 15:20:13 Database collection error: /domino/dom/server/data/names.nsf: Entry not found in index
The precursor to this is that they found the errors whilst correcting an issue where one of the "admins" had decided to replace the design of the Domino Directory with a mail template. Immediate concern is that the Domino Directory on the server is corrupt and so the standard replace options are done and we still see the error.
Further digging around by eliminating (or in our case including server tasks manually) shows us the events task would be the culprit.
Another "admin" or maybe the same "admin" who replaced the design of the Domino Directory had created a default database probe and for whatever reason had decided that the predefined ignore values should be changed. Removing the ignore entry for - Entry not found in index [[ 0x0404 ]]
Note that when you create a Database Error Monitoring probe it states the following:
This probe monitors key locations in the database software layer (NSF/NIF) and generates event documents for any errors that occur. Because some errors occur naturally, an error exclusion list can be configured with this probe. The schedule for this type of probe is not configurable.