Symptoms

Consider the following scenario:

  • You deploy Distributed File System Replication (DFSR) on a Windows Server 2008 R2-based server.

  • You enable Stop Replication functionality in AutoRecovery on the server. To do this, you set the StopReplicationOnAutoRecovery value to 1 under the following registry key:HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\DFSR\Parameters

  • An unexpected shutdown occurs, or you end the Dfsrs.exe process manually.

  • You restart the DFSR service. Event 2213 is logged stating that replication is disabled and requires admin intervention.

  • You disable the replication member in the replicated folder (RF) in Microsoft management console (MMC)

  • Run the dfsrdiag pollad command. Event ID 4114 is received.

  • You enable the replication member in the RF in the MMC.

  • Run the dfsrdiag pollad command.

  • You resume the replication.

In this scenario, no initial synchronization starts. Additionally, Event ID 2212 and event ID 2214 are logged in event log.

Workaround

To work around this issue, resume the replication before you enable the RF. For example, in the scenario described in the Symptom section, you can follow these steps instead:

  1. You deploy DFSR on a Windows Server 2008 R2-based server.

  2. You enable Stop Replication functionality in AutoRecovery on the server. To do this, you set the StopReplicationOnAutoRecovery value to 1 under the following registry key:HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\DFSR\Parameters

  3. An unexpected shutdown occurs, or you end the dfsrs.exe process manually.

  4. You restart the DFSR service. Event 2213 is logged stating that replication is disabled and requires admin intervention.

  5. You disable the replication member in the RF in MMC.

  6. Run the dfsrdiag pollad command. Event ID 4114 is received.

  7. You resume the replication.

  8. You enable the replication member in the RF in the MMC.

  9. Run the dfsrdiag pollad command.

  10. Initial sync starts.

Note

  1. Back up the files in all replicated folders on the volume. Failure to do this may result in data loss from unexpected conflict resolution during the recovery of the replicated folders.

  2. To resume the replication for this volume, use the ResumeReplication WMI method of the DfsrVolumeConfig class. For example, from an elevated command prompt, run the following command: wmic /namespace:\\root\microsoftdfs path dfsrVolumeConfig where volumeGuid=""E18D8280-2379-11E2-A5A0-806E6F6E6963"" call ResumeReplication

More Information

For more information about the DFSR event ID 2213, go to the following Microsoft website:

2846759 DFSR event ID 2213 in Windows Server 2008 R2 or Windows Server 2012

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×