Http Web Server: Lotus Notes Exception - Entry Not Found In Index
Created by Sarah on 03/13/2007. Modified: 03/13/2007 05:49 AM
Message
HTTP Web Server: Lotus Notes Exception - Entry not found in index [/nui/bussols/ACTREQ.nsf/f652c9f96cce555f00256adf003fd701/e6e0511566c560d50025727c006517c3?EditDocument&Seq=1]
Synopsis
We have tried restoring database, deleting and recreating the full text index, running updall, compact, fixup to no avail - any ideas?!
Suggested Causes and Solutions:
Solutions
Kindly maintain solution and tips with error
santosh on 04/18/2007 10:41 AM
Hi,
From your Notes desktop, make a local replica of the afectted database. Then replace the server database with the local replicated database. When you make a replica, the database is repaired.
Albert, Barcelona, Spain
Albert Buendia on 05/03/2007 05:09 AM
Hi,
Me too getting the same error while attaching a attachment in the document.
HTTP Web Server : Lotus Notes Exception - Entry not found in index[/pscsa/eBatch.nsf/vwParentKey/NOV-73E5MH1770635657NOTV-73E5MJ?OpenDocument&vwtitle=vwBatchByMonth&&]
Can any body help me out to resolve..?
Thanks in Advance
Ramesh
Ramesh on 05/21/2007 04:06 AM
from my id this error not display till some dates but from some users id error displayed but after some i checked again from my id i also face same error
Http Web Server: Lotus Notes Exception - Entry Not Found In Index
i also tried to open from different pc
this error is coming from web client in lotus notes
anil kumar on 01/04/2008 01:19 AM
test test
Suguna on 01/15/2008 12:28 AM
I get this error when @DbLookup tries to find an entry in a column and fails, as part of a computed field's data
RSlater on 08/14/2008 09:58 AM
this error comes when the database is corrupted. just repair the database from the server console.u will not get this error message on next login........
rgds
kulbir
kulbir on 12/21/2008 06:46 AM
I had the same problem. I resolved it changing Database anonymous access from Depositor to Reader.
I hope it be useful
Enrique Munoz on 02/01/2011 04:34 AM
I got this error when I was using @dblookup but was able to resolve the issue by adding [FailSilent] to it and it worked.
Moshood Aminu on 07/13/2011 09:04 AM
Add Your Own Solution
Use this form to add a suggested cause or solution which you think might help.
Adding content is disabled. The spammer have won.