I have one user (out of about 25, all using local replicas) that has a document in her db that is not on the server. No replication formulas, no replication settings, full send-receive, 15 minute replication schedule.
I refreshed the view index on her machine, but it’s still there. Actually, it shows in more than one view.
I’m stumped. What would prevent it from replicating?
Subject: Documents that were modified before the replication cutoff interval will not replicate.
That period is typically 90 days. Did she play around with her system clock recently? Verify the time/date on her machine and try having her edit the document again.
Subject: RE: Documents that were modified before the replication cutoff interval will not replicate.
I’ve seen the ACL entry mess this up even though it looks correct. Simply delete the user from the ACL, close the ACL, open it again and re-add the user.
Subject: RE: Documents that were modified before the replication cutoff interval will not replicate.
And if all of the above does not work, verify there are no reader fields in the document, this could cause this behavoir as well. If you use readers fields, and you do not have the server listed as a reader, the document will not replicate. Just a thought.
Subject: RE: Documents that were modified before the replication cutoff interval will not replicate.
Don’t know if this is your situation, but I had 2 users who were trying to replicate locally and were not able to because of corrupt documents. I deleted the local copy and then created a new copy of their mail file, deleted the mail file on the server and copied the new copy to the server. They were then able to replciate locally.
Subject: Why won’t this one doc replicate to the server?
Robert,
Try clearing the Replication History on BOTH the Local and Server copies and then try replicaion again. Also, be sure to clear the date on the Other tabs too.
Well, the user with the orphan document was able to edit it, and then saving it caused it to be replicated to the server. So, I don’t really know why it wouldn’t replicate before, but it looks like it did have something to do with the last saved date.