DFS-R initial replication failing to complete

[mka via WinServerKB.com]

I'm replicating four remote file servers Windows 2k3 sp2 R2/Windows 2K8 (all
DC's) to a win2k8 member server.
Replication starts out fine, however it soon stops. After running a
diagnostic, I get the following errors:

This member is waiting for initial replication for replicated folder Common
and is not currently participating in replication. This delay can occur
because the member is waiting for the DFS Replication service to retrieve
replication settings from Active Directory. After the member detects that it
is part of replication group, the member will begin initial replication.

Replication will begin after initial replication is complete. If this state
does not change, see The Microsoft Web Site.

I am also get the following warning:

The DFS Replication service is stopping communication with partner xxxxx for
replication group xxxxx due to an error. The service will retry the
connection periodically.

Additional Information:
Error: 9033 (The request was cancelled by a shutdown)
Connection ID: DF48BABC-DF8C-4B6F-934E-99C6EF915E72
Replication Group ID: F3B441C7-326F-4516-99DA-8B896CE28C38

Any ideas, AD replication seems fine to the remote site as I have run a
DCDIAG and repadmin /replsum. Both passed with flying colors. Any help would
be appreciated. Thanks.

[Danny Sanders]

Try resetting the primary member.

Dfsradmin Membership Set /RGName:<replication group name>
/RFName:<replicated folder name> /MemName:<member you want to be primary>
/IsPrimary:True

For example, if you want NA-DC-01 to be primary member for the replicated
folder DATA in the replication group RG1:

Dfsradmin Membership Set /RGName:RG1 /RFName:DATA /MemName:NA-DC-01
/IsPrimary:True

Please run "Dfsrdiag Pollad" against all the members to force them to pick
up this change as soon as possible.


hth
DDS

Post by mka via WinServerKB.com
I'm replicating four remote file servers Windows 2k3 sp2 R2/Windows 2K8 (all
DC's) to a win2k8 member server.
Replication starts out fine, however it soon stops. After running a
This member is waiting for initial replication for replicated folder Common
and is not currently participating in replication. This delay can occur
because the member is waiting for the DFS Replication service to retrieve
replication settings from Active Directory. After the member detects that it
is part of replication group, the member will begin initial replication.
Replication will begin after initial replication is complete. If this state
does not change, see The Microsoft Web Site.
The DFS Replication service is stopping communication with partner xxxxx for
replication group xxxxx due to an error. The service will retry the
connection periodically.
Error: 9033 (The request was cancelled by a shutdown)
Connection ID: DF48BABC-DF8C-4B6F-934E-99C6EF915E72
Replication Group ID: F3B441C7-326F-4516-99DA-8B896CE28C38
Any ideas, AD replication seems fine to the remote site as I have run a
DCDIAG and repadmin /replsum. Both passed with flying colors. Any help would
be appreciated. Thanks.
--
Message posted via WinServerKB.com
http://www.winserverkb.com/Uwe/Forums.aspx/windows-server-dfs-frs/200907/1

[mka via WinServerKB.com]

Hi Danny,

Thx for the repsonse,

This was done already to no avail, am afraid...

Any other suggestions?

Post by Danny Sanders
Try resetting the primary member.
Dfsradmin Membership Set /RGName:<replication group name>
/RFName:<replicated folder name> /MemName:<member you want to be primary>
/IsPrimary:True
For example, if you want NA-DC-01 to be primary member for the replicated
Dfsradmin Membership Set /RGName:RG1 /RFName:DATA /MemName:NA-DC-01
/IsPrimary:True
Please run "Dfsrdiag Pollad" against all the members to force them to pick
up this change as soon as possible.
hth
DDS

Post by mka via WinServerKB.com
I'm replicating four remote file servers Windows 2k3 sp2 R2/Windows 2K8 (all

[quoted text clipped - 30 lines]

Post by mka via WinServerKB.com
would
be appreciated. Thanks.