Cannot find search key: error message of death?

Cannot find search key: error message of death?

Post by leickld » Fri, 17 Oct 2008 20:58:42

I've been reading all the posts on the "Cannot find search key" error
and getting pretty nervous that I'm screwed.

We've been replicating for years, and one day a user emailed me to
tell me her synch failed because she got the "Cannot find search key
error". Then one by one other users got the error message too. Now
no one can synch their data to the server and I have multiple data
sets floating around out there on laptops that I fear I'll never be
able to synchronize.

We are doing direct synchronizations over a VPN. I've read the
warnings about doing direct synchs over a VPN, but I thought it was at
least a step up from how we WERE doing it before (back and forth via
email). I've tried Trigeminal's TSI indirect synch method, but I
haven't gotten it to work yet (I know Access and Visual Basic pretty
well but I don't understand what JET is). I've been trying to get
that to work and figured the users would be safe for a few weeks until
I got it up and running....not the case I guess.

Right now, my main concern is getting this data to synch. I've tried
compacting and repairing. I've tried moving the user's data onto the
server itself and doing a local direct synch. Neither of these things
has worked. I know my methodology for VPN synchs needs to be fixed to
be indirect instead of direct, but my immediate need is to get
everyone's data synchronized. If I can do that, I can at least start
a new design master from scratch, give everyone new replicas, and then
make figuring out the TSI Indirect Synch process a top prioirty.

Does anyone have any suggestions for fixing this data???

Cannot find search key: error message of death?

Post by David W. F » Sun, 19 Oct 2008 00:40:30

leicklda < XXXX@XXXXX.COM > wrote in



Jet is the database engine that is the default for Access. When you
are using replication in Access, you're using a feature provided by
the Jet database engine. I'm not sure why this should be a stumbling
block for you (I think you've misidentified the are of your lack of
knowledge that's holding you back). That said, indirect replication
is quite tricky to set up without replication manager.


I don't know for certain, but it seems to me that if none of your
replicas can synch with each other, you're completely stuck with
gathering all the replicas, manually synching the data and then
re-initializing your replica set (i.e., create a completely new

Before embarking on that, I'd suggest trying one thing, and that's
to see if you can create a new replica from one of the problem
replicas and synch between those two replicas. Another thing to do
is to try moving an existing replica to a new location and opening
it there to see if that "wakes it up." I've seen that work (because
it's now got a different replica ID) for certain kinds of situations
where synchs had stopped working, but I can't guarantee that it will
work here -- it's just worth a shot.

Last of all, perhaps this was caused by the fact that you were
direct synching across a VPN, which you admit is something you're
not supposed to do. I would strongly suggest that you get your
indirect synch infrastructure up and running before you start your
new replica set. Otherwise, you could end up right back where you
started, with a broken replica set.

David W. Fenton
usenet at dfenton dot com


Cannot find search key: error message of death?

Post by Chris flle » Sat, 29 Nov 2008 03:55:16

Hello Christopher

I have finally competed all the access profiles for today by organsing all
the business files organazations and I have competed and recivied to you all
my third last tasks on access for today.

Anyway thanks