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 installed

This 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.

Problem 1

On 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
Event Source: DFSR
Event Category: None
Event ID: 2104
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description: The DFS Replication service failed to recover from an internal database error on volume Volume Letter:. Replication has been stopped for all replicated folders on this volume.
Additional Information:
Error: 9201 (Access was denied to the database (-1032))
Volume: Volume GUID
Database: Volume Letter\System Volume Information\DFSR

Problem 2

On 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 Source: DFSR
Event Category: None
Event ID: 2104
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description: The DFS Replication service failed to recover from an internal database error on volume Volume Letter:. Replication has been stopped for all replicated folders on this volume.
Additional Information:
Error: 9204 (The volume hosting the database is out of free space (-1808))
Volume: Volume GUID
Database: Volume Letter\System Volume Information\DFSR

Error event 2

Event Type: Error
Event Source: DFSR
Event Category: None
Event ID: 2004
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description: The DFS Replication service stopped replication on volume Volume Letter:. This failure can occur because the disk is full, the disk is failing, or a quota limit has been reached. This can also occur if the DFS Replication service encountered errors while attempting to stage files for a replicated folder on this volume.
Additional Information:
Error: 9014 (Database failure)
Volume: Volume GUID

Error event 3

Event Type: Error
Event Source: DFSR
Event Category: None
Event ID: 439
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description: Dfsr (3748) \\.\D:\System Volume
Information\DFSR\database_98F4_7E20_F47E_134\dfsr.db: Unable to write a shadowed header for file \\.\Volume Letter:\System Volume Information\DFSR\database_98F4_7E20_F47E_134\tmp.edb. Error -1808.

Error event 4

Event Type: Error
Event Source: DFSR
Event Category: None
Event ID: 454
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Message : Dfsr (3748) \\.\Volume Letter:\System Volume Information\DFSR\database_98F4_7E20_F47E_134\dfsr.db: Database recovery/restore failed with unexpected error -566.

Cause of problem 1

This 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 2

This problem occurs when the volume or the volumes to which Error event IDs 2104 and 2004 refer are out of disk space.

Resolution for problem 1

Grant 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 2

Free 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.

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