AdminP failed to update the Notes Build number

Hy

Upgraded a server from 5.0.10 to 6.0, I have still an error message on the server:

Admin Process: Received the following error performing a Place Server’s Notes Build Number into Server Record request on XXX (File name: d:\lotus\notes\data\names.nsf): You are not authorized to perform that operation

Server has manager access to names.nsf, admin4.nsf with all roles assigned.

Signer of the admin doc is of course the Server XXX.

Document created:

Action: Set Directory Filename

Action requested by: XXX

Server responding to request: XXX

Start time: 17:26:05 Heute

End time: 17:26:05 Heute

Errors: Title: XXX’s Address Book File name: d:\lotus\notes\data\names.nsf; Error: You are not authorized to perform that operation

Has anyone an idea why it fails?

Thanks for any hints

Heinz

Subject: AdminP failed to update the Notes Build number

Is that server also the Administration Server for the PAB (Names.nsf) and for the Administration Requests database (Admin4.nsf)?

From memory that is one failure that can present this message and stop the changes taking place.

If you look in the ACL, is there a key symbol attached to the Server Icon?

Regards,

Mike

Mike Kemp

Lotus Notes Specialist

mikejkemp@aol.com

Subject: IRIS Please HELP:AdminP failed to update the Notes Build number

Yes this is the admin server for the PAB and for the admin4.nsf.Yes in the ACL of both db’s, there exists a key symbol in the server entry.

Absolutely for sure, server XXX is admin server for both databases. I have also deleted the admin4.nsf and restarted the server (admin4.nsf was agin created of course).

What else?

kind regards

Subject: AdminP failed to update the Notes Build number

Somehow the server is has no access to his own server doc…

Checked also the public key (they are the same in the serverXXX.ID and server document - also in the O-Cert.ID and Notes certification document).

What else?

Subject: RE: AdminP failed to update the Notes Build number

Checked the ACL again and again…Figured out that it works if I set the ACL of the server in the server directory to unspecified. Why?

Thanks for responses

Heinz