And you’ve removed ALL connection documents that could be causing this and you’ve also gone and removed all traces of the obsolete servers from the events4.nsf database and from the ddm.nsf collection hierarchy? You must be running DDM my friend.
Check out this technote then from IBM / Lotus. I went through and wholesale deleted all of the docs from the hidden $vwStatus view, restarted the Event Monitor task and FINALLY the errant replication attempts have ceased.
I suppose it prevents you from messing things up by having this independent mechanism for ensuring replication rather than the DDM creating a bunch of connection documents that you could then alter and mess up. But the nonstandard replication approach is a bit of a pain to figure out initially.
I’m posting this entry here to increase the likelihood of others stumbling upon the above technote in their quest to resolve this issue.
Posted under Lotus Domino
This post was written by Marc
on May 30, 2008 at 1:22 am