DFS Error : Found 2 <DfsrReplicatedFolderConfig> objects with same ReplicationGroupGuid

After recovering from a crashed virtual server we started getting the following error when checking DFS backlogs ::
Found 2 <DfsrReplicatedFolderConfig> objects with same ReplicationGroupGuid

There are 4 Server 2008 R2 servers connected in a mesh for the DFS structure.  We only get the error when checking the backlogs on 1 of the servers.  The DFS seems to still be in synch and new files are synchronized to all servers constantly.
Who is Participating?
arnoldConnect With a Mentor Commented:
An MS form searching for objects with same ReplicationGroupGuid
suggesting the use of dfsrdiag pollad.
The suggestion includes going through the system volume information as well as changes/adjustment to a registry key.

When you say recovered, you mean you restored the VM ....... in the various ways?

Did you readd the recovered VM back DFS-R group/DFS without removing the old reference???
keystonetechAuthor Commented:
The virtual servers VHD expanded to the point it filled the physical storage and the server crashed.  We had to run the DFS for 2 days without this server as part of it.  During that time we compressed the VHD file, expanded the storage space and then were able to get the virtual server up and running again.
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

keystonetechAuthor Commented:
Yes we've found the same instructions on multiple sites.  They have not had any impact on the problem.
Can you check whether the DFS-R replication somehow references two connections to or from this system?

i.e. connection
server A to this system
system to server a
system to server A

There should be a GUID of the duplicate.

to which system does that GUID belong.  That may simplify

Difficulty is whether there are files on the recovered VM that have yet to replicate out.

one option is to use robocopy with the /L flag (run through but do not actually copy.

to see if there are files here that need to go look at the staging folder on this VM, and see if there are outsdanding .....
keystonetechConnect With a Mentor Author Commented:
We eventually contacted microsoft and had one of their technicians take a look.
In the end they stopped all DFS services, increased out staging folder size, deleted all replica and volume xml files, deleted associated registry entries and restarted the server.
keystonetechAuthor Commented:
Arnolds answer was part of the solution but a few other items were required.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.