Previous Thread

8/14/2006 12:41:02 PM    MDB crashed when sychronising
Hi, 
 
I had a corrupt record in one of my replica sets which I have removed by 
 
creating a new replica from the desing master and using append an append 
 
query to update all the amended records which would normally be done via 
 
synchronising. 
 
The design master did attempt to synchronise prior to me doing this and now 
 
when I try to synchronise with another replica it gets about 90% of the way 
 
through and crashes. 
 
Now as I am doing this over a VPN network I thought I'd test to see whether 
 
this was causing a problem (never has before). I made copies of each backend 
 
to my machine and attempted to sync again at which point I received the 
 
message "The search key was not found in any record". 
 
I was kinda hoping to not retrieve all the updated data the hard way, any 
 
suggestions would be appreceiated. 
 
Thx in advance 
 
Charlie



8/14/2006 4:20:36 PM    Re: MDB crashed when sychronising
Charlie <Charlie@discussions.microsoft.com> wrote in 
 
news:D5EA1970-5F87-4310-99DF-97E922FA946C@microsoft.com: 
 
What do you mean by a "corrupt record?" 
 
Is it possible you've got PK collisions? 
 
Have you gone through the troubleshooting on this in the MS 
 
Knowledge Base? 
 
I have never seen the search key problem as anything other than the 
 
result of using an incorrect workgroup file. But others have seen it 
 
for other reason (memo field issues). Check Tony Toews corruption 
 
FAQ to see what it says: 
 
http://www.granite.ab.ca/access/corruptmdbs.htm 
 
-- 
 
David W. Fenton                  http://www.dfenton.com/ 
 
usenet at dfenton dot com    http://www.dfenton.com/DFA/

8/15/2006 3:41:44 PM    Re: MDB crashed when sychronising
Charlie <Charlie@discussions.microsoft.com> wrote in 
 
news:57CF2B92-8DAC-4234-A433-55064EDA3EF0@microsoft.com: 
 
How so? What problems did it cause beyond that? 
 
In any event, that could indicate a number of problems, but it 
 
definitely means your database is corrupted at some level. 
 
Well, if the primary key values you are appending already exist in 
 
the table, there would be primary key collisions. 
 
I don't think your problems have anything at all to do with 
 
replication -- they are generic Jet corruption issues. 
 
I don't know. Do you still have a copy of the replica before you 
 
attempted to fix it? If so, I'd suggest manually copying the records 
 
before the #error record and pasting them somewhere, and then 
 
copying the records *after* the #error record and pasting them to 
 
the same destination. This will allow you to retain all the 
 
non-corrupt data. 
 
On the other hand, if the corrupted record has no viewable data in 
 
it for you to recover, just delete it. 
 
Last of all, if all else fails, you can contact Peter Miller at 
 
PKSolutions.com and see if he can help you. If he can't, you won't 
 
be charged for it. 
 
-- 
 
David W. Fenton                  http://www.dfenton.com/ 
 
usenet at dfenton dot com    http://www.dfenton.com/DFA/