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: 763
  • Last Modified:

Replication failed. The search key was not found in any record.

Hello,

I am using Ms Access 2003 running on windows xp professional sp2 and I have a trouble with the replication between 2 replicas. When I tried to synchronize 2 replica I have a got an error message " The synchronize between replica replica1 and replica2 failed" The search key was not found in any record.

I have also checked there is no any memo field indexed.

Could you help please?

Best regards

Anouphone
0
Anouphone
Asked:
Anouphone
1 Solution
 
rockiroadsCommented:
With regards to sync-ing over the net, there is a known bug and the solution is to install the lastest service pack for jet database. This may be a similar problem.

Have you tried updating to the latest service pack? http://support.microsoft.com/kb/239114


0
 
AnouphoneAuthor Commented:
Dockiroads,

thanks you for your response.
I have check my jet service pack version 8.

Best regards
0
 
Rick_RickardsCommented:
It sounds like one of two things happened.  Either the replica expired or it has become corrupt.  Unfortunately there aren't many good solutions to fix the problem beyond methods by which you can move on.  

The first and most difficult thing to come to grips with is that the two replicas will most likely never synchronize properly again.  That being the case the main question is which replica has the most current set of data.  As long as both are Global replicas you need not stick to the Design Master if the other Global Replica has the most current set of data.  If you preserve the Design Master you can create a new replica from it and dispose of the other replica previously used once you've extracted all the data you want from it manually into the Design Master.

If you want to preserve the other copy (not the Design Master) you can do that as long as it's a Global Replica.  In such a case you can select Recover Design Master from the Replication Menu, create a new replica from it and if you want to latter declare the replica just created as the design master you can do that by going through exactly the same steps as before, just remember to sychronize immediately after so that the old Design Master is aware that it has been demoted.

If there is any data in the copy you rendered obsolete you'll need to ether re-enter the data or insert it using queries.  As a temporary stopgap measure you can link to the obsolete copy and then run update queries to capture any critical data.  Sadly this can get messy if there is a lot of data to copy but hopefully you synchronize with some regularity (although if you do it's not likely one copy simply expired - yes they will expire past a certain date).  Usually replicas will expire if they have not synchronized with (I believe) 61 or 91 days (honestly I don't remember exactly).  As a general rule I encourage anyone who uses replication to synchronize before they start working with their copy so they get the most up-to-date data and then synchronize immediately when they are done for the day (so they pass on all of their changes).

Oh one last thing.  In addition to Service Pack 8 you should be aware that there is an additional service pack specifically for Replication Above and beyond Jet 4.0 SP8.  It is the "Jet 4.0 Service Pack 8 (SP8) Replication File Update - KB321076"  http://support.microsoft.com/kb/321076

Hope this helps, just let me know if you have any questions.  

0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

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