Microsoft help

MS: SYSVol DFS Replication Errors (EventID 2213 – then EventID 4012)

I was having issues trying to get gpupdate to work on a RODC in one of our sites. I kept getting an error about: processing of group policy failed to read the GUID\gpt.ini from a domain controller

Then I decided to check the logs and coincidentally came across DFS replication logs and found this:
The DFS replication service stopped replication on volume C:. This occurs when a DFSR JET datavase 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. wmic /namespace:\\root\microsoftdfs path dfsrVolumeConfig where volumeGuid="B4A015E2-A116-11DE-89FB-806E6F6E6963" call ResumeReplication

After backing up my Sysvol directory and editing the registry to resume replication automatically (change the HKLM\System\CurrentControlSet\Services\DFSR\Parameters\StopReplicationOnAutoRecovery registry key to a DWORD value of 0) I ran the command (from admin cmd) exactly as they state in the event properties:
wmic /namespace:\\root\microsoftdfs path dfsrVolumeConfig where volumeGuid=”B4A015E2-A116-11DE-89FB-806E6F6E6963″ call ResumeReplication

I then got this error:
The DFS Replication service stopped replication on the folder with the following local path: C:\Windows\SYSVOL\domain. This server has been disconnected from other partners for 64 days, which is longer than the time allowed by the MaxOfflineTimeInDays parameter (60). DFS Replication considers the data in this folder to be stale, and this server will not replicate the folder until this error is corrected.

This means that my Sysvol directory has not synced for more than 64 days, and that now the registry setting (which is set to a max of 60 days) is blocking DFS replication from working. So I had to increase the default MaxOfflineTimeInDays:
wmic.exe /namespace:\\root\microsoftdfs path DfsrMachineConfig set MaxOfflineTimeInDays=65

Soon after everything started working and the error logs cleared up.



Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s