.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
Post New Web Links

Subscriber always wins conflict resolver - verify the component is registered

Posted By:      Posted Date: September 28, 2010    Points: 0   Category :Sql Server

I have started getting an issue in replication where replication fails with the process could not initialise the subscriber always wins conflict resolver. Please verify the component is registered. I can not locate the cause of this error.


I have even uninstalled all my SQL Servers and done a new install of SQL 2008 R2 x64


Windows 2008 R2 x64 with SQL 2008 R2 x64

Any help would be appreciated.

View Complete Post

More Related Resource Links

Could not determine the threading model of the Custom Resolver Component from the registry.

I have an application that uses web synchronization and performs merge replication programmatically using RMO. A number of the tables in the publication use a COM-based custom conflict resolver that I have written in c#. I have an installation package that creates a virtual directory containing the replication listener (replisapi.dll) and installs the conflict resolver. This week the package was deployed on a 64-bit Small Business Server (SBS) 2008. The first subscriber was able to synchronize successfully but subsequent syncs and syncs by other subscribers resulted in the following exception: Could not determine the threading model of the Customer Resolver Component from the registry. In the registry on the server the ThreadingModel value of my conflict resolver was set to Both and I was able to resolve the issue by changing the value to Free. My first question is why when using the Both model would the resolver not simply be loaded in the same apartment as the merge agent? My second question is whether I have plumbed for the correct alternative of Free (rather than Neutral or not specifying a model)?

Custom Conflict Resolver in Merge Replication



I am a newbie and now setting up Merge Replication on SQL Server 2005 as below.

Step1   Publisher1 > Node1 > Publisher1

In the morning,   Node1 will sync with Publisher1, update data and sync back to Publisher1.

Publisher1 and Publisher2 are quite similar (some articles are the same)

Step2   Publisher2 > Node2 > Publisher2

Here I want to write a custom code for conflict resolver where Node2 will always be a winner whenever the conflict occurs. If there is no conflict, data will be sync.

I tried to use a Conflict resolver comes along in SQL Server 2005, but it also affect not only in the conflicting situation but also in normal merging without conflicts.

thank you


Example of Stored proc conflict resolver?



Hi all,

I need to write a custom conflict resolver for an application using merge replication.  It's relatively simple logic  - compare the two rows from the publisher and the subscriber and the winner is based on the value of one particular column.

Reading BOL gives me the input parameter list for the sp, and specifies that the output should be exactly the winning row. What is doesn't give is any example of how to do this, in particular how to access the two rows in conflict so that they can be compared.

I can do this by dynamically building SELECT statements, one connecting to the table locally on the publisher and another connecting to the subscriber using the form SERVER.DATABASE.OWNER.TABLE, but this requires me to explicitly have the subscriber as a linked server to do this.  An example of my revolting code is appended to this post.

Is this what I have to do, or is there some table I can access on the publisher that has the conflicting rows in so I can compare them without going back to the subscriber?

Thanks for your help



---- code sample --

ALTER PROCEDURE [dbo].[prRep_ResolveInventoryConflicts]

@tableowner sysname

stored procedure based custom conflict resolver truncates data


I created a stored procedure based custom conflict resolver in SQL 2005, I return the winning result set and also save that result set to a test table to compare the values.  The values saved to the test table are correct but some of the values saved as the conflict winter are truncated.


Example a char(3) filed is updated at the subscriber as '111' and updated at the publisher as '222', in my custom conflict resolver if I use the value from the subscriber the conflict resolver updates the field as  '11 ', if I use the publisher value the conflict resolver updates the field as '22 '.  Now the same records is saved to the test table correctly as either '111' or '222' depending on the logic I used.  So the result set has the correct values, its after the custom conflict resolver is called where the values is somehow truncated.  Has anybody run into this before and what steps can I take to avoid this.


Thank you,

Error Registering COM+ Component

Hi All,

I am experimenting with using EnterpriseServices. I created a component, created the SNK file, compiled the DLL. In the assemblyinfo.vb file, I added '<Assembly: AssemblyKeyFile("c:\key.snk")> '.
I created a new package in COM+, When I attempt to add the .dll to the package i get:

An error occured while processeing the last operation.
Error Code 80020009 - Exception ocurred.

The eventlog may contain additional troubleshooting information.

Here is the Event log:

Installation of 'TransactionalComponentsCore.dll' into '{6367F5F1-56A7-4223-97AC-51F7DC1D53EB}' failed with an exception:

System.EnterpriseServices.RegistrationException: Could not install type library 'TransactionalComponentsCore.tlb' into application 'TransactionalComponentsCore'.

Server stack trace:
at System.EnterpriseServices.RegistrationDriver.InstallTypeLibrary_W2K(ApplicationSpec spec)
at System.EnterpriseServices.RegistrationDriver.InstallTypeLibrary(ApplicationSpec spec)
at System.EnterpriseServices.RegistrationDriver.InstallAssembly(RegistrationConfig regConfig, Object obSync)
at System.EnterpriseServices.RegistrationHelperTx.InstallAssemblyFromConfig(RegistrationConfig& regConfig, Object sync)
at Sys

Windows with C++: Windows Imaging Component Basics


Windows Imaging Component (WIC) is an extensible framework for encoding, decoding, and manipulating images. See how to use WIC to encode and decode different image formats.

Kenny Kerr

MSDN Magazine April 2008

Toolbox: Code Generation, A Charting Component, and More


Developers have a number of tools at their disposal, but which of these components do you really need to complete your project? Each month we'll analyze the latest software and books to see if they merit inclusion in your toolbox.

Scott Mitchell

MSDN Magazine January 2006

Cryptography: Employ Strong Encryption in Your Apps with Our CryptoUtility Component


When storing sensitive data, you need to be able to identify threats, determine how these threats interact with each other, and how issues can combine to constitute a vulnerability that will leave your data exposed. With a good understanding of the various cryptographic algorithms, salt, hashes, ACLs, and other available techniques, you'll be in a better position to protect your critical data.

Michael Stuart and J Sawyer

MSDN Magazine November 2004

The XML Files: XSLT Keys, Select vs. Match, Conflict Resolution, and More


This month Aaron Skonnard covers how keys work in XSLT, XSLT match and select attributes, SelectNodes order, finding