Select the product you need help with

FIX: "Not registered correctly" error when you use a pull subscription and the Replication Interactive Conflict Resolver

Article ID: 2618680 - View products that this article applies to.

Microsoft distributes Microsoft SQL Server 2008 SP2 or Microsoft SQL Server 2008 R2 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security updates that were included with the previous SQL Server 2008 SP2 or SQL Server 2008 R2 update release.

Back to the top | Give Feedback

SYMPTOMS

Consider the following scenario:

You set up the following merge replication environment:
- The publisher or the distributor uses Microsoft SQL Server 2008 or Microsoft SQL Server 2008 R2.
- The subscriber uses Microsoft SQL Server 2005.
You configure the subscription to be a pull subscription.
You enable the use partition groups option on the article of the publication. For example, you use filters on the article.
You use the Microsoft Replication Interactive Conflict Resolver for merge replication. For example, you use Microsoft SQL Server Subscriber Always Wins Conflict Resolver.
You try to run the replication.

In this scenario, the replication fails, and you receive an error message that resembles the following:

<Conflict resolver name> is not registered correctly

Back to the top | Give Feedback

CAUSE

This issue occurs because the publisher or the distributor returns an incorrect COM CLSID key to the subscriber.

Back to the top | Give Feedback

RESOLUTION

Cumulative update information

SQL Server 2008 Service Pack 3

The fix for this issue was first released in Cumulative Update 3 for SQL Server 2008 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:

2648098

(http://support.microsoft.com/kb/2648098/LN/ )

Cumulative update package 3 for SQL Server 2008 Service Pack 3

Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

2629969

(http://support.microsoft.com/kb/2629969/LN/ )

The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 3 was released

Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 3 hotfix to an installation of SQL Server 2008 Service Pack 3. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

SQL Server 2008 R2

The fix for this issue was first released in Cumulative Update 11. For more information about how to obtain this cumulative update package for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:

2633145

(http://support.microsoft.com/kb/2633145/ )

Cumulative Update package 11 for SQL Server 2008 R2

Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

981356

(http://support.microsoft.com/kb/981356/ )

The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released

SQL Server 2008 R2 Service Pack 1

The fix for this issue was first released in Cumulative Update 4 for SQL Server 2008 R2 Service Pack 1. For more information about how to obtain this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:

2633146

(http://support.microsoft.com/kb/2633146/ )

Cumulative Update package 4 for SQL Server 2008 R2 Service Pack 1

2567616

(http://support.microsoft.com/kb/2567616/ )

The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was released

SQL Server 2008 Service Pack 2

The fix for this issue was first released in cumulative update package 7 for SQL Server 2008 Service Pack 2. For more information about how to obtain this cumulative update package for SQL Server 2008 Service Pack 2 (SP2), click the following article number to view the article in the Microsoft Knowledge Base:

2617148

(http://support.microsoft.com/kb/2617148/ )

Cumulative update package 7 for SQL Server 2008 Service Pack 2

Note Because the builds are cumulative, each new update release contains all the hotfixes and all the security updates that were included with the previous SQL Server 2008 SP2 update release. We recommend that you consider applying the most recent update release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

2402659

(http://support.microsoft.com/kb/2402659/ )

The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 2 was released

Back to the top | Give Feedback