RE: Premature Replica Expiration
From: KimL (KimL_at_discussions.microsoft.com)
Date: 02/07/05
- Previous message: KimL: "Premature Replica Expiration"
- In reply to: KimL: "Premature Replica Expiration"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 7 Feb 2005 10:13:02 -0800
I should have mentioned that these are all Internet synchronizations. Kim
"KimL" wrote:
> I have a replicated database application using an Access 2000 front end with
> about 100 users. The current replica set has been in operation since
> November 2003. Last week users began reporting that they were receiving
> replica expired errors.
>
> The application uses JRO to sync under WinXP and DAO under Win2K. This
> problem seems to occur with both methods. The retention time for the replica
> set is 60 days. Replicas have been marked by the system as expired that were
> synchronized as few as 5 or 6 days prior.
>
> The replica set has shown no signs of curruption and there are currently no
> conflicts. Only d ata is included, no design changes are ever synchronized.
> There is only one design master.
>
> Please let me know if you have any idea what would cause replicas to be
> marked as expired long before the retention period is reached and if you know
> of a solution.
>
> Thanks much, Kim.
>
- Previous message: KimL: "Premature Replica Expiration"
- In reply to: KimL: "Premature Replica Expiration"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
