You find some of your servers are still trying to replicate like crazy with servers you’ve removed from your Domino Domain?

Lotus Notes LogoAnd 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


1 Comment so far

  1. Sven Harlfinger September 29, 2008 9:19 am

    Hello Marc

    I encountered the same issue with an office server we demoted some weeks ago. It almost drove me insane to see all of those replication errors on the console.

    After running through all the server docs and config databases for hours i finally registered a new server with the name of the already deleted one. Then we replicated the new one with our admin server and afterwards deleted the newly registered machine again. Finally the problem disappeared.

    I have added your problem solver to our technical documentation databases though.

    Thanks for posting this piece of information.

    Best regards,


Leave a Comment

Name (required)

Email (required)



More Blog Posts