We upgraded from R5.0.11 about a month ago. The servers build number has yet to update on the server document. AdminP message says: Place Server’s Notes Build Number into Server Record - Title: servers Address Book File name: /server/NOTES/DATA/names.nsf; Error: You are not authorized to perform that operation.
The server id has manager access to the NAB and the Admin Process dbs. Not sure where else to look. Currently All AdminP processes are failing with this message.
Subject: AdminP process fails to update Server build number and all other Admin Requests after upgrade
As a security enhancement in 6.0 adminp started opening and updating databases with the identity of the Administration Request’s signer. What the message is saying is that the signer of the request (the server whose build number is being updated) does not have the rights to update its server document. You have to give this server rights to update its document either by giving in Editor access in the ACL of the NAB or by adding its name to the Administrators or owners field of its server document
Subject: RE: AdminP process fails to update Server build number and all other Admin Requests after upgrade
Still fails. Server has manager access to the NAB and we updated server doc to have the server listed as the owner and administrator. Any ideas?
Subject: RE: AdminP process fails to update Server build number and all other Admin Requests after upgrade
I figured out the problem in my case, under R5 we had an agent that required an entry in the address book for the server as a “person” document. The agent sent out messages on the server’s behalf, and the person document that listed the servers name gave it a target mail file to dump responses, failed messages, whatever. If I rename this “person” document that contains the servers name, admip works fine, but if I put the “person” document back to reflect the name of the server, admip breaks again. Apparently R6 can not tell the difference from a server as a server, and a person named after a server. This was never a problem under R5, and it worked fine, but now it no longer does. Something to put on your bug fix list I do believe.
Subject: ditto … needs to put on the bug list and fixed
Subject: RE: AdminP process fails to update Server build number and all other Admin Requests after upgrade
I am using Domino R702fp1 in mixed Win/aix enviornment. Adminp still does not add the release to the server doc, even with the server name in the admin/owners field.
Subject: RE: AdminP process fails to update Server build number and all other Admin Requests after upgrade
I have been experiencing the same issue on Domino 7.0.2 FP1 and found that I had a person document with the same name as the server. Once I deleted this person document, the server build number updated.
Subject: My solution to AdminP process fails to update Server build number and all other Admin Requests after upgrade
I had the same problem. Servers from 6.5.2 up to 7.0.2. There are also Persondocuments with different Lastnames but with an entry in the Username field exactly like the servername. Changing this entry and AdminP is running.
Hth
Sebastian
Subject: RE: My solution to AdminP process fails to update Server build number and all other Admin Requests after upgrade
Or
An AdminP request is not generated to update the client build information in the Person document
Server build number is blank or incorrect in Server document
JYR