Delete Person not removing user from Address Books

HCL Domino Domino Forum
1

Strange…Via the Administration server in the NAB, I click Delete Person; when prompted to delete via Adminp I select YES. I see the request being completed via Adminp; the person document is then removed from the Administration NAB. However, this deletion is NOT removed from the remaining NABs in the domain. I checked the ACLs, verified the Admin Server, issued a tell adminp process now at the console. Nothing is working. This occurred yesterday and today the person document is still in the other replicas.

Any other clues as to what to do?

Thanks in advance.

2

Subject: Delete Person not removing user from Address Books

Have you checked that you are replicating as a ‘push pull’ to other replicas in your domain?

Try to issue a manual replication to another replica from your main server where the deletion has worked. If this works, then the issue is to do with your replication schedule.

HTH,

Ranjan

3

Subject: RE: Delete Person not removing user from Address Books

Hi Ranjan,I verified the replication type: its pull push so the Administration server is performing the work. I cleared the replication history and forced a replication, still no deletion. However I did find something…this client is has another replica of the NAB under a different filename; that replica received the deletion. So we have: name.nsf and names2.nsf. Names2.nsf received the deletion but names.nsf did NOT. Could it be the deletion stub no longer exist, thereby not deleting it from names.nsf.

4

Subject: RE: Delete Person not removing user from Address Books

All replicas should get the deletion stub…please verify that the names2.nsf is a replica, and also verify that names2.nsf is listed in the notes.ini (hint this may be part of a ‘cascading n&a book setup’ - please check.

HTH,

R

5

Subject: RE: Delete Person not removing user from Address Books

names2.nsf was not part of a cascade they actually created for remote users and never got rid of it scary

to determine if there might be NAB corruption, i renamed names.nsf to oldnames.nsf and renamed names2.nsf to names.nsf…created a test user, submitted the deletion, and guess what, it worked.