Error message and event log warning 6804 when you complete a DFS Replication SYSVOL migration by using the Dfsrmig.exe tool on a domain controller that is running Windows Server 2008 R2: "No connections exist for Domain System Volume"
While performing a Distributed File System Replication (DFSR) SYSVOL migration by using the Dfsrmig.exe tool on domain controllers that are running Windows Server 2008 R2, the following warning is logged in the DFS Replication event log:
Log Name: DFS Replication Source: DFSR Date: date Event ID: 6804 Task Category: None Level: Warning Keywords: Classic User: N/A Computer: computer name Description: The DFS Replication service has detected that no connections are configured for replication group Domain System Volume. No data is being replicated for this replication group.
Additional Information: Replication Group ID: 07003670-2807-4D5B-89BD-FFF3DA94F2C6 Member ID: F2679227-2489-4A6D-A92C-2050E4ED4ACD
Additionally, when creating a DFSR Diagnostic Health report, the following error is logged:
No connections exist for Domain System Volume.
Affected replicated folders: All replicated folders on this server. Description: The DFS Replication service has detected that there are no connections configured for replication group Domain System Volume. No data for this replication group is being replicated to or from this server. Event ID: 6804 Last occurred: date Suggested action: To resume replication, create connections using the DFS Management snap-in or the Dfsradmin.exe command-line tool.
A code defect in DFS Replication SYSVOL migration prevents an anti-event 6806 from being written. A 6804 event can be expected because of Active Directory replication timing issues. However, a 6806 event is supposed to be written when the topology fully forms.
You can safely ignore the Warning event that has event ID 6804 as long as migration to the Prepared state (state "1") works and as long as the data replicates through DFS Replication without any issues. The warning is expected and spurious in this scenario.
The DFS Replication Diagnostic Health Report error can also be ignored. After you restart the DFS Replication service on any affected computers, the error no longer appears in health reports.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about SYSVOL Replication Migration, visit the following Microsoft Web site: