Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / General 2 / January 2008

Tip: Looking for answers? Try searching our database.

Problem replicated db

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
John - 17 Jan 2008 17:49 GMT
Hi

There seems to be some problem between the replica master and its replicated
copies. What is the method to set the db back to normal and re-replicate?

Thanks

Regards
user@domain.invalid - 17 Jan 2008 18:32 GMT
> Hi
>
[quoted text clipped - 4 lines]
>
> Regards

What kind of problem?

doing what you ask is not a trivial thing to do.

If the replicated copies do not have any changes that are not on the
master, you could delete the replicas and recreate them.

Bob
John - 17 Jan 2008 19:18 GMT
Hi

The problem is that when I open the replica db I get the message "This
member of the replica set has conflicts from synchronizing changes with
other members. Do you want to resolve the conflicts now?" selecting Yes does
nothing i.e. it does not bring up the conflict resolution dialog. Selecting
Tools->Replication->Resolve Conflicts menu also does not do anything. Which
means the conflict remains and gives message every time db is opened. I have
tried doing a detect and repair on Access 2000 but no luck. Any ideas?

Thanks

Regards

>> Hi
>>
[quoted text clipped - 14 lines]
>
> Bob
user@domain.invalid - 17 Jan 2008 19:53 GMT
> Hi
>
[quoted text clipped - 28 lines]
>>
>> Bob

Try to manually sync with each member of the replica set.

You could also Google search for cannot open resolve conflict menu

Bob
John - 17 Jan 2008 19:59 GMT
How do you manually sync? I tried Tools->Replication->Resolve Conflicts
menu, is there another way?

Regards

>> Hi
>>
[quoted text clipped - 36 lines]
>
> Bob
user@domain.invalid - 17 Jan 2008 23:15 GMT
YOu do this by Tools - replication - Synchronize now

Bob

> How do you manually sync? I tried Tools->Replication->Resolve Conflicts
> menu, is there another way?
[quoted text clipped - 41 lines]
>>
>> Bob
John - 17 Jan 2008 20:03 GMT
Google search for cannot open resolve conflict menu brings nothing at least
on first few pages

>> Hi
>>
[quoted text clipped - 36 lines]
>
> Bob
user@domain.invalid - 17 Jan 2008 23:22 GMT
> Google search for cannot open resolve conflict menu brings nothing at least
> on first few pages
[quoted text clipped - 39 lines]
>>
>> Bob

Why not try to respove conflicts in one of the replicas.  Perhaps also
try on another PC.

Bob
David W. Fenton - 20 Jan 2008 22:43 GMT
> The problem is that when I open the replica db I get the message
> "This member of the replica set has conflicts from synchronizing
[quoted text clipped - 4 lines]
> remains and gives message every time db is opened. I have tried
> doing a detect and repair on Access 2000 but no luck. Any ideas?

Make sure you've got hidden objects and system objects displayed
(Tools | Options), and then check the MSysConflicts table. If it has
no records in it, then you don't actually have any conflicts. If it
*does* have conflicts, you'll need to decipher it by looking up the
GUIDs of the tables involved. You should also check to see if there
are conflict tables for any of your user tables. If you have a table
called tblPerson and there's a conflict, there will be a table
called tblPerson_Conflicts. That will have the data for the *losing*
record in the conflict. If the winning record is OK, then you can
just delete that table (or check all the records there before
deleting it).

Remember, the conflict resolver does nothing but offer an
opportunity to check that Jet resolved the conflicts correctly --
the conflicts have already been resolved. So, if worst comes to
worst, you can just delete the conflict tables and be done with it.

You should also try looking at other replicas, which may allow you
to resolve the conflicts.

Another thing you might try is to open the conflict resolver
directly and then open the replica you want to look at. The default
location for the conflict resolver is:

C:\Program Files\Common Files\Microsoft Shared\Database Replication

and the conflict resolver is called WZCNFLCT.EXE.

If you run it, you'll get the opportunity to point it at a
particular MDB.

Report back to us on what you find and then we can go from there.

Signature

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

 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.