3167 error - record is deleted in replicated database

Have a system with about 25 users having replicated databases on
laptops. when they connect to the lan and open the app, it direct
syncs on a LAN based replica which is located in the same building
with 100 mbps ethernet connections. I actually have the people in
three locations, each syncing to a server db at their location. Each
server has a cluster of 3 replicas that are synced hourly and hourly
the three different clusters are synced together.

Recently have found two instances of databases that will no longer
sync to the server. Error 3167 - record is deleted.

1)I am using Access 2000 file format. Is the Access 2002/2003 format
more reliable?

Yes I use memo fields. Unfortunately I was forced into it by user
requirements.


2) Any good ways to find out the source of the problem and manually
repair it? So far, I think I can find the table in error by trying to
import all tables into another clean database. But it doesn't
identify the record.

3) Anyone have any good utilities/code for comparing the table
contents in two databases to find differences?

3b) Any code to apply differences to another copy of the database?

4) Anyone using replicated copies on laptops use a cluster on the
laptop?

Bob

.

Relevant Pages

  • 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)
  • 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)
Loading