"Server error: Entry not found in index" when switching between view all / view unread

Since upgrading to 8.5 server, we have had 5 users report getting “Server error: Entry not found in index” when switching between view all / view unread in both the basic and eclipse 8.0.2 client against an 8.5 server. If the user marks all documents as read, the problem will go away for a bit, but eventually comes back later in the day. I have run a compact -c and a fixup -F -J with no success. I also removed/rebuilt the cache.ndk, bookmark.nsf and names.nsf for the user but that did not fix it. The number of effected users seems to slowly be increasing, so any advice is greatly appreciated.

Regards,

Tom

Subject: I have reproduced this on my platform.

On my enviroment happen in folders with exactly more than 500 message (501 and more).Please confirm if you can reproduce.

For Lotus Suppport:

I have find this document.

LO38696: “ENTRY NOT FOUND IN INDEX” ERROR VIEWING ONLY UNREAD

in my enviroment this happen with Server 8.5 HF109 Linux , Lang. Pack Italian

Client 8.5 english and italian.

Thanks in Advance

Luca

Subject: I can now reproduce on demand

Client is in the inbox, view all is selected. A message is delivered to the mail file and is put into a folder by a mail rule and the message count for the folder shows that there is an unread message. While still in the inbox, I click on the view unread option and the error message appears. This does not happen in any folders or in all documents, only the inbox.

Subject: Seen something like this before.

I have seen the issue before where a mail file didn’t have a properly updated design. So a form would make a call to code that didn’t exist in the database.

Try this (manually).

  1. Replace the design with the current correct template for your version.

  2. Do the folder upgrade to update all the folders.

Then try seeing if you can reproduce the issue.

It may also be related to a particular document (eg. form stored in mail).

Another one to check is to see that the users location document is correctly filled out (although intermittent, it might not be that).

Subject: A few thoughts

