Recent server upgrade from 7.0.2 to 8.5., Windows 2003 R2 standard server w/SP2, 32bit.Applied hotfix SPR-JPAI7MFS69.
Used the adminp process to rename the CN of a user. The task completes with no errors, but the name never changes. The adminp should complete and change the name in the directory as well as any group memberships and security. Rebuild the index of the names.nsf. Nothing has worked.
Any takers on this one?
Subject: Already installed that fix
I stopped the domino server, installed the fix and restarted. Same issue.
I will restart the entire server in the morning.
Thank you.
Subject: Not sure, but …
seems that IF2 does not include HF1 which addresses this issue.
Subject: HF1 link needed
I looked and looked on fix central and came up blank on the hf1.
Does anybody have a link to the fix?
Subject: IF3 has just been released
IF3 adresses the rename problem
Subject: IF3, HF211 installed
Removed IF2 - IF3 installed. Now when a rename is initiated, I get:
04/08/2009 11:53:05 AM Admin Process: Received the following error performing a Initiate Rename in Domino Directory request on Forrest Gump/NotesDomain (Path: names.nsf): The name to act on was not found in the Domino Directory.
When a directory search does find the name. WTF!
Subject: Update - Domino 8.5 - person rename not working
OK, another piece of the puzzle.
When I did the server reboot, I noticed an error in the server log that a resource in the reservation database had an invalid character. I initiated a name change and received a dialog that the rename service needed to be started. Answered yes and the other renames started to launch. However the other renames did not complete.
Subject: new-names.ns_ not being updated
I noticed in some of the errors, a file listed as new-names.ns_. I checked this file and found that of the rename functions that are failing, ie: names not found, the names are not in this application(DB). This seems to be a mirror of the names.nsf.
What is the new-names.ns_? I have not come across this before.
Subject: Never
heard of a new-names.ns_ before.Perhaps it’s a temporary file that is created during the upgrade process and has not been deleted. I suppose it has the same replica ID like names.nsf but a different content. So the rename process looks into this ns_ file first but cannot find the user.
I would suggest to delete the file and try another rename.
I’ve tested with HF211 and had no problems renaming users.
Subject: Solved - replica of DomDir not replicating
That was it. Apparently the new-names.ns_ was a replica of the names.nsf that the server was looking at for the directory. In addition, the file was not replicating. I deleted the replica(backup was good) and the rename worked right away.
Thank all of you for your help.