synchronizing replicas

[Guest]

I am fairly new at working with an access database. I am attempting to
synchronize the Design Master with a Replica and I am receiving an error
message stating 'This member of the replica set has conflicts from
synchronizing changes with other members'. I have located my MSysConflicts
file and need assistance in resolving the conflicts. I have two errors one
being, 'Update/update conflict. Another replica also updated this record. The
record lost the conflict. Either resubmit your update or delete this
conflict record' and the second one being 'Unique key violation. This record
has the same key value as another record, whereas only unique values are
permitted. Either change the key value in this conflict'. I recently had a
machine crash and when it was wiped clean and reloaded IT loaded MS 2007,
could this be creating some conflict? Any help is much appreciated.

 

[David W. Fenton]

I am fairly new at working with an access database. I am
attempting to synchronize the Design Master with a Replica and I
am receiving an error message stating 'This member of the replica
set has conflicts from synchronizing changes with other members'.
I have located my MSysConflicts file and need assistance in
resolving the conflicts. I have two errors one being,
'Update/update conflict. Another replica also updated this record.
The record lost the conflict. Either resubmit your update or
delete this conflict record' and the second one being 'Unique key
violation. This record has the same key value as another record,
whereas only unique values are permitted. Either change the key
value in this conflict'. I recently had a machine crash and when
it was wiped clean and reloaded IT loaded MS 2007, could this be
creating some conflict?

Was the replica lost on that hard drive? If so and the error comes
from that replica, then you've got a problem. The only way to
eliminate it is to delete that replica from the replica set. To do
that:

1. assuming the machine that was wiped and rebuilt has the same name
as before and the new replica is in the same location,

2. from another machine, attempt to synch with that replica.

You will get the message to the effect that the replica was "not
found -- replica deleted" and that will mark the replica as obsolete
in MSysReplicas.

Now, if you've never had but one ReplicaID in that location, one
synch like that will do the trick, and errors associated with that
ReplicaID will disapper since the replica doesn't exist any longer).
However, if you've had more than one replica in that location, you
may need to redo the attempted synch several times.

You can tell for certain which ReplicaID needs to be deleted by
checking the conflict record in MSysConflicts for the Winning and
Losing ReplicaID fields. For errors like this, I'm not exactly sure
which will be which, but it one of the ReplicaIDs should point to
one of the replicas that existed in that location. Once that one is
marked with a numeric value in the REMOVED column in MSysReplicas,
your error should disappear.

The conflict, on the other hand, ought to be easily resolvable by
just choosing one of the records to win the conflict (either the
winning record to keep things as they are, or the losing record to
revert to the other data). If, on the other hand, the conflict was
between the lost replica and another replica, the conflict will
disappear when you delete the lost replica, just as with the error.
And if that doesn't work, just delete the conflict record from its
specific conflict table (the one with the name of the table that had
the conflict, like tblPerson_Conflicts, not from the MSysConflicts
table, which you can't edit).

And a note about how to restore a replica to a rebuilt computer:

Do not ever create a new replica. Instead, use a backup, and just
copy the replica from the last backup (I assume you have backups,
right?). And you can prepare for this kind of thing by copying the
replica off the machine before its hard drive is wiped, and then
copying it back in place once it's been restored. However, be sure
that the machine name is the same as before and that the path where
you put it is exactly the same as before, or you will have wasted
your time copying it back instead of creating a new replica (if the
machine name or path is different, then you'll end up with a new
ReplicaID anyway).

 

[Guest]

David,

I have resolved my conflict errors, but now when I go to synchronize the
Design Master and the replica I receive the error message 'MS Jet database
engine cound not find MSysCompactError object. Make sure object exists and
name and path are spelled correctly'. As I said I am fairly new to all of
this. Any suggestions on how to resolve this error? I am not sure how to
locate the path for this object.
Thanks again.

 

[David W. Fenton]

I have resolved my conflict errors, but now when I go to
synchronize the Design Master and the replica I receive the error
message 'MS Jet database engine cound not find MSysCompactError
object. Make sure object exists and name and path are spelled
correctly'. As I said I am fairly new to all of this. Any
suggestions on how to resolve this error? I am not sure how to
locate the path for this object.

The MSysCompactError table is created when a compact occurs that
cannot fully recover the internal data structures of the source MDB.
That table includes records that define each error that occurred.
This allows you to track down and, perhaps, recover any lost data.

Now, the error you're getting sounds like an out-of-date tables
collection somewhere. I'd make a backup and do a compact.

Did you know that you'd had compact errors? I'm pretty sure Access
tells you when it opens a compacted database with an
MSysCompactErrors table.

Not sure if it's a replicated table (don't think it ought to be), so
I don't know why it's prohibiting a synch.

But try the compact first.

If that doesn't fix it, try creating a new replica from one of them.
I doubt it will be able to do so, but if it can, perhaps you can use
those to replace the ones that are broken.