Log Name: DFS Replication
Date: 1/1/2010 3:37:14 PM
Event ID: 4012
Task Category: None
The DFS Replication service stopped replication on the replicated folder at local path c:\rf1. It has been disconnected from other partners for 76 days, which is longer than the MaxOfflineTimeInDays parameter . Because of this, DFS Replication considers this data to be stale, and will replace it with data from other members of the replication group during the next replication. DFS Replication will move the stale files to the local Conflict folder. No user action is required.
Error: 9061 (The replicated folder has been offline for too long.)
Replicated Folder Name: rf1
Replicated Folder ID: 5856C18F-CA72-4D2D-9D89-4CC1D8042D86
Replication Group Name: rg1
Replication Group ID: BC5976EF-997E-4149-819D-57193F21EC76
Member ID: FAEC4B17-E81F-4036-AAD9-78AA46814606
wmic.exe /namespace:\\root\microsoftdfs path DfsrReplicatedFolderInfo get ReplicationGroupName,ReplicatedFolderName,State
ReplicatedFolderName ReplicationGroupName State
rf1 rg1 5
1. Start DFSMGMT.MSC on the affected server.
2. On any affected replication groups this server is a member of, select the computer on the Membership tab and "Disable" it.
3. Accept the warning prompt.
4. If the reason for replication never occurring was the schedule being set to "no replication" on the RG or RF, or no bi-directional connections being place between servers, fix that situation now.
5. Force AD Replication and verify it has converged.
6. On the affected server, run:
7. Wait for the 4008 and 4114 events being written to the DFSR event log to confirm that the replicated folder(s) are no longer being replicated.
8. In DFSMGMT.MSC , "Enable" the replication again on the affected replicated folders for that server.
9. Force AD replication and POLLAD again.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.