SPR

Technote

Problem:
The problem does not replicate to other servers since the design collection is
built on the fly for each replica and does not replicate. To correct the
problem if it has already occurred and to prevent future occurrences:

1. Bring down the Domino server.
2. Open the Domino Directory locally with a Notes 6.x Client who has Manager
access, mapping a network drive as necessary to have local access.
3. Restart the Domino server.
4. For any Notes 6.x Clients that have experienced the problem and can no
longer view the directory, remove the Domino Directory icon from the Workspace
and bookmarks, and then re-add it.

If you have not experienced the problem, there are two ways to prevent the
problem:

1. Upgrade all Notes 6.0 and 6.0.1 Clients who have Editor or lower access to
the Domino Directory to Notes Client 6.0.1 Critical Fix 1. The Notes Client
6.0.1 CF1 fix checks the access rights of the client. If the client doesn't
have the correct access rights to rebuild the collection, then the call to the
R5 server to delete the collection won't be allowed.

Excerpt from the Lotus Notes and Domino Release 6.0.1 CF1 fix list (available
at http://www.lotus.com/ldd):

Client
SPR# SSHE592PAE - Fixed an issue where R5 names.nsf databases were experiencing
b-tree corruption when opened with a Notes 6 client.

2. As a one time procedure to upgrade the design collection of the Domino
Directory, with the server still running, open the Domino Directory with a
Notes 6.x Client who has Manager access to the directory. This will upgrade
the design collection version and prevent the condition which causes the design
collection to be deleted.


Supporting Information:

To use NotesPeek to determine the design collection version, do the following:

1. Open the database in NotesPeek.
2. Expand Design Elements.
3. Scroll down to *Design Collection.
4. Expand *Design Collection.
5. Highlight $Version.
More >