• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 4315
  • Last Modified:

DFS Replication error

We have 5 Windows 2008 R2 servers that use DFS Replication. All of the sudden only 2 DFS server Replicate files and the rest get this error when I check for backlog
Failed to execute GetVersionVector method. Err: -2147217406 (0x80041002)
I run this command to check backlog
dfsrdiag backlog /rgname:srs-storage /rfname:storage /smem:srrs1 /rmem:srrsgb
We have all the servers on a MPLS
DFS management says the topology is fine.
I think we were close to 100% bandwidth a week ago. We have fixed that in case it was the issue. All servers replacte back to a main and back out again. Worked fine for over a year?
I have tried this help I found on the main server and so far no change
Open a CMD prompt in %windir%\system32\wbem

type mofcomp dfsrprovs.mof

net stop winmgmt
net start winmgmt
net start iphlpsvc
net stop dfsr
net start dfs

Please let me know any info you need, this is driving me crazy. Thanks
  • 4
1 Solution
Patrick BogersDatacenter platform engineer LindowsCommented:

The issue may 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.
RobertJayAuthor Commented:
Thank you. I have checked and set all of these and run the command. Someone else stated the best thing to do next is reboot each server tonight and see if I get the error. I will do that tonight and see if the error is resolved and DFS start working.
RobertJayAuthor Commented:
Well it did not work. I have been looking in the log and found this
The DFS Replication service stopped replication on volume D:. This occurs when a DFSR JET database is not shut down cleanly and Auto Recovery is disabled. To resolve this issue, back up the files in the affected replicated folders, and then use the ResumeReplication WMI method to resume replication.
Additional Information:
Volume: D:
GUID: 9D9B38F6-DA40-11E0-8F2C-782BCB367D91
Recovery Steps
1. Back up the files in all replicated folders on the volume. Failure to do so may result in data loss due to unexpected conflict resolution during the recovery of the replicated folders.
2. To resume the replication for this volume, use the WMI method ResumeReplication of the DfsrVolumeConfig class. For example, from an elevated command prompt, type the following command:
wmic /namespace:\\root\microsoftdfs path dfsrVolumeConfig where volumeGuid="9D9B38F6-DA40-11E0-8F2C-782BCB367D91" call ResumeReplication
For more information, see http://support.microsoft.com/kb/2663685.
RobertJayAuthor Commented:
running this command on each server that had the error fixed my issue. It seems it started due to power outages due to a massive snow storm. It did not take long to resolve and start copy files again. I would say with our servers it took 30-45 minutes to fix the issue and a couple hours to copy missing files that were about 6000 documents.

Thanks again for the help and I hope this helps someone else
RobertJayAuthor Commented:
Info provided was good but fining this error in the log and running the fix command in the error resolved the issue
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.

Join & Write a Comment

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now