DFSR errors

Question

I have three DFRS servers replicating a bunch of file shares. It has been running pretty nice for the last three years. During my weekly checks, I am now seeing DFS stopping replication. It says it the database is corrupted. Did a reboot and that seem to clear it up. However, DFS is still reporting errors on a server that does exist, but it is not a member of any replication group. Never has been. DFS is quitting and not replicating files because of this error. All dfs services are complaining about this particular server. This particular server has never has been a member of DFS. Why are the rest of the systems stopping DFS because of a non-existent replication member ?

(Windows logs report; No more information to provide)

Suggestions ?

Answer 1

Hi Robin Ganderton

Just checking to see how is everything.

Please feel free to let me know if you need any assistance

Answer 2

Hi Robin Ganderton

Don't forget to share your experience with "Accept the answer" . That others in community with similar issues can benefit from the guidance. Thank you

Answer 3

Dear Robin Ganderton

I think the issue is likely caused by stale or orphaned metadata within the DFS Replication (DFSR) configuration database on one or more of your servers. Even if the problematic server was never an actual replication member, its hostname may still exist in AD DFSR objects or in the server’s local DFSR database, causing the service to treat it as a missing partner. A reboot temporarily clears the active DFSR process, but it does not repair the underlying metadata issue - which is why the errors continue.

I recommend checking the DFSR Global Settings and Topology in Active Directory using tools like DFSRdiag, ADSIEDIT, or DFSMGMT.msc to identify and remove any lingering references to the unknown server. You may also need to force a rebuild of the DFSR database by stopping the service, renaming the DSFDatabase folder, and allowing DFSR to automatically recreate a clean database. Please ensure you perform this step during a maintenance window, as initial sync may take time. After cleanup, run dfsrdiag /pollad on each server to ensure all replicas refresh their AD configuration.

Once the stale records are removed, DFSR should resume normal replication across your three valid members.

If you find this explanation helpful, please click “Accept Answer” to support others who may face the same issue

Thank you

Answer 4

It sounds like you're experiencing issues with the DFS Replication (DFSR) service, particularly related to a server that is not part of any replication group but is still causing errors. Here are some suggestions to address this issue:

1. Check DFS Configuration: Ensure that the server in question is not mistakenly configured as a member of any replication group. Sometimes, remnants of previous configurations can cause issues.
2. Event Logs: Look for specific event IDs related to DFSR in the Windows Event Viewer. This can provide more insight into what might be causing the replication to stop. Pay attention to Event ID 2104, which indicates that the DFSR service has stopped replication due to a database issue.
3. Database Recovery: If the DFSR database is corrupted, you may need to rebuild it. You can do this by deleting the database from the System Volume Information folder and restarting the DFSR service. This will trigger an initial replication from other members, but be cautious as this may lead to conflicts if not managed properly.
4. Force Active Directory Replication: If your DFS servers are in different Active Directory sites, ensure that Active Directory replication is functioning properly. Use the DFSRDIAG POLLAD command to update the DFSR service after any configuration changes.
5. Review DFSR Health: Use the Dfsrdiag tool to check the health of the DFSR setup. This can help identify any underlying issues that might not be immediately apparent.
6. Consider Server Role: If the problematic server has never been a member of DFS, ensure that it is not inadvertently being referenced in any DFS configurations. This could be causing the other servers to fail in their replication tasks.

If these steps do not resolve the issue, you may want to consider further troubleshooting or consulting Microsoft documentation for more specific scenarios related to DFSR errors.

---

References:

• DFS Replication FAQ
• Recover from a DFSR database crash on designated primary member
• Troubleshoot the File Replication Service and the Distributed File System