Log Type = Replica set member past expiration date

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Ingo Hueser via AccessMonster.com (forum_at_AccessMonster.com)
Date: 01/17/05

  • Next message: Ingo Hueser via AccessMonster.com: "Unmanaged replica is being synchronized violently" 
    Date: Mon, 17 Jan 2005 14:34:21 GMT

    We have a replica set with a number of replicas synchronizing frequently and directly within the company network and some replicas on remote machines synchronizing indirectly. The set is managed with the Replication Mgr. In addition, we set up a replica farm according to the suggestions by Michael Kaplan. This worked well for 3 months now, however, suddenly weird things happen. First one replica turned out to be corrupt, and then we found a whole range of replicas (all part of the internal network synchronizing directly with the replica farm) whose ReplicaID expiration date apparently has passed (at least the log file says so). What does that mean? How could we avoid this happening again? Thanks a lot for your advice!!!! 

    -- 
Message posted via http://www.accessmonster.com
  • Next message: Ingo Hueser via AccessMonster.com: "Unmanaged replica is being synchronized violently"