Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Sync Failed: The Search Key Cannot Be Found in Any Records

127 views
Skip to first unread message

mikej711

unread,
Mar 28, 2011, 4:10:38 PM3/28/11
to
This topic has been discussed at length previously. I wouldn’t even
bring it up except that I have new information that might help. My
copy is one of the last using direct synchronization of GLOBAL
replicas in 2002 file format (I know bad idea). Even worse, they
passed replicas around using Skype. The situation worked, or had
worked, since there was one replica in the field office.
That changed when the field updated to Access 2010. Now, they get the
error “Sync Failed: The Search Key Cannot Be Found in Any Records;
Unknown Reason (-1601)” HALF WAY through the sync. I have Access 2007
in my office. I went through and visually inspected the records. I
couldn’t find any corruption.
All this has been described in other posts but here’s something new: I
also have Access 2002 in my office. I can open the main office’s
backend in 2002, but when I try to open the field office, I receive
the following error:

Microsoft Access cannot open this file.

This file is located outside your intranet or on an
untrusted site. Microsoft Access will not open the file
due to potential security problems.

To open the file, copy it to your machine or an
accessible network location.

Do these two errors make sense together?

David-W-Fenton

unread,
Mar 30, 2011, 11:42:50 AM3/30/11
to
mikej711 <mike...@charter.net> wrote in
news:cb3a5dac-a444-4c2b...@o21g2000prh.googlegroups.co
m:

> This topic has been discussed at length previously. I wouldn’t
> even bring it up except that I have new information that might
> help. My copy is one of the last using direct synchronization of
> GLOBAL replicas in 2002 file format (I know bad idea).

What's a bad idea?

> Even worse, they
> passed replicas around using Skype.

That's unquestionably a bad idea, though.

> The situation worked, or had
> worked, since there was one replica in the field office.
> That changed when the field updated to Access 2010. Now, they get
> the error “Sync Failed: The Search Key Cannot Be Found in Any
> Records; Unknown Reason (-1601)” HALF WAY through the sync.

I don't know for sure, but it may be that you'll have to rebuild the
replica set. Or clean up the dead replicas (which is likely
completely impossible, given the likely inaccessibility of the PCs
where the replicas have been opened).

> I have Access 2007
> in my office. I went through and visually inspected the records. I
> couldn’t find any corruption.

Even in a non-replicated context, the search key error generally
doesn't have any visible manifestation. One cause of it that the MS
documentation doesn't mention is a mismatched workgroup file.
Indeed, that's a very likely thing here, as A2010 is likely to use
its own new workgroup file, so it won't be the same as the one the
replica set was created with. You might try replacing the A2010
workgroup file with the one from A2002 (as default workgroup file)
and see if that makes a difference. Or you could just try a shortcut
opening with the A2002 workgroup to test it.

> All this has been described in other posts but here’s something
> new: I also have Access 2002 in my office. I can open the main
> office’s backend in 2002, but when I try to open the field office,
> I receive the following error:
>
> Microsoft Access cannot open this file.
>
> This file is located outside your intranet or on an
> untrusted site. Microsoft Access will not open the file
> due to potential security problems.
>
> To open the file, copy it to your machine or an
> accessible network location.
>
> Do these two errors make sense together?

These errors don't have anything to do with replication. They are
A2002's "security" prompts, I think. It might be that they have
something to do with the changes made to a file in A2007 and A2010.

--
David W. Fenton http://www.dfenton.com/
contact via website only http://www.dfenton.com/DFA/

mikej711

unread,
Apr 2, 2011, 3:37:27 PM4/2/11
to
I think you're right about the workgroup being at fault.
Unfortunately, I don't know how to decrypt a replica set to assign a
new workgroup. Microsoft’s Knowledge Base has an article on decrypting
a single database but I’m afraid that if I give the Users group Full
Permissions and import the tables to an empty database, as the article
suggests, I’ll lose the sync data. Besides, wouldn’t the Design Master
have to sync with the replica in order for that to work, something I
cannot do?

On Mar 30, 10:42 am, "David-W-Fenton" <NoEm...@SeeSignature.invalid>
wrote:

David-W-Fenton

unread,
Apr 3, 2011, 11:45:37 AM4/3/11
to
mikej711 <mike...@charter.net> wrote in
news:fe75dc20-262d-4d03...@r13g2000yqk.googlegroups.co
m:

> I think you're right about the workgroup being at fault.
> Unfortunately, I don't know how to decrypt a replica set to assign
> a new workgroup. Microsoft's Knowledge Base has an article on
> decrypting a single database but I'm afraid that if I give the
> Users group Full Permissions and import the tables to an empty
> database, as the article suggests, I'll lose the sync data.
> Besides, wouldn't the Design Master have to sync with the replica
> in order for that to work, something I cannot do?

You need to find the original workgroup file or recreate it, which
is completely possible if you know the usernames, any custom user
groups and the PID of each. If you don't have that information, you
have a real problem. But if you have the correct workgroup file (or
can recreate it), you can just run with it and should be able to
function just fine.

BTW, you don't actually have to have any objects secured or any
non-default permissions set for this to be a problem. I encountered
this cause of the "search key not found" error message in exactly
that context, with a workgroup file that was somehow different, but
had no security settings in it all (just some custom users).

0 new messages