Server 2019: DFS Replication broken after network Outage - DFSR Event 6002

Andre Dierker 1 Reputation point


we sometimes have network outages and sometimes after that the DFS replication does not work anymore. The DFS Replication Healt Reports give this error:

Inconsistent configuration detected (invalid object).
Affected replicated folders: All replicated folders on this server.
Description: The DFS Replication service detected invalid msDFSR-Subscriber object data while polling for configuration information. Additional information includes Object DN: CN=ef4970ff-8aae-4eb5-9753-d9c6328bab5d,CN=DFSR-LocalSettings,CN=DC-BNN,OU=Domain Controllers,DC=contoso,DC=com Attribute Name: msDFSR-MemberReference and domain controller: Event ID: 6002
Last occurred: Mittwoch, 20. April 2022 at 13:27:41 (GMT1:00)

Both Servers seem to be consistent:


All domain controllers have migrated successfully to the Global state ('Eliminated').
Migration has reached a consistent state on all domain controllers.

I do not really understand what to to. We have a lot of Data in the filesystem so we can't start from scratch.
It's Server 2019 on both Machines.

Thank You

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,574 questions
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Limitless Technology 39,506 Reputation points


    very often this issue appears after lost connectivity and when the connection has been restore you end up with duplicate connections. If that is the case what you can do is to delete the connections that appear as duplicates. You can use adsiedit connected to configuration naming context to delete duplicate connections and then force replication across all DCs.
    The reference to domain controller: DC-BNN.contoso.... within the Event Viewer error is only saying which domain controller reported the issue.
    You need to run a search to see if a matching "msDFSR-Subscriber" object with the same GUID value for the "cn" attribute exists. If it does, it will be nested below the computer we're trying to find in order to fix the missing "msDFSR-ComputerReference" error from the Event Log.

    Use the discussion here for reference:

    --If the reply is helpful, please Upvote and Accept as answer--

    0 comments No comments

  2. Andre Dierker 1 Reputation point

    Hello and Thanks,

    I don't think they are duplicate entries, either on one server or the other. It looks the same on both servers. Is this the right place I'm looking?


    We have three configured namespaces and the sysvol as shown here



    0 comments No comments

  3. Andre Dierker 1 Reputation point

    Any idea on this?

    Suddenly only one of two DCs show this error.

    0 comments No comments