FIX: w3wp.exe process crashes during merge replication with SQL Server Compact subscribers and precomputed partitions

Applies to: SQL Server 2008 R2 Service Pack 2SQL Server 2008 R2 DeveloperSQL Server 2008 R2 Enterprise


Assume that you use Microsoft SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, or SQL Server 2014. When you use merge replication with SQL Server Compact subscribers and precomputed partitions, the w3wp.exe process crashes during the synchronization of the subscribers, and then the synchronization fails. Additionally, the SQL Server Compact subscribers may report the following error:
ERR:Couldn't find existing RSCB xxx.


Service Pack information

To resolve this issue, apply Microsoft SQL Server 2008 SP4. For more information about how to obtain SQL Server 2008 SP4, click the following article number to view the article in the Microsoft Knowledge Base:
2979596 SQL Server 2008 Service Pack 4 release information

Hotfix for SQL Server 2008 SP3

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

The issue was first fixed in the following cumulative update of SQL Server.

Cumulative Update 2 for SQL Server 2012 SP2

Cumulative Update 12 for SQL Server 2012 SP1

Cumulative Update 3 for SQL Server 2014

Cumulative Update 13 for SQL Server 2008 R2 SP2


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.