When you use the Distributed File System (DFS) Replication service to replicate many files on a computer that is running Windows Server 2008, the DFS Replication service may stop responding during the initial replication. Additionally, in the DFS Replication event log, you may find warning events that have the event ID of 4102. However, you do not find the corresponding events that have the event ID of 4104.
Note The start of an initial replication is indicated by an event that has the event ID of 4102. The completion of the initial replication is indicated by a corresponding event that has the event ID of 4104.
If you run the dfsrdiag backlog command several times to check the replication backlog, the same files appear at the top of the output list.
You may have to restart the DFS Replication service to resolve this problem. When you restart the DFS Replication service, the replication backlog may be decreased. However, the DFS Replication service may stop responding again.
This problem occurs because of a deadlock that occurs between the two threads in the DFS Replication service.
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 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, visit the following Microsoft Web site:
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.
Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the “Hotfix Request” page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.
To apply this hotfix, your computer must be running Windows Server 2008 Service Pack 2 (SP2).
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
The English 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.
Windows Server 2008 file information notes
The .manifest files and the .mum files that are installed in each environment are listed in the "Additional file information for Windows Server 2008" section. These files and their associated .cat (security catalog) files are critical to maintaining the state of the updated component. The .cat files are signed with a Microsoft digital signature. The attributes of these security files are not listed.
For all supported x86-based versions of Windows Server 2008 SP2
For all supported x64-based versions of Windows Server 2008 SP2
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
The following are samples of event logs for a 4102 event and for a 4104 event.
The DFS Replication service initialized the replicated folder at local path <path name> and is waiting to perform initial replication. The replicated folder will remain in this state until it has received replicated data, directly or indirectly, from the designated primary member.
Additional Information: Replicated Folder Name: Data Replicated Folder ID: <GUID> Replication Group Name: <name> Replication Group ID: <GUID> Member ID: <GUID>
The DFS Replication service successfully finished initial replication on the replicated folder at local path <path name>.
Any local pre-existing content in this replicated folder that did not exist on the primary member for <replication folder name> has been moved to the hidden system folder DfsrPrivate\PreExisting under the replicated folder root.
Content in the DfsrPrivate\PreExisting folder will not be replicated to other members of the replication group, and will not be deleted by the DFS Replication service during any automatic clean-up. If you would like this content to be replicated to other members, please move the content into the replicated folder outside the DfsrPrivate folder.
Additional Information: Replicated Folder Name: <name> Replicated Folder ID: <GUID> Replication Group Name: <name> Replication Group ID: <GUID> Member ID: <GUID>
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: -
824684 Description of the standard terminology that is used to describe Microsoft software updates
Additional file information for Windows Server 2008
Additional files for all supported x86-based versions of Windows Server 2008