Just upgraded 2 servers from 4.6 to 6.01. From Administrator, on Server 1, People & Groups, I can open person documents and see everything as I would expect on the seven tabs.
From Server 2’s directory replica, same view, etc., I open a document and see only the UserID attachment. No tabs, no field names, just the person’s name at the top and the ID attachment underneath.
Okay, just to check, I went a step further. Opening the directory replicas in the Notes 6 client, it’s the same story.
Do you think it’s an access control issue, or a design issue? I’ve looked into both, but not found a significant difference.
The design template is listed by both replicas as “StdR4PublicAddressBook”. Is that correct?
Subject: All person docs are blank!
I had the same problem with groups. It was as though the new design of the NAB did not take.
Have a look in the redbook “Upgrading to Lotus Notes and Domino 6”. In section “6.6 Before restarting the server: Post upgrade tasks” there. In summary:
\data directory\c:\lotus\domino\nfixup names.nsf -f -j -v -l
\data directory\c:\lotus\domino\nfixup admin4.nsf -f -j -v -l
\data directory\c:\lotus\domino\ncompact names.nsf -c -i -K -F
\data directory\c:\lotus\domino\ncompact admin4.nsf -c -i -K -F
\data directory\c:\lotus\domino\nupdall names.nsf -R
\data directory\c:\lotus\domino\nupdall admin4.nsf -R
The redbooks may be found at IBM Redbooks
Subject: Person docs are fixed!
John, you’re right. I did follow this procedure when I performed the upgrade, but doing it again did the trick.
Thanks,
LD
Subject: All person docs are blank!
I saw this, too, right after upgrading my second (clustered) server from R5 to R6. I left it alone for a while because the server was still functioning properly – even though I couldn’t see the information contained in the Person docs, I could right-click on doc properties and see that everything was there and the server was still servicing users, replicating, etc. If memory serves, I did the basic tricks (refresh/replace design of the NAB, updall, etc.) but none worked, so I eventually shut that second server down and pulled a new replica (or did an OS copy) of the NAB from the “good” server. Not necessarily a good answer from an administrators point of view, but it worked.