I am having a problem with the “Request move to new certifier” function of the Domino 6 Administrator client. The process in Administrator works fine (select user, initiate process, select current certifier ID, select new certifier, allow primary name change), but when it moves to the Administration Requests database, it sticks at “Move Person’s Name in Hierarchy.” The user in question can logout and login multiple times, but adminp does nothing. I have told adminp to “process all” several times, but to no avail.
Our users are working from Notes 5.0.11 clients and the server is on the same version. This process has worked for us before, but since we started a mass recertification project (246 are currently queued to be recertified in the Administration Requests database), it stopped working altogether.
Any ideas?
Subject: Move Person’s Name in Hierarchy
You need to open the Admin4 database (Administration Requests), and go to the Requests/Name Move Requests View. Select the unprocess requests, and hit the “complete move for selected entries” button.
At least that’s what did it for us…
Subject: Move Person’s Name in Hierarchy
In Admin Requests database select the document that is stuck and go to the menu bar, under Actions there is the option to complete the move to a new certifier (If my memory serves me correctly).
Choosing this will ask you to verify the new certifier by selecting the id.
The process should then complete.
Regards
Mac
Subject: RE: Move Person’s Name in Hierarchy
I have this same problem, whether I create the request through Admin server or using the C++ api. Either way the request never gets processed.
Initially I couldn’t find any Action menu item for complete move to a new certifier - but as an FYI I found that you had to be on the “Name view Requests” view for this option to available.
Also I am trying to using this adminp C++ API call:
RequestMoveComplete(const LNCertifier &newcertifier, const LNString &user, const LNString &organization)
→ within my C++ code but I get an exception from it even though the rest of the request is successful and the request is logged in the admin request database. Could this be a side effect of this same problem?
Thanks.