I had the same error ( maybe different views ) when I updated from 8.0.2 to 8.5 earlier this year.Couldn’t find out either what exactly causes this error. After I opened and resaved each and every policy document, the error did no longer occur.
Not sure if this will solve the problem on your site; just try it.
And NO, you are not the only one having this issue after upgrade or new install. I know at least two others …
your names.nsf still may have an old ODS Version since the serve can’t compact it because it’s always in use.
Set Create_R85_Databases=1 in your Server’s Notes ini if u havent already
shutdown Server
make sure no domino process is running
open CMD → go into your domino directory
run ncompact -c -B \names.nsf
restart server
check if ODS is Correct on 85 now
to make sure replace design of the domino directory again.
This worked for me.
also run the compact on every Database in the Data-Directory root which the Server has not updated to the actual ODS, this may be log.nsf, catalog.nsf and some others.
After many attempts to resolve the issue with the nab we think we may have found the fix. We found corruption in the nab once again so we decided to try something new. In the past we have run compact, fixup, tried creating new copies, refreshed design, replaced design, created a new nab from Ahlstrom template and copied docs in however each morning we come in to find the nab corrupted again.
This morning we tried something new. We took a stock IBM/Lotus directory template (pubnames.ntf) and created a new nab with no customization. We created a view in the current nab to view all docs so that we could copy them to the new nab. Prior to copying all the docs over to the new nab we analyzed the docs that were in the old nab because we were seeing some messages in the log about docs that had illegal characters. While we were looking around we found something interesting, mail in the nab! click here to view the mail we found in the nab => There were over 200 e-mails in the nab. We are not sure how the e-mail got into the nab but a guess would be that someone with editor access or higher copied the messages from a mail database and accidentally pasted them into the nab. Because none of the views in the nab are set up to view docs with the form names “memo” or “reply” the messages went unnoticed.
The e-mail and or the customization to the nab was the cause of the problem we have been experiencing. Sometimes we see the corruption in the nab begin during the day and sometimes it happens overnight. The new clean nab has been in place several weeks now and has shown no signs of corruption.