Is this in the user’s mail file on the server or on the local computer? Have you tried compacting the database? Is there a full-text index? If so can you delete it and try again? Are there any issues writing to the temp directory (try emptying the temp items on all drives on the computer.

Can you delete the cache.ndk file and let Notes re-create it? Can you reproduce this in basic mode?

Can you make a fresh replica and reproduce the problem?

Sorry for the stream of ideas but this sounds like a classic view/folder corruption issue and the db needs to be compacted, or create a fresh replicate and replace the old one.

Subject: Results of your suggestions

Micheal,

Thank you for your suggestions. I had previously tried both a compact -c and a fixup -F -J, but those did not resolve it. I has also tried deleting and recreating the cache.ndk, names.nsf, and boomark.nsf and also made a new replica, but all still have the issue. I had not tried deleting the full text index until now, but unfortunately that also did not work.

The only way I have been able to temporarily eliminate the problem is by marking all documents as read and then it will go away for a bit but will return soon after. Hopefully the log info posted earlier will be helpful.

Thanks again for your suggestions!

Tom

Subject: Did you resolve this?

We are experiencing the same issue. It’d be interesting to know, otherwise I’ll open a PMR with IBM.

Subject: same here…

Did anyone resolve this?

Thanks!

Subject: From Client

Turn on

CLIENT_CLOCK=1

DEBUG_OUTFILE=c:\noteslog\notes.log

in notes.ini, reproduce the problem and reply to this, with portion of notes.log leading up and including that which shows the error.

Subject: Log as requested

(36-26 [36]) OPEN_DB(CN=xxxxxxx/OU=xx/O=xxxx!!mail\xxxxxxx.nsf): (Connect to xxxxxxx/xx/xxxx: 122 ms) (Exch names: 0 ms)(Authenticate: 9 ms.)(OPEN_SESSION: 11 ms)

3 ms. [134+290=424]

(37-26 [37]) DB_MODIFIED_TIME: 4 ms. [14+68=82]

(38-26 [38]) DB_MODIFIED_TIME: 1 ms. [14+68=82]

(39-26 [39]) FINDDESIGN_NOTES: 16 ms. [40+16=56]

(40-26 [40]) OPEN_COLLECTION(REP85256B1A:005429B7-NT0000055E,0000,0000): 7 ms. [42+34=76]

(41-26 [41]) FOLDER_GETMODTIME_RQST: 1 ms. [78+60=138]

(42-26 [42]) GET_NAMED_OBJECT_ID($profile_016calendarsettings_cn=xxxxxxx/ou=xx/ou=xx/o=xxxx): 1 ms. [90+24=114]

(43-26 [43]) OPEN_NOTE(REP85256B1A:005429B7-NT000495C6,00400020): 15 ms. [48+3128=3176]

(44-26 [44]) FIND_BY_KEY: 6 ms. [48+34=82]

(45-26 [45]) READ_ENTRIES(REP85256B1A:005429B7-NT0000055E): 1 ms. [76+964=1040]

(46-26 [46]) CLOSE_COLLECTION(REP85256B1A:005429B7-NT0000055E): 0 ms. [12+0=12]

0 ms. [12+0=12] (Session Closed)

(47-29 [47]) READ_ENTRIES(REP85256B1A:005429B7-NT0004A9B2,Since:02/03/2009 04:52:00 PM): 4 ms. [240+76=316] (Entry not found in index)

(48-37 [48]) CLOSE_COLLECTION(REP85256B1A:005429B7-NT0000037E): 1 ms. [12+0=12]

(49-37 [49]) GET_NOTE_INFO: 1 ms. [18+102=120]

(50-37 [50]) CLOSE_COLLECTION(REP85256B1A:005429B7-NT0004A9B2): 1 ms. [12+0=12]

(51-37 [51]) GET_NAMED_OBJECT_ID($profile_016calendarsettings_cn=xxxxx/ou=xx/xxx=us/o=xxxx): 7 ms. [90+24=114]

(52-37 [52]) OPEN_NOTE(REP85256B1A:005429B7-NT000495C6,00400000): 3 ms. [48+3128=3176]

(53-37 [53]) UPDATE_NOTE(REP85256B1A:005429B7-NT000495C6,00080000): 12 ms. [3100+106=3206]

(54-37 [54]) CLOSE_COLLECTION(REP85256B1A:005429B7-NT0004A9B6): 1 ms. [12+0=12]

(55-37 [55]) CLOSE_COLLECTION(REP85256B1A:005429B7-NT00000586): 0 ms. [12+0=12]

(56-37 [56]) CLOSE_DB(REP85256B1A:005429B7): 1 ms. [14+0=14]

Subject: A action button with @ViewShowThisUnread(“1”) gives the same result

I created an action button in the Inbox with a formula of:

@ViewShowThisUnread(“1”)

This yields the same error message.

Subject: Identified

Subject: Identified

The behavior that you are seeing has been identified as SPR: JADS7PSQUS. At this time IBM cannot reproduce this and has closed it out, however customer’s may call into IBM Support or create an Electronic Service Request (ESR) to add a Customer Report in hopes that this issue will be raised once again to IBM Development.

In order to create the Electronic Service Request, please see below:

Subject: Issue Reproducable

Hi,I have encounted the same issue. Message pops up when the user switched to View Unread. On opeing an unread mail from the Inbox, message pops up. The Client 6.5 agianst an 8.5 server. Any feedback appreciated.

Subject: Reproduced here as well…

Users with large amounts of documents in their inbox get this message when they have their “View Unread” button selected. If I reduce the number of documents in the Inbox below 500, the issue goes away.

Happens to users running 7.03/8.5 clients against an iSeries server running Domino 8.5.

Subject: I have two users with this problem so far, Upgraded Servers to 8.5 last week

Hi All,

I have 2 users experiencing the same problem.

I only upgraded the servers to Domino 8.5 FP1 last week.

Both Clients are using version 7.03.

Does anybody know of a solution to this problem?

thanks All.

Subject: Same Error

We upgraded our servers from 8.0.2 to 8.5FP1 and users are on 7.0.2 client. We have 3 users that are getting the “Server Error Entry Not Found in Index”. We have tried fixup, updall, compact, marking all unread to read, reinstalling the client, replacing the id… Still not fixed. Has anyone found a fix?

Subject: Was able to workaround…

I was able to workaround this issue with user on Notes 8 Standard (8.0.2 FP3) Platform is Windows 2003, Domino 8.5.1 in the same way Mike stated above…by reducing the number of documents in the inbox below 500. The following concerns searches, but helped in this case:

http://www-01.ibm.com/support/docview.wss?uid=swg21444878

Subject: OS, anyone?

We see this on our 8.5 mail servers running natively on the iSeries. Is this common to everyone or does this affect multiple server O/S’s?

Subject: OS is iSeries. Is anyone on Windows Server platform experiencing this problem?

We recently upgraded our Domino servers to 8.5 FP1 and have just begun to start receving calls in relation to this problem. A temp workaround I found is to send the user a test message and request them to leave this UNREAD. I found that if at least 1 UNREAD message is in the inbox when they are using the View Unread function the error does not occur. We have a mixture of R6/R7/R8 clients/mail templates!