Solved

Time limit for synchronisation?

Posted on 2002-03-19
6
323 Views
Last Modified: 2012-06-22
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
Comment
Question by:vivn
  • 3
  • 2
6 Comments
 
LVL 57
ID: 6879837
What version of Access are we talking about and how old are the replicas?

Jim.
0
 
LVL 57

Accepted Solution

by:
Jim Dettman (Microsoft MVP/ EE MVE) earned 100 total points
ID: 6879849
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
 
LVL 54

Expert Comment

by:nico5038
ID: 6879885
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
Use Case: Protecting a Hybrid Cloud Infrastructure

Microsoft Azure is rapidly becoming the norm in dynamic IT environments. This document describes the challenges that organizations face when protecting data in a hybrid cloud IT environment and presents a use case to demonstrate how Acronis Backup protects all data.

 

Author Comment

by:vivn
ID: 6880247
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
 
LVL 57
ID: 6880289
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
 

Author Comment

by:vivn
ID: 6882188
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

Networking for the Cloud Era

Join Microsoft and Riverbed for a discussion and demonstration of enhancements to SteelConnect:
-One-click orchestration and cloud connectivity in Azure environments
-Tight integration of SD-WAN and WAN optimization capabilities
-Scalability and resiliency equal to a data center

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

In the previous article, Using a Critera Form to Filter Records (http://www.experts-exchange.com/A_6069.html), the form was basically a data container storing user input, which queries and other database objects could read. The form had to remain op…
Overview: This article:       (a) explains one principle method to cross-reference invoice items in Quickbooks®       (b) explores the reasons one might need to cross-reference invoice items       (c) provides a sample process for creating a M…
Familiarize people with the process of utilizing SQL Server stored procedures from within Microsoft Access. Microsoft Access is a very powerful client/server development tool. One of the SQL Server objects that you can interact with from within Micr…
In Microsoft Access, learn how to “cascade” or have the displayed data of one combo control depend upon what’s entered in another. Base the dependent combo on a query for its row source: Add a reference to the first combo on the form as criteria i…

820 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question