You are currently offline, waiting for your internet to reconnect

FIX: W3WP.exe process stops unexpectedly when multiple merge replication subscribers synchronize at the same time in SQL Server 2008 R2 or SQL Server 2012

Statement of support

There is an issue with the original Microsoft SQL Server 2008 R2 hotfix package that was associated with this KB. Therefore it has been replaced with a new updated package whose version is 10.50.4285.0 that the current link of this KB refers to. The package includes all the fixes documented in this article, Customers that installed the original hotfix package (build 10.50.4280.0) should upgrade to the new package as soon as possible. 
Symptoms
When multiple merge replication subscribers try to synchronize at the same time by using Web synchronization in SQL Server 2008 R2 or Microsoft SQL Server 2012, the W3wp.exe process stops unexpectedly. Additionally, the following event is logged in the Application log:

Event Source: Application Event ID: 1000 Description: Faulting application name: w3wp.exe, version: 7.5.7601.17514, Faulting module name: xmlsub.dll, version: 2009.100.4270.0, Fault offset: 0x0002191b.
Resolution

Cumulative update information

Cumulative update 9 for SQL Server 2012

The fix for this issue was first released in Cumulative Update 9. For more information about how to obtain this cumulative update package for SQL Server 2012, click the following article number to view the article in the Microsoft Knowledge Base:
2867319 Cumulative update package 9 for SQL Server 2012
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 2012 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:
2692828 The SQL Server 2012 builds that were released after SQL Server 2012 was released

Cumulative update 5 for SQL Server 2012 Service Pack 1

The fix for this issue was first released in Cumulative Update 5. For more information about how to obtain this cumulative update package for SQL Server 2012 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:
2861107 Cumulative update package 5 for SQL Server 2012 Service Pack 1
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 2012 Service Pack 1 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:
2772858 The SQL Server 2012 builds that were released after SQL Server 2012 Service Pack 1 was released

Cumulative update 7 for SQL Server 2008 R2 Service Pack 2 (SP2)

The fix for this issue was first released in Cumulative Update 7. For more information about how to obtain this cumulative update package for SQL Server 2008 R2 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
2844090 Cumulative update package 7 for SQL Server 2008 R2 Service Pack 2
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 Service Pack 2 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:
2730301 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 2 was released

Hotfix information

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.

Prerequisites

To apply this hotfix, you must have SQL Server 2008 R2 installed.

Restart requirement

You do not have to restart the computer after you apply the hotfix.

File information

The global version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
File nameFile versionFile sizeDateTimePlatform
Xmlsub.dll2009.100.4280.0278,64812-Apr-201310:10x64
Xmlsub.dll2009.100.4280.0179,83212-Apr-201310:13x86
Xmlsub.dll2009.100.4280.0522,36012-Apr-201310:09IA-64
Note This hotfix also contains all the fixes that are included in SQL Server 2008 R2 Service Pack 2 (SP2) Cumulative Update 6 (CU6). To determine which files are changed, please review the "File information" section of the cumulative update. After you apply this fix, the only cumulative updates that can be applied are SQL Server 2008 R2 SP2 Cumulative Update 7 (CU7) or a later cumulative update.



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

Article ID: 2837247 - Last Review: 08/21/2013 03:22:00 - Revision: 5.0

  • Microsoft SQL Server 2008 R2 Datacenter
  • Microsoft SQL Server 2008 R2 Enterprise
  • Microsoft SQL Server 2008 R2 Standard
  • Microsoft SQL Server 2008 R2 Web
  • Microsoft SQL Server 2008 R2 Workgroup
  • Microsoft SQL Server 2008 R2 Express
  • Microsoft SQL Server 2008 R2 Express with Advanced Services
  • SQL Server 2012 Enterprise Core
  • Microsoft SQL Server 2012 Developer
  • Microsoft SQL Server 2012 Enterprise
  • Microsoft SQL Server 2012 Express
  • Microsoft SQL Server 2012 Standard
  • Microsoft SQL Server 2012 Web
  • kbautohotfix kbqfe kbhotfixserver kbfix kbsurveynew kbexpertiseadvanced KB2837247
Feedback