Hi,
i need some advice which settings, fields can affect such problem.
This happened also on R5, and is still happening in R6.
We have a Content Management System implemented in Notes, where there is a database for the editors for manipulating the documents, a database for all for reading the documents and a database for protocolling the versions. On our main Notes server there is one replica of editors, readers and protocoll database, on two other servers there is only a replica of the readers database. The replic conflict happens in the readers database. As we have the problems for some time, we decided that there is only a push from the main server to the two others. So a possible replic conflict cannot be replicated back.
The form itself has the setting to generate a replic conflict! But this is not the problem i think.
Now what happens:
Author 1 generates a new document and set the document active. In this process a doc.CopyToDatabase is called to the reader database and the protocoll database. Everything works fine.
Three days later an another author 2 generates a new version of this document. He publishes the document which does the following: Remove the document in the reader database, and copies the new document again in the reader database, and copies the new version in the protocoll database. This is done at 1:00 PM without any error message (i put some error message in the code in the case the delete does not work or if after the copy there are more than one document).
And after a while, there is a replication conflict in this document. The replication document is old version modified at 2:00 PM by author 1. But this information is wrong! Author 1 can not have edited the document.
Proof: There is no replication conflict in the editors database nor in the protocoll database, the time stamp of the document in the editors database is 1:00 PM, the author of this document is author 2, in the protocoll database there are only 2 versions.
There is no periodically agent running in the readers database, in the editors database there are some, but they do not affect the above document
The ACL of the readers database allows all users to generate documents, as printing change the form. And there are several local replicas of several users.
Thanks for your help,
Markus Stroebel