Select the product you need help with
Error event IDs 2014 and 2004 and other Error events may be logged when you try to perform a replication on a Windows Server 2003 R2-based server that has DFSR installedArticle ID: 957555 - View products that this article applies to. On This PageSUMMARYThis article describes two problems that you may encounter
on a Windows Server 2003 R2-based server when you perform a Distributed File System (DFS) replication on one or more
nodes. SYMPTOMSProblem 1On a Windows Server 2003 R2-based server that has Distributed File System Replication (DFSR) installed, a replication may fail when you try to perform the replication on one or more nodes. When this problem occurs, you receive the following Error event in the event log:Event Type: Error
Problem 2On a Windows Server 2003 R2-based server that has Distributed File System Replication (DFSR) installed, a replication may fail when you try to perform the replication on one or more nodes. When this problem occurs, you receive the following Error events in the event log.Error event 1 Event Type: Error Event Type: Error Event Type: Error Event Type: Error CAUSECause of problem 1This problem occurs when the local system account (NT AUTHORITY\System) is not granted Full Control permissions for the system volume information folder on the Volume Letter volume or for the sub folders of this folder.Cause of problem 2This problem occurs when the volume or the volumes to which Error event IDs 2104 and 2004 refer are out of disk space.RESOLUTIONResolution for problem 1Grant Full Control permissions to the System account for the system volume information folder and for all its sub folders. Then, restart the Windows Server 2003 R2-based server.Resolution for problem 2Free up disk space on the volumes that are referenced in Error event IDs 2104 and 2004. After you free up space on these volumes, DFSR will automatically check the available disk space without any additional steps. You do not have to restart the service or restart the server. Event IDs 2106 and 2002 are logged when the database has successfully recovered.STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section. PropertiesArticle ID: 957555 - Last Review: October 24, 2008 - Revision: 1.0 APPLIES TO
|


Back to the top








