Failed to find Search Key

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Chip Coutts - 23 Apr 2004 15:15 GMT

I have a replicated database, with a Design Master and
three Replicas, and I use Replication Manager to synch
them at night.

From time to time I make updates to the Design Master. For
the second time in a little over a week now, I have had a
synchronization failure with a particular Replica, we'll
call it Replica3. Both times, the error message
mentioned "failed as no search key was found". I have had
other failures with other Replicas in the past, but I have
only gotten this message with this Replica3. I tried to
synchronize manually, and got the same error, so I will be
creating a new Replica for them, and they will have to re-
enter the lost data.

Any thoughts?

Reply to this Message

Michael \(michka\) Kaplan [MS] - 23 Apr 2004 20:01 GMT

Is it partial? Is it local/anonymous?

Signature

MichKa [MS]
NLS Collation/Locale/Keyboard Development
Globalization Infrastructure and Font Technologies

This posting is provided "AS IS" with
no warranties, and confers no rights.

> I have a replicated database, with a Design Master and
> three Replicas, and I use Replication Manager to synch
[quoted text clipped - 12 lines]
>
> Any thoughts?

Reply to this Message

Chip Coutts - 07 May 2004 20:01 GMT

The Replica is a full global replica.

>-----Original Message-----
>Is it partial? Is it local/anonymous?
[quoted text clipped - 17 lines]
>
>.

Reply to this Message

Michael \(michka\) Kaplan [MS] - 18 May 2004 18:56 GMT

Hmmm.... it is harder to get this error (which simply means that a record
that the Jet reconciler expected to find in one of the replication system
tables could not, in fact, be found) in a full global replica. But it is
occasionally possible if the replica is either corrupt or past date.

Signature

MichKa [MS]
NLS Collation/Locale/Keyboard Development
Globalization Infrastructure and Font Technologies

This posting is provided "AS IS" with
no warranties, and confers no rights.

> The Replica is a full global replica.
>
[quoted text clipped - 27 lines]
> >
> >.

Reply to this Message

WullaertKarel - 23 May 2004 18:38 GMT

My method was very simple.
I had 2 replicas. One (I don't know which one) was corrupted so when
tried to synchronize, I got the message 'The search key was not foun
.'. I simply toke a new replica of each and then tried to synchroniz
the 2 new replica's which worked. But I have to admit that I won't kno
If I lost data and neighter which data but it worked.

Kare

-
WullaertKare

Reply to this Message

Michael \(michka\) Kaplan [MS] - 24 May 2004 16:31 GMT

If the creation worked then you have all the data... its a similar problem
to the "no common point..." error:

http://trigeminal.com/usenet/usenet021.asp

In both cases, the problem is an inbility of Jet to find replica metadata
that it thinks it needs, so its cool that same solution works....

Signature

MichKa [MS]
NLS Collation/Locale/Keyboard Development
Globalization Infrastructure and Font Technologies

This posting is provided "AS IS" with
no warranties, and confers no rights.

> My method was very simple.
> I had 2 replicas. One (I don't know which one) was corrupted so when I
[quoted text clipped - 11 lines]
> ------------------------------------------------------------------------
> View this thread: http://www.mcse.ms/message603967.html

Reply to this Message