Group:  Microsoft Access ยป microsoft.public.access.replication
Thread: Partner replica is exclusively locked cannot apply changes

DotNetBag
.NET Development Newsgroups

HTVi
TV Discussion Newsgroups

Our Hot Pick: Rising Antivirus 2006 - Certified by TUV & Checkmark! Get 10% discount by entering this coupon code: ONDISCOUNT10
Rising Antivirus 2006

Partner replica is exclusively locked cannot apply changes
Donald Prebus 02.08.2006 04:06:01
This is an error message I get terminating the internet replication exchange.
I can see the lock file open in the folder and I am prevented from deleting
it if I try. I have set Access to open the database in shared mode as opposed
to exclusive mode. What can be wrong. I used to successfully sychronize this
same backend replicated database over the internet in the past. And the
exchange starts - but won't complete. Help.
Re: Partner replica is exclusively locked cannot apply changes
"David W. Fenton" <XXXusenet[ at ]dfenton.com.invalid> 02.08.2006 18:34:43
Donald Prebus <DonaldPrebus[ at ]discussions.microsoft.com> wrote in
news:2C1BE7A8-C746-4A5A-A1B5-8DFF69AC61A0[ at ]microsoft.com:

[Quoted Text]
> This is an error message I get terminating the internet
> replication exchange. I can see the lock file open in the folder
> and I am prevented from deleting it if I try. I have set Access to
> open the database in shared mode as opposed to exclusive mode.
> What can be wrong. I used to successfully sychronize this same
> backend replicated database over the internet in the past. And the
> exchange starts - but won't complete. Help.

Are you using a production replica for one end of the Internet
synchronization? I'd recommend against that. Remember that this can
cause these problems:

1. if a user has a table open that has a design change, the synch
will fail.

2. if you are editing memo fields in bound forms, a synch during an
edit of a memo can corrupt the memo pointer and lead to loss of the
whole record with the corrupted memo pointer.

Now, obviously, the synchs have to happen at one point, but I think
it's better to separate the production replica from the
synchronization replica. That means, at least, that the remote
synchs, which are very fragile, will not be subject to problems
caused by the production replica. Yes, of course, a scheduled synch
between the synchronization replica and the production replica would
experience the same problems, but it won't prevent the synch with
the remote location from completing successfully.

It's possible that one of your users has gotten an exclusive lock on
the replica that is locked.

Also, be sure you are using a split architecture with the
forms/reports/etc. in one MDB and the data tables in another MDB.
Only the tables MDB should be replicated.

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

Home | Search | Terms | Imprint | Contact
Newsgroups Reader - provided by WiredBox.Net