I have a problem with the names.nsf on a couple of Domino-servers. The problem is that after upgrade to 8.5 and 8.5.1 the new “settings” are missing. These settings are part of the policy.
The settings I’m talking about are “Activities”, “Lotus Traveler”, “Roaming” and “Symphoney”. These are missing and cannot be created.
One of the server with the problem is a Linux RHEL server with domino 8.5.1.
The other server is Windows 2003 64bit with 64bit Domino 8.5.
In the Domino Administrator. Example of “Add Settings” on a correctly upgraded server:
Archiving
Desktop
Registration
Mail
Security
Setup
Activities
Lotus Traveler
Roaming
Symphony
= In total 10 settings
And the problematic 8.5:
Archiving
Desktop
Registration
Mail
Security
Setup
= In total 6 settings
On one of the servers the problem seemed to be solved by upgrading names.nsf again. On the other server I have tried that a couple of times but without success.
The thing is we missed those already in 8.02 (just didn’t find out until we wanted to use Traveler).
I can’t confirm completely but it seems the following happened:
When we upgraded our servers from 6.54 to 8.02 we first upgraded the servers with the new software and then (after the first one was running 8.02) upgraded the Adressbook. It seems that we lost settings here.
We then set up a 8.51 server for traveler from the scratch for testing purpose and all the settings had been available. Unfortunately when we started with our productive system we used of course the 8.02 Adressbook and then the new Traveler server was missing that settings too.
There was no way to recreate them unless I replaced the design on the traveler server to 8.51. After the setting appeared I stripped it down to 8.02 again (we are not allowed the 8.51 template yet) and then replicated that to the other servers. Voila!
Those setting are documents and not design elements. Therefore once created they want be deleted by a design replace (but also won’t be created if something goes wrong in the beginning).
But beware: don’t copy those from another adressbook. That’s what I tried first. Bad idea because they get unique doc-ids and then you may end up with two setting docs instead of one.
So now have all the settings but still have problems that might or might not be related: There is no view for the Deny Access Group anymore. Just dissapeard. Theres anothe view that is missing (can’t remember right now). Also the desktop policy document is there but can’t be opened due to an error message upon creation of a new desktop setting.
What we are doing now is to test the 8.51 adressbook (we are still running some 7 servers) and then try to get to a clean stat somehow.
My reccomendation for those who upgrade in the future: update adressbook design before the server update or at least allow the server to upgrade it during his first start.