Hi, We have a Notes application enabled the doc locking at database properties and no lock statement specified within any sub-routine. The server v 6.0.3 handle the lock and unlock automatically.
Sometime, we still receive replication conflict issue and today we receive “Changes made to database have NOT been incorporated into the database. There was a conflict detected. Your changes may be found in body of this message. A document link to the original document is attached to the end of the messag” error. The document is still remained lock and I have to ask for the document owner to do a dummy amendment to tick the system to release the lock when he is done.
Anyone know what is the problem? Server bug or something else. Please help.
It’s a feature, not a bug. Someone made a change to a document and wasn’t able to automatically obtain a lock from the server (usually due to network issues or the server was down/unreachable, etc.). They got a dialogbox asking them if they want to take out a provisional lock, which they probably clicked “Yes” for. However, someone else got a ‘real’ lock before the prvisional lock from the other user could get promoted to a real lock, made a change and when the other user with the prvisional lock tried to save his/her changes, the conflict occured.
When will the document being unlock? The problem is the doc is still locked over 2 days and the owner tried to make a change and save it again but no luck, it created another conflict and the doc is still locked. How can we unlock it? I tried to run a agent to unlock it but I am not the doc owner…can’t do it.
Yes, but why is Notes/Domino not able to release the document when closing the document?
Locks should only be set when documents are edited, not browsed.
Off course the client (Notes/Web) could crash and then fail to release the lock, but this never occured here. But I still receive these “conflict messages”.