Hello,
When conflicts arise, we can use the conflict viewer. We have checked the
box that says to log them for future use. Help says they go to the system
tables.
I am trying to find conflict information from several replications ago, but
can't find them. Is there a certain system table they go to?
Thanks,
Steve
Steve,
the tables that maintain conflict information are:
conflict_<PublicationName>_<ArticleName>_usertable name and
MSmerge_delete_conflicts.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Showing posts with label viewer. Show all posts
Showing posts with label viewer. Show all posts
Friday, 24 February 2012
Conflict Viewer included with MSDE 2000 Release A?
It seems that installing MSDE 2000 Release A does not install the conflict viewer, and therefore if a subscription is set to allow interactive conflict resolution at the client, it will not work...
Does anyone have the definitive answers to the following?
- Is Conflict Viewer supposed to be included with MSDE 2000 Rel A?
- Was it included in versions of MSDE prior to Rel A (my research has indicated that it was)?
- Is Conflict Viewer redistributable (hopefully there's a merge module somewhere?!)
- Does any other MS product apart from SQL Server install the Conflict Viewer (we have observed that certain machines that don't have SQL Server installed still have the conflict viewer...)?
Just for more information, our scenario is as follows:
- SQL Server 2000 database server, set with a publication allowing anonymous pull subscriptions, and articles set up to allow interactive conflict resolution.
- MSDE 2000 Rel A clients, with anonymous pull subscriptions to the server. When an on-demand synchronisation is attempted, we get the following message - "the process failed to
get information about the interactive resolver component from the
registry".
- If the files under Program Files\Common Files\Microsoft Shared\Database Replication are manually copied across and registered, it all works.
There's other posts asking similar questions in the replication discussion group, from Tanya Milanova and markeboy, but the answers given don't answer the question about redistribution of the component...
Cheers, Jim
Conflict Viewer as well as all the other tools for setting up and
maintaining replication on SQL Server 2000 are part of Enterprise Manager
and are not (and never have been) part of the MSDE distribution. The SQL
Server 2000 client tools (EM) cannot be legally redistributed.
Jim
"Jim Kirton" <JimKirton@.discussions.microsoft.com> wrote in message
news:EC5C41EB-AACB-4642-B57B-81C343DC8DE5@.microsoft.com...
> It seems that installing MSDE 2000 Release A does not install the conflict
viewer, and therefore if a subscription is set to allow interactive conflict
resolution at the client, it will not work...
> Does anyone have the definitive answers to the following?
> - Is Conflict Viewer supposed to be included with MSDE 2000 Rel A?
> - Was it included in versions of MSDE prior to Rel A (my research has
indicated that it was)?
> - Is Conflict Viewer redistributable (hopefully there's a merge module
somewhere?!)
> - Does any other MS product apart from SQL Server install the Conflict
Viewer (we have observed that certain machines that don't have SQL Server
installed still have the conflict viewer...)?
> Just for more information, our scenario is as follows:
> - SQL Server 2000 database server, set with a publication allowing
anonymous pull subscriptions, and articles set up to allow interactive
conflict resolution.
> - MSDE 2000 Rel A clients, with anonymous pull subscriptions to the
server. When an on-demand synchronisation is attempted, we get the following
message - "the process failed to
> get information about the interactive resolver component from the
> registry".
> - If the files under Program Files\Common Files\Microsoft Shared\Database
Replication are manually copied across and registered, it all works.
> There's other posts asking similar questions in the replication discussion
group, from Tanya Milanova and markeboy, but the answers given don't answer
the question about redistribution of the component...
> Cheers, Jim
Does anyone have the definitive answers to the following?
- Is Conflict Viewer supposed to be included with MSDE 2000 Rel A?
- Was it included in versions of MSDE prior to Rel A (my research has indicated that it was)?
- Is Conflict Viewer redistributable (hopefully there's a merge module somewhere?!)
- Does any other MS product apart from SQL Server install the Conflict Viewer (we have observed that certain machines that don't have SQL Server installed still have the conflict viewer...)?
Just for more information, our scenario is as follows:
- SQL Server 2000 database server, set with a publication allowing anonymous pull subscriptions, and articles set up to allow interactive conflict resolution.
- MSDE 2000 Rel A clients, with anonymous pull subscriptions to the server. When an on-demand synchronisation is attempted, we get the following message - "the process failed to
get information about the interactive resolver component from the
registry".
- If the files under Program Files\Common Files\Microsoft Shared\Database Replication are manually copied across and registered, it all works.
There's other posts asking similar questions in the replication discussion group, from Tanya Milanova and markeboy, but the answers given don't answer the question about redistribution of the component...
Cheers, Jim
Conflict Viewer as well as all the other tools for setting up and
maintaining replication on SQL Server 2000 are part of Enterprise Manager
and are not (and never have been) part of the MSDE distribution. The SQL
Server 2000 client tools (EM) cannot be legally redistributed.
Jim
"Jim Kirton" <JimKirton@.discussions.microsoft.com> wrote in message
news:EC5C41EB-AACB-4642-B57B-81C343DC8DE5@.microsoft.com...
> It seems that installing MSDE 2000 Release A does not install the conflict
viewer, and therefore if a subscription is set to allow interactive conflict
resolution at the client, it will not work...
> Does anyone have the definitive answers to the following?
> - Is Conflict Viewer supposed to be included with MSDE 2000 Rel A?
> - Was it included in versions of MSDE prior to Rel A (my research has
indicated that it was)?
> - Is Conflict Viewer redistributable (hopefully there's a merge module
somewhere?!)
> - Does any other MS product apart from SQL Server install the Conflict
Viewer (we have observed that certain machines that don't have SQL Server
installed still have the conflict viewer...)?
> Just for more information, our scenario is as follows:
> - SQL Server 2000 database server, set with a publication allowing
anonymous pull subscriptions, and articles set up to allow interactive
conflict resolution.
> - MSDE 2000 Rel A clients, with anonymous pull subscriptions to the
server. When an on-demand synchronisation is attempted, we get the following
message - "the process failed to
> get information about the interactive resolver component from the
> registry".
> - If the files under Program Files\Common Files\Microsoft Shared\Database
Replication are manually copied across and registered, it all works.
> There's other posts asking similar questions in the replication discussion
group, from Tanya Milanova and markeboy, but the answers given don't answer
the question about redistribution of the component...
> Cheers, Jim
Conflict Viewer hangs
Hello, All!
MS SQL 2k EE SP3a, merge replication.
After long time Conflict Viewer began to hang when viewing conflicts on some
articles (not on all). There is no waiting locks. Workload is minimal.
What's wrong?
Thanx in advance.
I've run it under debugger and found that it runs an infinite loop in the
sqloledb.dll
No commands sent to server.
Guys from MS - whats wrong?
"Ray D" wrote:
> Hello, All!
> MS SQL 2k EE SP3a, merge replication.
> After long time Conflict Viewer began to hang when viewing conflicts on some
> articles (not on all). There is no waiting locks. Workload is minimal.
> What's wrong?
> Thanx in advance.
MS SQL 2k EE SP3a, merge replication.
After long time Conflict Viewer began to hang when viewing conflicts on some
articles (not on all). There is no waiting locks. Workload is minimal.
What's wrong?
Thanx in advance.
I've run it under debugger and found that it runs an infinite loop in the
sqloledb.dll
No commands sent to server.
Guys from MS - whats wrong?
"Ray D" wrote:
> Hello, All!
> MS SQL 2k EE SP3a, merge replication.
> After long time Conflict Viewer began to hang when viewing conflicts on some
> articles (not on all). There is no waiting locks. Workload is minimal.
> What's wrong?
> Thanx in advance.
Conflict Viewer error:
Un unexpected error occurred while trying to launch the Conflict Viewer.
Nothing more and of course, no conflict viewer...
Any idea how to fix this?
Michael
I am having the same issue. Anybody aware of this.
thanks
"AlohaMike" wrote:
> Un unexpected error occurred while trying to launch the Conflict Viewer.
> Nothing more and of course, no conflict viewer...
> Any idea how to fix this?
> Michael
Nothing more and of course, no conflict viewer...
Any idea how to fix this?
Michael
I am having the same issue. Anybody aware of this.
thanks
"AlohaMike" wrote:
> Un unexpected error occurred while trying to launch the Conflict Viewer.
> Nothing more and of course, no conflict viewer...
> Any idea how to fix this?
> Michael
Subscribe to:
Posts (Atom)