Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 345
  • Last Modified:

Time limit for synchronisation?

My replicated database cannot be synchronisaed - error 3521 is generated.
Two members of the replica set cannot be synchronized because there is no common point to start the synchronization.
Access says that this is because too much time has elapsed between synchronisations.

Is there any way of overcoming this problem?
0
vivn
Asked:
vivn
  • 3
  • 2
1 Solution
 
Jim Dettman (Microsoft MVP/ EE MVE)PresidentCommented:
What version of Access are we talking about and how old are the replicas?

Jim.
0
 
Jim Dettman (Microsoft MVP/ EE MVE)PresidentCommented:
Just to get things started, here is a MSKB article link on one possible cause of the problem you describe:

ACC97: No Common Point to Synchronize Replicas After Year 2000 (Q191916)

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q191916

Jim.
0
 
nico5038Commented:
Wooow, a real Year 2000 problem if we may believe M$ and who doesn't....
Using the SP doesn't solve this particular problem, so all that "rests" is to create a new replica and "manually" (or by using queries) append the entries to synchronize again after the SP has been implemented... ;-(

Nic;o)
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
vivnAuthor Commented:
This is an Access 97 database - I'm not sure when it was last syncronised but I think it was 3-4 weeks ago.

I thought that I may have to manually resynch using queries but hoped there may be another way round.
0
 
Jim Dettman (Microsoft MVP/ EE MVE)PresidentCommented:
Is this the only MDB that won't sync or is it all on that machine or don't you know for sure?

Also, was this indirect or direct?

Jim.
0
 
vivnAuthor Commented:
Jim

I think you hit the nail on the head with the MSKB article.

Of the four replicas only 2 are giving this error message.
We think the 2 causing the problem were created before 2000 whereas the other 2 were definately created after 2000.
The problem seems to have arisen after the design master was compacted (as described in the MSKB article).

Viv

 
 
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now