PermaLinkFix for ND6 replication access - Thanks Jake
posted Thursday 25th, September 2003
 



Another nagging problem has been solved due to a post on Master Jake's Codestore site.

I've been having problems replicating with ND6. Tried 6.01 and 6.02 CF1 on server and client. Once in a great while, replication would work. The solution? Ensure that every entry in the ACL has the option checked for "Replicate or copy documents". Are you kidding me? OK, whatever. The bottom line is that this adjustment to the ACL does no harm (that I can see), and it fixes the problem. So I'm a happy guy.

Thanks, Jake.
Comments :
 
 

1. Posted by Ben Poole - website09/09/2007 08:43 PM



Yeah, that's a painful one: a load of us ran into that issue a while back, and the same conclusion was reached in the ND6 forum on the Lotus Developer Domain. Really weird.



2. Posted by Rock - website09/09/2007 08:43 PM



Weird that this came up this week - I submitted a PBR on it on Sept. 17th for the same thing. The problem is this: If you have the "Replicate or Copy Documents" property turned OFF for anonymous, AND the HTTP task has accessed the db recently (and still has an open thread to it), you get the replication error. If you bounce HTTP, OR enable that property on anonymous, then it works. It is the HTTP task in conjunction with that property that causes the intermittency of the problem.

Lotus has finally been able to reliably reproduce the problem, which should mean a fix is in order.

Rock