I have an application
that uses web synchronization
and performs merge
replication programmatically using RMO. A number of the tables in the publication use
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
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)?
View Complete Post