DFS was configured and working fine on Server 2003 STD and suddenly stopped.
The server was EOL and we have upgraded and went to Server 2008 R2 STD.
Currently no DFS replication works.
I am getting the following errors in event viewer
The DFS Replication service stopped replication on the replicated folder at local path D:\Share.
Additional Information:
Error: 9007 (Unable to set root path)
Additional context of the error:
Replicated Folder Name: Share
Replicated Folder ID: 2E689D1A-7CC7-4BED-8FA7-1BD1FE9661AB
Replication Group Name: Brentwood1 to NAS F
Replication Group ID: 5965B0C7-3C54-4765-9224-F8CD99AE966A
Member ID: 99B7EE2B-0E36-46FF-93C2-B199F57ADCB3
I also get this event which is not an error
The DFS Replication service initialized the replicated folder at local path D:\Share. This member is the designated primary member for this replicated folder.
Additional Information:
Replicated Folder Name: Share
Replicated Folder ID: 2E689D1A-7CC7-4BED-8FA7-1BD1FE9661AB
Replication Group Name: Brentwood1 to NAS F
Replication Group ID: 5965B0C7-3C54-4765-9224-F8CD99AE966A
Member ID: 99B7EE2B-0E36-46FF-93C2-B199F57ADCB3
I have also tried following resolution from a different thread:
According to the research, the issue maybe occur because the DFS servers do not have the permission to read AD information on themselves or their partners.
1. Please open the ADSIedit.msc console to verify the "Authenticated Users" is set with the default READ permission on the following object:
a. The computer object of the DFS server
b. The DFSR-LocalSettings object under the DFS server computer object
2. After the permissions is set correct, please run "DFSRDIAG POLLAD" to pick up the changes.
Another possible reason is that FSRM is configured as some types of files are blocked from DFS replication. When the DFSR filters are not set to match FSRM screens by extension and the files exist on the server before screening, this can lead to degraded DFSR performance and the files will never replicate.
If possible, please remove file screening and reconfigure it to remove files by extension or set a comparable DFSR filter rule to prevent replication attempts.
This is not resolve my issue.