Hi there
Whilst attempting to set up a user client we couldn’t get past the password - seems there must have been a typo that I couldn’t recreate! Only way was to delete the user and then re-register again!
Did this, got the ID file and set everything up - and it works fine, emails are flowing in and out - but the user has now vanished from the address book!
Any idea what might have happened and what I can do?
Subject: Vanishing Address Book Entries
I can’t find anywhere where you state how many servers are in your domain; however, Ill assume more than one and pass this on. A few years ago I ran into the same problem, deleted a user then replaced him, or her, with the same name. It is my opinion that replication from one of the other servers in our system was causing this problem. The final solution was to disable the replication system whereever it could be disabled and then to go through all of the address books on each server and make 100% sure that they agreed down to the smallest “.” .
So if you have more than one server you might want to check that possibility too. If not then maybe its time to call an exorcist.
Cheers,
Steve
Subject: User vanished from Address Book
The user deletion process queues up a series of server requests that takes some time to complete. That process should be allowed to complete before you register the same name again. Otherwise you get the ongoing deletion process running over your newly registered objects.
Subject: RE: User vanished from Address Book
Any idea what sort of time scale - or indeed how I would check that this has completed? Is there any way to re-build using the UserID file?
Thanks
Subject: RE: User vanished from Address Book
You can check the progress of the deletion process in the admin4.nsf database. Look in the Actions By Name view. Open the most recent request for the user and see what server will perform that action. You can force replication of admin4.nsf and names.nsf to the appropriate servers. Then issue the console command Tell AdminP Process New on the server that will handle the request. When it’s done do the same thing for the next request. While some requests are handled by a specific server and can be answered quickly, others will be handled by all servers and that requires more time. If you’re a single-server environment you can probably get through the whole thing in just a few minutes, but if your organization has hundreds of servers it will probably be better to just wait it out. Here is a link to a description of the process. This should help you determine when the process is complete:http://www-12.lotus.com/ldd/doc/domino_notes/Rnext/help6_admin.nsf/f4b82fbb75e942a6852566ac0037f284/0ec569ef183e908385256c1d0039efa4?OpenDocument
Subject: User vanished from Address Book
When you re-registered the user, did you by any chance have the registration server set to “Local”? (Check your personal address book to see if there’s a person doc there.)
Subject: RE: User vanished from Address Book
“When you re-registered the user, did you by any chance have the registration server set to “Local”? (Check your personal address book to see if there’s a person doc there.)”
The user was certainly
a) Deleted from the server NAB
b) Re-registered on the server and appeared in the server NAB - I copied the ID file from there
c) Was gone the next morning - but the user is able to login and use his mail account