We use Commomstore for archiving. There are a few users who are getting replication save conflicts immediately following archiving documents. The document properties indicate that the user was last to modify the document. Has aynone seen this before.
Also, does anyone know of any Commonstore knowledge databasea on the web…thanks…Wayne W
Subject: Commonstore - replication conflicts
I assume that you’re using user managed archiving rather than scheduled and are stubbing documents? A guess is that the user is still in the message when CommonStore hits it, and if that is the problem you could mitigate it by adding a close document to the action you’re using to kick off the archiving request.