After I upgraded my servers to Release 6.0.1 from 5.0.11 I noticed that my Mail server shows Release 6.0.1 in Administrator/All Server Docs. My other two servers that I also upgraded the same exact way still show Release 5.0.11 in the Administrator client. What went wrong or what do I need to change still?
Thanks,
Dan Koopman
Subject: After upgrade, Config still shows old Release
Thanks for the help. I looked in the Administration Request Database. I’m going to give the server some time to update itself. I only updated these servers this week and turned on Replication again last night. I’ll leave it for the weekend and if that does not work then I’m going to edit the templete for the NAB. Thanks again.
Dan Koopman
Subject: This should be easier
Instead of modifying your NAB design, try this:
Open up admin4.nsf on the administration server for your NAB.
Go to the Requests\All Requests by Action view. (this is the R6 view, R5 may be different)
Look for “Put/Place Server’s Notes Build Number into Server Record” and find the server that the action is suppose to perform on.
If you see that it’s already completed, click on “Perform request again”.
Save and close document. and AdminP will run again according to your Server’s AdminP interval (60 minutes is the default).
If it still doesn’t work, it means that something isn’t set up correctly. You could modify the template, but that still doesn’t correct the initial problem. It may be more work to track it down, but once you do, AdminP will be a properly working tool for you (automatically deleting dbs and replicas, created replicas, modifying ACL entries, etc.)
Hope this helps.
Scott Thompson
PCLP R4,R5
SET Consulting
Subject: After upgrade, Config still shows old Release
The field that contains those values is updated by the Administation process on each server. It should get updated according to the interval setting for AdminP in your server doc. Also, you should be replicating your admin4.nsf databases between all servers. If you’re not doing that right now, and you start repping them, be aware that “new” requests for that server(which are really old requests datewise)will try to run again on the new server.
Here’s a blurb from the Admin Help db.
Place server’s Notes build number into Server record
Triggered by: A server starting up and recognizing that it’s running a Lotus Domino Server build that differs from the build running at the last server startup.
Carried out on: The administration server for the Domino Database.
Carried out: According to the “Interval” setting for the Administration Process in the Server document.
Result: Populates the “Server build” field on the Server document.
Subject: After upgrade, Config still shows old Release
This happens frequently.
Edit the server form in the NAB (or NAB template) to make the version field editable.
Once you can edit blank it out and save the server record.
The Admin process should re-populate it shortly (but not immediately).