I was attempting to add a new DFSR node to an existing DFSR Replication Group consisting of 17 file servers. When adding the server the following error was experienced.
DFS Replication cannot replicate the replicated folder REPLICATEDFOLDER because the local path E:\replicationgroup is not the fully qualified path name of an existing, accessible local folder. This replicated folder is not replicating to or from this server. Event ID: 6404
This particular error is generally experienced when people attempt a non NTFS volume such as ReFS to a DFSR replication group as documented on the following forum.
In my case, I experienced this error with DFSR setup on NTFS volume on a new branch server.
The customer moved the DFSR node from one office, to another office. The C:\ "SYSTEM" volume was formatted and reloaded with a fresh copy of 2012 R2 with latest patches, however the E:\ "DATA" volume was not formatted. As a result it has its legacy DFSR Database, Staging data etc.
To clean up the staging data I created a new directory in C:\ called "empty":
I then ran the following commands after stopping the DFSR Replication service on the spoke server:
Robocopy "C:\Empty" "E:\System Volume Information\DFSR" /MIR
rmdir "E:\System Volume Information\DFSR"
Starting the DFSR replication service resulted in the error above.
After playing around a bit more, I found that in addition to flushing all data in System Volume Information\DFSR you must also remove the DfsrPrivate link which points to the System Volume Information\DFSR sub directory for DfsrPrivate data.
After doing this, starting the DFS Replication service kicks of its normal DFSR Initial Sync shown by a state of 2:
Wmic /namespace:\\root\microsoftdfs path dfsrreplicatedfolderinfo get replicationgroupname,replicatedfoldername,state
State Values (Uninitialized, Initialized, Initial Sync, Auto Recovery, Normal, In Error), ValueMap (0, 1, 2, 3, 4, 5)}
Need help with DFSR In Perth? Click for IT Support.