Article

pnuffer's picture
article
Reads:

3124

Score:
0
0
 
Comments:

0

Solving Lotus Notes "Corruption" Problems

Author Info

15 February 2006 - 6:35am
Submitted by: pnuffer

Author Blog
Author Profile

Tags

Tags Map

(View Disclaimer)

Problem

A reader recently asked:

"When running the Lotus Notes Driver's publisher polling process, ndsrep, on the Domino server, sometimes an "Error reading NotesDN person" message is reported to the Domino Console. Does an "Error reading NotesDN person" message from ndsrep indicate database (names.nsf) corruption?"

And here's the response from Novell's Perry Nuffer ...

Solution

Data corruption is always a possibility, but it is very unlikely given this type of error message. More specifically, it means that the person document (user record) that ndsrep was trying to read may be missing its FullName field, or at least a problem existed when reading the FullName field (no value was returned) of that person document.

Also, the same message may be returned if the value of the entry in the FullName field is not appropriately formatted in canonical format; specifically it must start with 'CN='. So, if this message is displayed on the Domino Console log for ndsrep, then a) the person document in question has no value in the FullName field, or b) the values in the FullName field do not start with 'CN='.

Note: This solution was tested in an environment with Lotus Notes/Domino 5, 6, or 7; IDM 2 or 3; and Notes Driver v2 or above.


Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).

It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.



Related Articles


User Comments

© 2013 Novell