Hi Everybody,

DFS was configured and working fine on 2 Windows Server 2012 64 Bit.  But now no longer to replicate. I'm have Done some do some troubleshooting. But still failed to solve the issue.

1.)Failed to run on both DFS Server :\>dfsrdiag backlog /ReceivingMember:server1/SendingMember:server2 /RGName:folder/RFName:folder. 

2.)DFS Replication Health Report Failed to Generate.

3.When i trying to restart (Server A) as the Promary Member. I always get this error: Error: The DFS Replication service has detected an unexpected shutdown on volume D:. This can occur if the service terminated abnormally (due to a power loss, for example) or an error occurred on the volume. The service has automatically initiated a recovery process. The service will rebuild the database if it determines it cannot reliably recover. No user action is required.

4.) No Error on Evertviewer log.

I am inclined to recreate the replicated folder in DFS to see if that resolves the issue but I cannot seem to find a step-by-step process on how to effectively do this.

Looking forward to your response.

Regards,

Nicolas

 

Could any Expert help me with my issue?

Hi All,

I found some similar post for how to recreate the dfs database. but some of the step is different.  shall i need go for step (A) or (B) on below?  Do i need to Set ServerA as Primary server & Dfsradmin Membership Set /RGName:<RG Name> /RFName:<RF Name> /MemName:<Member Name> /IsPrimary:True ? 

A) Remove any existing Replication Groups, Remove the File Services/DFS Replication Role. Reboot (it will make you reboot twice to fully remove). Next, we need to remove the leftover DFS Database, which is hidden in C:\system volume information. Open a cmd prompt using run as administrator and then run the following command > c:\icacls c:\system volume information /grant Administrators:F

Next, run the following, *but be careful to not forget \dfsr! > c:\Rd c:\system volume information\dfsr /s /q

 

B) 1.       Stop and ALSO disable the DFSR service on <ServerA> server (don't just simply stop it)

      2.       In Windows Explorer open the specific drive

      3.       Right click on the "System Volume Information" directory and select Properties\Security

Note: You might need to select the option for "Show hidden files, folders or drives" and also uncheck "Hide protected operating system files" in the folders view options to be able to even see the "System Volume Information" directory.

     4.       Grant your user account that you're logged in with (if a member of Administrators group this will also suffice) "Full Control" to the "System Volume Information" directory.

Note: You may get an error on setting security on some files - this is expected.

     5.       Open an elevated/Administrative command prompt. Switch to the "<drive letter>:\System Volume Information" directory

     6.       Type the command "rmdir DFSR /s"

     7.       Enable and re-start the DFSR service on <ServerA> server

     8.       Set ServerA as Primary server:

Dfsradmin Membership Set /RGName:<RG Name> /RFName:<RF Name> /MemName:<Member Name> /IsPrimary:True

After i restart my DFS Server A today, Now i able to generate a DFS diagnostics Report. 

1 error to report - Volume E: is full or failing.

The DFS Replication service stopped replication on volume E:. This failure can occur because the disk is full, the disk is failing, or a quota limit has been reached. Event ID: 2004

But my E Drive: still available disk space 400GB.  Anyone know how to resolve this issue?

Thanks in advanced. 

When you got the error in event viewer, from your first post, what was the event ID, do you remember?

Have you gotten any event ID 2213?

Is there plenty of free disk space on both replication partners?

Hi John,

Yes, I got this Event ID 2213& 2004. Both of the replication partners still have a lots free disk space.

Regards,

Nicolas

Hi,

If there is enough free disk space, please check if it is the staging folder limitation which causes the issue. Set Staging folder larger in DFS management to see the result.

Event 2213 should be caused by resetting DFSR database but if issue still exists after enlarge staging folder and reboot the system, refer to this article for recovering the replication:

DFSR event ID 2213 in Windows Server 2008 R2 or Windows Server 2012

https://support.microsoft.com/en-us/kb/2846759