This article describes an issue that occurs when you use the Distributed File System (DFS) Replication database cloning feature on a clustered volume in Windows Server 2012 R2. A hotfix is available to fix this issue. The hotfix has a prerequisite.

Symptoms

Assume that you add a new member to an existing DFS Replication (DFSR) group and you use the DFSR database cloning feature to add the new downstream server. After the downstream server is added, if the downstream server is a cluster, you will receive event ID 4102 that's followed by event ID 4104. However, only event ID 4104 is expected.

The following is an example for event ID 4102 in DFSR:

Hotfix information

Important If you install a language pack after you install this hotfix, you must reinstall this hotfix. Therefore, we recommend that you install any language packs that you need before you install this hotfix. For more information, see Add language packs to Windows.

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

If the hotfix is available for download, there's a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section doesn't appear, submit a request to Microsoft Customer Service and Support to get 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 don't 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:

http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you don't see your language, it's because a hotfix isn't available for that language.

Prerequisites

To apply this hotfix, you must have April 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (2919355) installed in Windows Server 2012 R2.

Registry information

To use the hotfix in this package, you don't have to make any changes to the registry.

Restart requirement

You may have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix doesn't replace a previously released hotfix.

Status

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

More Information

For more information about how to clone a DFS Replication database, see: DFS Replication Initial Sync in Windows Server 2012 R2: Attack of the Clones.

References

See the terminology that Microsoft uses to describe software updates.

File Information

The English (United States) version of this software update installs files that have the attributes that are listed in the following tables. The dates and times for these files are listed in Coordinated Universal Time (UTC). Be aware that dates and times for these files on your local computer are displayed in your local time and with your current daylight saving time bias. The dates and times may also change when you perform certain operations on the files.

Important Windows 8.1 hotfixes and Windows Server 2012 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8.1/Windows Server 2012 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

Notes

  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

    Version

    Product

    Milestone

    Service branch

    6.3.960 0.16 xxx

    Windows Server 2012 R2

    RTM

    GDR

    6.3.960 0.18xxx

    Windows Server 2012 R2

    RTM

    GDR

  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very important to maintain the state of the updated components. The security catalog files, for which the attributes aren't listed, are signed with a Microsoft digital signature.

x64 Windows Server 2012 R2

File name

File version

File size

Date

Time

Platform

Dfsrprovs.mof

Not applicable

75,761

22-Aug-2013

06:48

Not applicable

Dfsrress.dll

6.3.9600.16384

2,048

22-Aug-2013

11:43

x64

Dfsrs.exe

6.3.9600.18040

3,906,048

27-Aug-2015

16:32

x64

Dfsrwmiv2.dll

6.3.9600.18040

2,427,392

27-Aug-2015

16:32

x64

Dfsrwmiv2.mof

Not applicable

40,484

18-Jul-2013

15:53

Not applicable

Dfsrwmiv2_uninstall.mof

Not applicable

2,708

18-Jun-2013

15:17

Not applicable


x64 Windows Server 2012 R2

File property

Value

File name

Amd64_41dc8b19b10a61929e16a822f5cdb91a_31bf3856ad364e35_6.3.9600.18040_none_f7551e368e071fbb.manifest

File version

Not applicable

File size

712

Date (UTC)

28-Aug-2015

Time (UTC)

06:51

Platform

Not applicable

File name

Amd64_microsoft-windows-dfsr-core-serveronly_31bf3856ad364e35_6.3.9600.18040_none_8e711c477ba1bb96.manifest

File version

Not applicable

File size

41,007

Date (UTC)

28-Aug-2015

Time (UTC)

06:51

Platform

Not applicable

File name

Update.mum

File version

Not applicable

File size

1,833

Date (UTC)

28-Aug-2015

Time (UTC)

06:51

Platform

Not applicable


Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×