PC Review


Reply
Thread Tools Rate Thread

Database fails to synchronize, Search key not found, error 3709

 
 
Alchemy
Guest
Posts: n/a
 
      2nd Jul 2009
G'day All, I hope someone can shed some light on a problem I'm having
with a MS Access 2003 (Access 2002 - 2003 file format - *.mdb)
database.

Background:
I have a split database (back-end tables only) that is replicated /
synchronized about four times a week (between two geographical sites)
over a VPN. UI are located on users (10) PCs. Both databases (Master
and Replica) reside on a MS Small Business Server 2003 SP 2
(msjet40.dll version 4.0.9505.0). The database is approximately 110
Mb and consists of many tables with relationships (one-to-one and one-
to-many). There are tables that have memo fields, none of which are
indexed. I have check & then rechecked that there are no index memo
fields.

When I try to replicate / synchronise the databases (which takes
approximately 30 mins) the following error is displayed: The Search
Key was not found in any record. (Help = Error 3709). I have tried to
replicate / synchronise from both sites. Same error is displayed on
both sites.

I have "compact and repaired" both databases, yet the problem
continues.

I've reviewed the following kb articles:
http://support.microsoft.com/kb/302525
http://support.microsoft.com/kb/301474/en-us
http://support.microsoft.com/kb/239114/

I have also reviewed other information on the internet but have been
unsuccessful in getting the databases to replicate. Over a thousand
records have been added / edited across the sites - so I really need
to replicate the databases ASAP.

Any assistance will be appreciated – even if someone can tell me how
to determine which table is corrupted, surely that would be a start.
If I can’t replicate the databases I will have to manually update the
database across the two sites...... (using queries); I lifetime of
hurt ahead of me if I can’t fix this issue.

Alchemy
 
Reply With Quote
 
 
 
 
David W. Fenton
Guest
Posts: n/a
 
      2nd Jul 2009
Alchemy <(E-Mail Removed)> wrote in
news:072d677a-6fe4-4f26-9372-(E-Mail Removed)
m:

> Background:
> I have a split database (back-end tables only) that is replicated
> / synchronized about four times a week (between two geographical
> sites) over a VPN. UI are located on users (10) PCs. Both
> databases (Master and Replica) reside on a MS Small Business
> Server 2003 SP 2 (msjet40.dll version 4.0.9505.0). The database
> is approximately 110 Mb and consists of many tables with
> relationships (one-to-one and one- to-many). There are tables
> that have memo fields, none of which are indexed. I have check &
> then rechecked that there are no index memo fields.
>
> When I try to replicate / synchronise the databases (which takes
> approximately 30 mins) the following error is displayed: The
> Search Key was not found in any record. (Help = Error 3709). I
> have tried to replicate / synchronise from both sites. Same error
> is displayed on both sites.


If the synch is taking 30 minutes, you're pretty clearly
synchronizing using direct replication, and you're doing it across a
WAN connection. This is the wrong way to do it -- direct replication
is viable only on a wired LAN with at least 10Mbps of bandwidth.
Anything else is extremely dangerous, because a direct synch opens
the remote replica across the wire, and any hiccup in the connection
will likely corrupt the remote replica.

Whether or not that's the cause of the present error I can't say (I
doubt it), but the point is you need to change your synchronization
methods ASAP or you're asking for grief in the long run.

> I have "compact and repaired" both databases, yet the problem
> continues.
>
> I've reviewed the following kb articles:
> http://support.microsoft.com/kb/302525
> http://support.microsoft.com/kb/301474/en-us
> http://support.microsoft.com/kb/239114/
>
> I have also reviewed other information on the internet but have
> been unsuccessful in getting the databases to replicate. Over a
> thousand records have been added / edited across the sites - so I
> really need to replicate the databases ASAP.


I have seen the error message in question triggered by mismatched
workgroup files.

> Any assistance will be appreciated – even if someone can tell me
> how to determine which table is corrupted, surely that would be a
> start. If I can’t replicate the databases I will have to manually
> update the database across the two sites...... (using queries); I
> lifetime of hurt ahead of me if I can’t fix this issue.


Can you create new replicas? If so, can those replicas synch?

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
 
Reply With Quote
Reply

Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Error 3709 - Search key was not found in any record David Microsoft Access Form Coding 0 5th Nov 2008 08:38 PM
The search key was not found in any record. (Error 3709) =?Utf-8?B?ZmlzaHk=?= Microsoft Access 6 22nd Sep 2007 07:21 AM
Replica fails to synchronize, Search key not found, 3709 =?Utf-8?B?SmltRWFnbGVPbmU=?= Microsoft Access 3 25th Jul 2006 05:35 PM
The search key was not found in any record. (Error 3709) Ed Microsoft Access Database Table Design 1 3rd Feb 2005 03:19 PM
HELP! error 3709 search key not found Sue Microsoft Access Forms 13 5th Jan 2005 07:17 PM


Features
 

Advertising
 

Newsgroups
 


All times are GMT +1. The time now is 02:39 AM.