question

GloriaGu-MSFT avatar image
0 Votes"
GloriaGu-MSFT asked ·

DFS replication has stopped due to database error

Following a networking issue that disrupted our FailoverCluster last week, DFS replication has stopped on our primary server (Server 2016). It appears the database needs to be rebuilt. What is the best way to do this?

Here is the error text from the DFS Diagnostic Report for one of the Resource Groups on the volume:

A database problem is blocking replication on volume W:.
Affected replicated folders: Common
Description: The DFS Replication service was unable to recover from an internal database error on volume W:. Replication has stopped for all replicated folders on this volume until the database is automatically rebuilt. If the database is rebuilt successfully, replication will resume after the rebuilding is complete. If the database cannot be rebuilt, a separate event is generated. If you are seeing this error more than two times in seven days, we recommend that you run Chkdsk on the volume that contains the database. Event ID: 2104
Last occurred: Thursday, June 21, 2018 at 1:36:45 PM (GMT-8:00)
Suggested action: For information about troubleshooting this problem, see The Microsoft Web Site

Volume W: is full or failing.
Affected replicated folders: Common
Description: The DFS Replication service stopped replication on volume W:. This failure can occur because the disk is full, the disk is failing, or a quota limit has been reached. Event ID: 2004
Last occurred: Thursday, June 21, 2018 at 9:36:45 AM (GMT-8:00)
Suggested action: Increase the available disk space on the specified volume or move the replicated folder to a different volume. See additional information about disk space under the informational section in the "Amount of disk space used by replicated folders" table.

=======================================

The DFS Replication log on the server continues to show repeated Event 2104 and 2004 entries similar to these:

DFSR Event 2004 The DFS Replication service stopped replication on volume W:. 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: 46E11D07-A11E-40A2-B886-EA6C89B7637B

DFSR Event 2104 The DFS Replication service failed to recover from an internal database error on volume W:. Replication has been stopped for all replicated folders on this volume.
Additional Information:
Error: 9214 (Internal database error (-1086))
Volume: 46E11D07-A11E-40A2-B886-EA6C89B7637B
Database: W:\System Volume Information\DFSR



Here are sample log entries from around the time the failure occurred:

6/14 6:02:50pm FailoverClustering Event 1795
Cluster physical disk resource terminate encountered an error.
Physical Disk resource name: File Server
Device Number: 3
Device Guid: {e026fce1-e9d7-62be-35e5-605888014a70}
Error Code: 1168
Additional reason: ReleaseDiskPRFailure

6/14 6:02:42pm WinAppLog ESENT Event 482 DFSRs (3104) \.\W:\System Volume Information\DFSR\database_14B6_CB27_B6CB_7E6\dfsr.db: An attempt to write to the file "\.\W:\System Volume Information\DFSR\database_14B6_CB27_B6CB_7E6\fsr.log" at offset 172032 (0x000000000002a000) for 4096 (0x00001000) bytes failed after 0.000 seconds with system error 21 (0x00000015): "The device is not ready. ". The write operation will fail with error -1022 (0xfffffc02). If this error persists then the file may be damaged and may need to be restored from a previous backup.

Thread source link: https://social.technet.microsoft.com/Forums/windowsserver/en-US/efaaaef1-ba42-4b1c-8b5b-6b58ff8c8e70/dfs-replication-has-stopped-due-to-database-error?forum=winserverfiles

windows-server-storage
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

XiaoweiHe-MSFT avatar image
0 Votes"
XiaoweiHe-MSFT answered ·

Hi,

According to the error description, this error may be caused by lack of disk space or corrupt DFSR files.

1.Please check the size of replicated folder and free space of the problematic server.

2.Please check if the NT AUTHORITY\System account has Full Control permissions on "System Volume Information" folder.

3.If there are enough free space, please try deleting the DFS-R folder for troubleshooting.

a.Stop the "DFS Replication" service on problem server.

b.On the system drive on problem server, show hidden files and system protected files. Give all permission on "System Volume Information" folder to you.

c.Double-click "System Volume Information", we should find DFSR folder. Backup this folder to avoid data loss.

d.Delete all "DfsrPrivate" folder in DFSR if there are several subfolder.

Restart "DFS Replication" service and test.

4.If the error still occurs, please check the Hard Disk to make sure there is no Hard Failure. Run command "chkdsk D: /r" (without quotation mark).

5.At the same time, please try to replicate without this server and let us know the result.

In addition, please also check the thread discussed before.

https://social.technet.microsoft.com/Forums/en-US/821d16d9-1f79-4104-bc23-b263c9454e7a/dfsr-error-2104-and-2004?forum=winservergen

https://social.technet.microsoft.com/Forums/windows/en-US/b69839aa-f050-419c-9344-6b7bf067c318/dfsr-database-corrupt?forum=winserverfiles

Best Regards,

·
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.