Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. DFSR stops replication after an unexpected shutdown in a Windows 8.1 or Windows Server 2012 R2 environment

DFSR stops replication after an unexpected shutdown in a Windows 8.1 or Windows Server 2012 R2 environment

View products that this article applies to.

Symptoms

Consider the following scenario:
  • On a domain server in a Windows 8.1 or Windows Server 2012 R2 environment, you have a Distributed File System Replication (DFSR) service folder.
  • Many replication activities appear in the folder.
  • The domain server performs an unexpected shutdown (also known as a "dirty shutdown.")
  • The NTFS journal wrap occurs after the unexpected shutdown.

In this scenario, the DFSR replication of folders stops working after the DFSR garbage collection task is performed.

↑ Back to the top

Cause

When there is an unexpected shutdown, DFSR updates records by restamping and marking records as GC VersionVectorTombstone. Journal wrap also marks the record as not present. The garbage collection task goes into effect, and the database GUID is added as a tombstoned GUID. DFSR then marks the database GUID as stale. When a new file is created, it is stamped with the stale database GUID. This causes the record to be filtered out from the version vector because it is a stale database. Therefore, replication does not occur.

↑ Back to the top

Resolution

Hotfix information

A supported hotfix is available from Microsoft Support. 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 the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

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, contact 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, go to the following Microsoft website:
http://support.microsoft.com/contactus/?ws=support
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 update, you must first have update 2919355 installed in Windows 8.1 or Windows Server 2012 R2.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any previously released hotfix.

↑ Back to the top

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

Windows 8.1 and Windows Server 2012 R2 file information and notes

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

    VersionProductMilestoneService branch
    6.3.960 0.16 xxxWindows 8.1 and Windows Server 2012 R2RTMGDR
    6.3.960 0.17 xxxWindows 8.1 and Windows Server 2012 R2RTMGDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows 8.1 and Windows Server 2012 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 8.1
File nameFile versionFile sizeDateTimePlatform
Dfsrdiag.exe6.3.9600.173311,830,91230-Aug-201420:47x86
For all supported x64-based versions of Windows 8.1 and Windows Server 2012 R2
File nameFile versionFile sizeDateTimePlatform
Dfsrprovs.mofNot Applicable75,76122-Aug-201306:48Not Applicable
Dfsrress.dll6.3.9600.163842,04822-Aug-201311:43x64
Dfsrs.exe6.3.9600.173313,833,34430-Aug-201421:51x64
Dfsrwmiv2.dll6.3.9600.173312,383,36030-Aug-201421:51x64
Dfsrwmiv2.mofNot Applicable40,48418-Jul-201315:53Not Applicable
Dfsrwmiv2_uninstall.mofNot Applicable2,70818-Jun-201315:17Not Applicable
Dfsrdiag.exe6.3.9600.173312,383,87230-Aug-201421:51x64
Dfsrmig.exe6.3.9600.173312,224,12830-Aug-201421:51x64

Additional file information for Windows 8.1 and for Windows Server 2012 R2

Additional files for all supported x86-based versions of Windows 8.1
File namePackage_1_for_kb2996883~31bf3856ad364e35~x86~~6.3.1.0.mum
File versionNot Applicable
File size1,833
Date (UTC)31-Aug-2014
Time (UTC)10:09
File namePackage_for_kb2996883_rtm_gm~31bf3856ad364e35~x86~~6.3.1.0.mum
File versionNot Applicable
File size1,405
Date (UTC)31-Aug-2014
Time (UTC)10:09
File namePackage_for_kb2996883_rtm~31bf3856ad364e35~x86~~6.3.1.0.mum
File versionNot Applicable
File size1,468
Date (UTC)31-Aug-2014
Time (UTC)10:09
File nameX86_0385da1bac24df568325382e7daf526c_31bf3856ad364e35_6.3.9600.17331_none_e1480762f40e3757.manifest
File versionNot Applicable
File size706
Date (UTC)31-Aug-2014
Time (UTC)10:09
File nameX86_microsoft-windows-dfsr-util-dfsrdiag_31bf3856ad364e35_6.3.9600.17331_none_6e90bcd506fb438a.manifest
File versionNot Applicable
File size2,651
Date (UTC)30-Aug-2014
Time (UTC)23:15
Additional files for all supported x64-based versions of Windows 8.1 and Windows Server 2012 R2
File nameAmd64_593d9a3862340298665fa000bf1d5af9_31bf3856ad364e35_6.3.9600.17331_none_7b1afdac1129ed78.manifest
File versionNot Applicable
File size709
Date (UTC)31-Aug-2014
Time (UTC)10:12
File nameAmd64_a3c16e3d4eb71166cdd03d7011f21df6_31bf3856ad364e35_6.3.9600.17331_none_0cd51f86157951cc.manifest
File versionNot Applicable
File size712
Date (UTC)31-Aug-2014
Time (UTC)10:12
File nameAmd64_e29f70ba0af43db5ecf726d6cbea8def_31bf3856ad364e35_6.3.9600.17331_none_6152c19211cd80f2.manifest
File versionNot Applicable
File size710
Date (UTC)31-Aug-2014
Time (UTC)10:12
File nameAmd64_microsoft-windows-dfsr-core-serveronly_31bf3856ad364e35_6.3.9600.17331_none_8e7d08f77b9896d0.manifest
File versionNot Applicable
File size41,487
Date (UTC)31-Aug-2014
Time (UTC)10:12
File nameAmd64_microsoft-windows-dfsr-util-dfsrdiag_31bf3856ad364e35_6.3.9600.17331_none_caaf5858bf58b4c0.manifest
File versionNot Applicable
File size2,655
Date (UTC)31-Aug-2014
Time (UTC)00:34
File nameAmd64_microsoft-windows-dfsr-util-dfsrmig_31bf3856ad364e35_6.3.9600.17331_none_19923ea10887686e.manifest
File versionNot Applicable
File size2,681
Date (UTC)31-Aug-2014
Time (UTC)00:34
File namePackage_1_for_kb2996883~31bf3856ad364e35~amd64~~6.3.1.0.mum
File versionNot Applicable
File size2,042
Date (UTC)31-Aug-2014
Time (UTC)10:12
File namePackage_2_for_kb2996883~31bf3856ad364e35~amd64~~6.3.1.0.mum
File versionNot Applicable
File size2,750
Date (UTC)31-Aug-2014
Time (UTC)10:12
File namePackage_for_kb2996883_rtm_gm~31bf3856ad364e35~amd64~~6.3.1.0.mum
File versionNot Applicable
File size1,691
Date (UTC)31-Aug-2014
Time (UTC)10:12
File namePackage_for_kb2996883_rtm~31bf3856ad364e35~amd64~~6.3.1.0.mum
File versionNot Applicable
File size2,119
Date (UTC)31-Aug-2014
Time (UTC)10:12

↑ Back to the top

Status

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

↑ Back to the top

References

Learn about the terminology that Microsoft uses to describe software updates.

↑ Back to the top

Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbexpertiseinter, kbsurveynew, kbbug

↑ Back to the top

Article Info
Article ID : 2996883
Revision : 1
Created on : 1/7/2017
Published on : 10/14/2014
Exists online : False
Views : 228