Notes/Domino Fix List
 |  |
| SPR # VDES6H9JA9 | Fixed in 6.5.6; 6.5.5 FP2; 7.0.2 release |  |
Product Area: Server Technical Area: Editor Platform: Cross Platform
Lotus Customer Support APAR: LO10653
SPR# VDES6H9JA9 - Under some situations $Writers replicates to replica servers, but never gets removed when the note is unlocked.
Technote Number: 1236863
Problem:
It is expected that documents will be unlocked on all replicas when unlocked on
the replica from which the user accessed the document. The fact that unlocking
is not occurring on all replicas was reported to Quality Engineering as SPR#
VDES6H9JA9, and has been fixed in Lotus® Domino® 7.0.2, 6.5.5 Fix Pack 2 (FP2)
and 6.5.6.
Excerpt from the Lotus Notes and Domino Release 7.0.2 MR fix list (available at
http://www.ibm.com/developerworks/lotus):
Editor
SPR# VDES6H9JA9 - Under some situations $Writers replicates to replica servers,
but never gets removed when the note is unlocked.
Refer to the Upgrade Central site for details on upgrading Notes/Domino.
Supporting Information:
To unlock documents which are not intended to be locked, a manager can select
the document, and then select Actions -> Unlock Document from the menu.
To avoid this issue in the future, disable the "Allow document locking"
property.
Other issues involving document locking:
Issue #1:
Locking problem where if a user locks a document on one replica, then edits the
same document on another server, a conflict warning will be generated:
"Another copy of this document was saved while you were editing it. Save your
changes also as a save conflict document?"
This scenario should not generate a conflict. Note: In some cases this
scenario produced a client crash when attempting to save the document on the
second client. This issue has been fixed in Notes/Domino release 6.5.5 and 7.0
Editor
MYAA67V75N - Fixed a note locking problem where if a user locks a document on
one replica, then edits the same document on another server, a conflict warning
will be generated. This scenario should not generate a conflict.
Issue #2:
Under certain conditions attempting to open a document returns the following
error:
"Document is locked by <username/...>"
This can occur in cases where a document contained multiple $Writers, which
causes it to stay locked when it should be unlocked. This issue has been fixed
in Notes/Domino releases 6.5.6 and 7.0.1.
Database
BSPR6G8KSA - Fixed a problem where a note might get multiple $Writers.
Issue #3:
Attempting to edit a document in island mode, or when client is off-line,
returns the following error:
"Document has been modified since opening, reopen in edit mode from view"
This issue has been fixed in Notes/Domino releases 6.5.5 and 7.0.
Editor
SIWA5TT4NS - Fixed a problem where users could not change a document to edit
mode in a local replica when document locking was enabled. More >
Last Modified on 10/29/2015
Go back
|