thread of this discussion. Specifically, even though the wzcnf.dll file can
buttons are supposed to be used for). Also, when using the conflict viewer,
"Hilary Cotter" <hilaryk@att.net> wrote in message
news:ehxRBRxeEHA.2908@TK2MSFTNGP10.phx.gbl...
> strange - i have a value of 0 for this key. Your value is 1, and it is
> working now?
>
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
>
http://www.nwsu.com/0974973602.html >
>
> "Jim~C" <jdchanATnovusint.com> wrote in message
> news:%239hDacweEHA.4068@TK2MSFTNGP11.phx.gbl...
> > Hilary,
> >
> > The key you mention looks like this:
> >
> > ebizdb:NWRepl:NWRepl:stltough01:Northwind
> >
> > Which looks ok to me. There's a subkey (among others) with the name
> > UseInteractiveResolver, REG_DWORD, with a value of 1 (which I assume
> means
> > that interactive resolution is enabled). And, indeed the interactive
> > resolver starts now,
> >
> > Cheers,
> > Jim
> >
> > "Hilary Cotter" <hilaryk@att.net> wrote in message
> > news:%23%23ft2jveEHA.3792@TK2MSFTNGP09.phx.gbl...
> > > looks good.
> > >
> > > I just want to clarify a few things. The way the interactive resolver
is
> > > supposed to work is you get some conflict while using WSM.
> > >
> > > A dialog is generated telling you there was a conflict and to contact
> your
> > > sysadmin.
> > >
> > > You click on OK (there is no other option) and then it goes away
> > >
> > > Can you look in this registry key and post back what you see?
> > >
> > > HKLM\Software\Microsoft\Microsoft SQL
> Server\80\Replication\Subscriptions\
> > >
> > > I am looking for the name of your publication and making sure it looks
> > > something like this:
> > >
> > >
> >
>
Publisher:PublicationDatabase:Publication:Subscriber:SubscriptionDatabase\Us
> > > eInteractiveResolver
> > >
> > > --
> > > Hilary Cotter
> > > Looking for a book on SQL Server replication?
> > >
http://www.nwsu.com/0974973602.html > > >
> > >
> > > "Jim~C" <jdchanATnovusint.com> wrote in message
> > > news:e1rGKJveEHA.2044@TK2MSFTNGP10.phx.gbl...
> > > > Hilary,
> > > >
> > > > Following are the results of executing sp_enumcustomresolvers:
> > > >
> > > > -----------------------
> > > > Microsoft SQLServer Stored Procedure Resolver
> > > > {08B0B2D6-3FB3-11D3-A4DE-00C04F610189}
> > > > Microsoft SQL Server Additive Conflict Resolver
> > > > {08B0B2DB-3FB3-11D3-A4DE-00C04F610189}
> > > > Microsoft SQL Server Averaging Conflict Resolver
> > > > {08B0B2DC-3FB3-11D3-A4DE-00C04F610189}
> > > > Microsoft SQL Server Maximum Conflict Resolver
> > > > {08B0B2DE-3FB3-11D3-A4DE-00C04F610189}
> > > > Microsoft SQL Server DATETIME (Later Wins) Conflict Resolver
> > > > {08B0B2DE-3FB3-11D3-A4DE-00C04F610189}
> > > > Microsoft SQL Server Priority Column Resolver
> > > > {08B0B2DE-3FB3-11D3-A4DE-00C04F610189}
> > > > Microsoft SQL Server Minimum Conflict Resolver
> > > > {08B0B2DF-3FB3-11D3-A4DE-00C04F610189}
> > > > Microsoft SQL Server DATETIME (Earlier Wins) Conflict Resolver
> > > > {08B0B2DF-3FB3-11D3-A4DE-00C04F610189}
> > > > Microsoft SQL Server Subscriber Always Wins Conflict Resolver
> > > > {08B0B2E0-3FB3-11D3-A4DE-00C04F610189}
> > > > Microsoft SQL Server Merge Text Columns Conflict Resolver
> > > > {08B0B2E1-3FB3-11D3-A4DE-00C04F610189}
> > > > Microsoft SQL Server Download Only Conflict Resolver
> > > > {08B0B2DD-3FB3-11D3-A4DE-00C04F610189}
> > > > Microsoft SQL Server Upload Only Conflict Resolver
> > > > {08B0B2E2-3FB3-11D3-A4DE-00C04F610189}
> > > > -----------------------
> > > >
> > > > By the way, I did not specify a particular resolver when I created
the
> > > > publication, so it should be using the default.
> > > >
> > > > Thanks for your assistance!
> > > > Jim
> > > >
> > > > "Hilary Cotter" <hilaryk@att.net> wrote in message
> > > > news:uU%23SwlueEHA.636@TK2MSFTNGP12.phx.gbl...
> > > > > the interactive resolver component is a com component which you or
> > > another
> > > > > developer has written to handle conflicts.
> > > > >
> > > > > Can you run this proc in the master database on your publisher and
> > tell
> > > me
> > > > > what it returns?
> > > > >
> > > > > sp_enumcustomresolvers
> > > > >
> > > > > --
> > > > > Hilary Cotter
> > > > > Looking for a book on SQL Server replication?
> > > > >
http://www.nwsu.com/0974973602.html > > > > >
> > > > >
> > > > > "Jim~C" <jdchanATnovusint.com> wrote in message
> > > > > news:esE8CmmeEHA.644@tk2msftngp13.phx.gbl...
> > > > > > I've got a clean install (in the following order) on a brand new
> > > Tablet
> > > > > PC:
> > > > > >
> > > > > > 1) Windows XP Pro SP1 + latest security patches (Version 5.1 -
> Build
> > > > > > 2600.xpsp2.030422-1633: Service Pack 1)
> > > > > > 2) Office XP with SP3 (all components, including Access)
> > > > > > 3) MSDE 2000 SP3a (clean install from latest kit)
> > > > > >
> > > > > > The MSDE is setup as a default instance with integrated security
> > (i.e.
> > > > > > installed using SETUP SAPWD="xxxx").
> > > > > >
> > > > > > On our network, we have SQL Server 2000 Enterprise SP3. I setup
a
> > test
> > > > > > publication of the Northwind database on this server using merge
> > > > > replication
> > > > > > supporting pull subscriptions and allowing interactive conflict
> > > > > resolution.
> > > > > >
> > > > > > I then setup a pull subscription on the Tablet PC using the
> Windows
> > > Sync
> > > > > > manager. The subscription shows up in the list and I can
> synchronize
> > > > with
> > > > > > the publisher successfully.
> > > > > >
> > > > > > I also setup the option to allow interactive conflict
resolution.
> > > > However,
> > > > > > when I changed some data on the subscriber and publisher to
> > instigate
> > > a
> > > > > > conflict, I get the following error when I synchronize:
> > > > > >
> > > > > > "The process failed to get information about the Interactive
> > Resolver
> > > > > > Component from the registry."
> > > > > >
> > > > > > Some detailed information from the Replication Monitor on the
> > > publisher
> > > > > > looks like this:
> > > > > >
> > > > > > "The process failed to get information about the Interactive
> > Resolver
> > > > > > Component from the registry.
> > > > > > (Source: Merge Process (Agent); Error number: -2147198712)"
> > > > > >
> > > > > > On the Tablet PC (the subscriber), I found the replication
> conflict
> > > > viewer
> > > > > > at c:\Program files\common files\microsoft shared\database