Notes/Domino Fix List
 |  |
| SPR # RTIN5U2SAJ | Fixed in 6.5.5 release | Security fix |
Product Area: Server Technical Area: Server Administration Platform: Cross Platform
Lotus Customer Support APAR: PQ95866
SPR# RTIN5U2SAJ - Fixed server crash which occurred when compact was executed from the client.
Technote Number: 1155450
Problem:
This issue was reported to Quality Engineering as SPR #RTIN5U2SAJ and has been
fixed in release 6.5.5.
Excerpt from the Lotus Notes and Domino Release 6.5.5 MR fix list (available at
http://www.ibm.com/developerworks/lotus):
Server Administration
SPR# RTIN5U2SAJ - Fixed server crash which occurred when compact was executed
from the client.
Refer to the Upgrade Central site for details on upgrading Notes/Domino.
In releases prior to 6.5.5, there are two known scenarios that can result in
this issue:
Issue #1:
This issue can be related to an organizational policy that contains archive
settings.
If the archive settings have been set to "Prohibit Archiving" but the
"Schedule" tab is set to "Enable client based archiving", the schedule settings
are still honored and the Notes client (when logged into the Domino server)
still attempts to honor those settings and attempts to archive. This archive
attempt leads to a compact attempt against each mail file on the server.
To work around this issue, when setting up a policy with archive settings,
deselect (i.e. remove the check from) the "Enable client based archiving"
option on the Schedule tab before saving the settings.
Issue #2:
This issue can occur if you have set up an archiving policy for server-based
archiving. When creating the archive setting, the Schedule tab will disappear
but the setting for "Enable client based archiving" continues to be honored.
This causes Compact to execute at 12:00 PM (noon) every Tuesday.
To work around this issue, deselect (i.e. remove the check mark from) the
"Enable client based archiving" on the Schedule tab of the Archive settings
document. Then choose the server-based archiving on the Basics tab.
This issue seems to be driven by policies. Some users may have old policy
settings. An administrator should follow these directions (ideally during off
hours to ensure all users will have to reauthenticate with the home server to
pull the new policy):
1. On the Administration server of the Domino directory, edit all of the
Archive setting documents that may have specified the "Enable client based
scheduled archiving" setting at some point in time. You can use Document
Properties, check the field Enabled and ensure that it is not set to 1. Even
if server-based archiving is chosen, it is not turned off
automatically.
2. Replicate the Domino directory to all servers that are home mail servers,
to the users in the domain.
3. Issue a "drop all" command on all servers that are replicated with the
Domino directory and are mail servers. This will force end users to
reauthenticate with their home server and to pull a new set of policies. Any
time a policy or setting is changed, drop users and replicate the Domino
directory. If, for some reason, you do not think policies are being updated
locally, touch the policy on the server (even modify the description), drop all
users and replicate. Users should get the new policy settings when they
reauthenicate with their home server.
Please note that a fix was put into Domino release 6.0.2 that creates the
Program document in the local names.nsf. A feature to clear out "client
archiving" fields when client archiving is not enabled is being considered for
a future release of Notes/Domino. More >
Last Modified on 12/10/2013
Go back
|