DFSR is not working anymore

Question

_{Friday, August 7, 2009 10:18 AM}

I have setup the dfs without any problem it has been working for last two months. Suddenly it as stopped with following error .

 Quick help is much appricated
The DFS Replication service failed to recover from an internal database error on volume D:. Replication has been stopped for all replicated folders on this volume.

Additional Information:

Error: 9214 (Internal database error (-1605))

Volume: 5FFCD36C-2DAF-11DE-884A-005056915034

Database: D:\System Volume Information\DFSR

For more information, see Help and Support Center at

All replies (3)

_{Friday, August 7, 2009 5:19 PM ✅Answered | 1 vote}

Hi,

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

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
http://support.microsoft.com/kb/95755
 

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.

Hope it helps.

This posting is provided "AS IS" with no warranties, and confers no rights.

_{Thursday, August 20, 2009 10:39 AM ✅Answered}

Thanks sorry for late reply I was on summer holidays. deleting the private folder has done the job for me.

_{Monday, February 3, 2020 3:47 PM}

Does this work for 2019 also?  I see there is a "DFSR\Private" folder under System VOlume Information, is this the same folder for 2019?

Confirmed This is it, repaired this in 2019 like this:

• Stopped DSFR Service
• Deleted the DFSR folder with elevated CMD "RD “c:\system volume information\dfsr” /s /q"
• Started DSFR Service
• DSFR folder is recreated, waiting for sync to finish, which should rebuild the DB and fix the error.