Re: Exceeded maximum days for replication

"Nick Rivers" <Luke.Crownover@xxxxxxxxx> wrote in
news:1168897554.170981.20730@xxxxxxxxxxxxxxxxxxxxxxxxxxx:

Greetings all,

I have a bit of a problem that I've inherited and at a loss of
what to do.

I have 2 Access 2000 databases that can't synchronize; they were
left alone for too long:

"This member of the replica set has exceeded the maximum number of
days allowed between synchronizations and can't be synchronized
with any other members of the replica set."

Additionally, the 2 databases are replicas. I'm not sure what was
done with the design master. I can promote one of the replicas to
the design master, but the above error about "..exceeded the
maximum number of days.." still shows up.

(I had hoped to promote one database to design master and manually
copy the 2nd replicas records into it {the records are
discernible} and restart replication)

Any ideas?

Is there any way to turn this error off and let the databases
synch up?

No. I've only had a replica expire once, and it was disposable (just
a development copy), so I just replaced it from another replica in
the set (which had been regularly synched). If both have expired,
and you can't create new replicas, then I'd say you are forced to
recreate the replica set. Find out which replica has the latest
data, import its data into a new MDB, then manually apply the
updates from the other replica.

The default retention period is 1000 days. If two replicas have not
needed to be synched in that time period, then I question whether or
not there's actually any need at all for replication.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
.

Relevant Pages

  • Higher Level
    ... I want to replicate a database on server A to server B ... I can use Visual Basic and JRO to create a replica. ... It does synchronize on it's own, because if Access is not open, there is nothing running that would know to synchronize. ... Assuming this is all accurate, I could create a service/timed program to run on either of those servers, or a server that has can read both databases, using JRO, that would kick of the synchronization at least once a month. ...
    (microsoft.public.access.replication)
  • Weird replica problem.
    ... replica for the plant. ... >I'm getting a weird message with a one of our databases. ... >each plant we have a farm. ... >and the production db) synchronize every 15 minutes. ...
    (microsoft.public.access.replication)
  • Re: Disaster recovery without backup but just files .edb & .stm
    ... a dirty shutdown state, you can't do anything other than a hard repair ... because Replistor copy data in synchrone mode ... ... If you shut down the Exchange server at the source the replica should ... The /r does just what mounting the databases would do, ...
    (microsoft.public.exchange.admin)
  • Re: Disaster recovery without backup but just files .edb & .stm
    ... a dirty shutdown state, you can't do anything other than a hard repair ... because Replistor copy data in synchrone mode ... ... If you shut down the Exchange server at the source the replica should ... The /r does just what mounting the databases would do, ...
    (microsoft.public.exchange.admin)
  • Re: Disaster recovery without backup but just files .edb & .stm
    ... a dirty shutdown state, you can't do anything other than a hard repair ... because Replistor copy data in synchrone mode ... ... If you shut down the Exchange server at the source the replica should ... The /r does just what mounting the databases would do, ...
    (microsoft.public.exchange.admin)