This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(150.4, 55.00000000000001%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPW%3C/text%3E%3C/svg%3E)
Dears,
I have 2 DCs, PDC and BDC, which PDC is the primary DC. within these few months I noticed that there are error logs in Server Manager within DS server. On PDC the error code is 1202, and it says:
"The DFS Replication service failed to contact domain controller to access configuration information. Replication is stopped. The service will try again during the next configuration polling cycle, which will occur in 60 minutes. This event can be caused by TCP/IP connectivity, firewall, Active Directory Domain Services, or DNS issues.
Additional Information:
Error: 160 (One or more arguments are not correct.)"
on BDC, there are 2 errors with codes 5002 and 4612.
4612:
The DFS Replication service initialized SYSVOL at local path C:\Windows\SYSVOL\domain and is waiting to perform initial replication. The replicated folder will remain in the initial synchronization state until it has replicated with its partner PDC.xxxx.local. If the server was in the process of being promoted to a domain controller, the domain controller will not advertise and function as a domain controller until this issue is resolved. This can occur if the specified partner is also in the initial synchronization state, or if sharing violations are encountered on this server or the sync partner. If this event occurred during the migration of SYSVOL from File Replication service (FRS) to DFS Replication, changes will not replicate out until this issue is resolved. This can cause the SYSVOL folder on this server to become out of sync with other domain controllers.
5002:
The DFS Replication service encountered an error communicating with partner PDC for replication group Domain System Volume.
I got these errors every time I restarted service DFSR, so it's not a one time thing.
I've run Dcdiag /test: DFSREvent on both DCs and all get the message "Failed test DFSREvent"
I also checked the sysvol folders on both DCs, and on BDC the "scripts" folder is empty and no "policies" folder under my domain.
Could somebody help me fix this?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Ok, well to be honest there may not be anything to save here but you could try this one.
https://gist.github.com/RavuAlHemio/00e51d3ea64731be9d43b01eda18734f
--please don't forget to upvote and Accept as answer if the reply is helpful--
I'm not very familiar with windwos servers and these settings, maybe I ask if we need to add features 'DFS Replication" to my 2 DCs? I find it's not installed on them.
while they both use the same technology they perform different functions. So in short; no don't add that role.
--please don't forget to upvote and Accept as answer if the reply is helpful--
Just checking if there's any progress or updates?
--please don't forget to upvote and Accept as answer if the reply is helpful--
No luck, still the same, PDC has error 1202, and BDC has 4612 & 5002.
What else was tried?
I read some articles that they say if we're using DFSR instead of FRS, there should be a folder SYSVOL under C:\Windows, but at my 2 servers, none of them has this folder, is it OK?
if I create a user in AD, it can sync to another server, but if create a group policy in GPO management, on PDC has the new policy, BDC doesn't.
And in Group Policy Management, after click Detect Now, I can see a message with question mark in front of it, says "1 Domain controller(s) with replication in progress" which is BDC, and "inaccessible" next to the host name.
You can try a non authoritative sync
https://support.microsoft.com/en-us/help/2218556/how-to-force-an-authoritative-and-non-authoritative-synchronization-fo
or simplest solution may be to move roles to another healthy one, demote, reboot, promo it again.
--please don't forget to upvote and Accept as answer if the reply is helpful--
Thanks Patrick.
I do this on both DCs, and on PDC, after I run command "repadmin /syncall /APed", I got all messages "SyncAll terminated with no errors.", but after running command "dfsrdiag pollad", I got error message:
"[ERROR] PollDsNow method executed unsuccessfully. ReturnValue: 12 (0xc)
[ERROR] Failed to execute PollAD command Err: -2147217407 (0x80041001)"
on BDC, it seems all commands run successfully, I got all messages "SyncAll terminated with no errors.", and in DFSR log, I saw the new log ID 4114 and after running command "dfsrdiag pollad", I got "Operation Succeeded", I saw the new log ID 4614 but no 4604, and still I got error event ID 5002.
It seems maybe it's the PDC problem, could you help advise how i can fix this?
thanks again.
What's in the System and DFS Replication event logs since last boot?
In DFS Replication event log, I still got this error:
The DFS Replication service failed to contact domain controller to access configuration information. Replication is stopped. The service will try again during the next configuration polling cycle, which will occur in 60 minutes. This event can be caused by TCP/IP connectivity, firewall, Active Directory Domain Services, or DNS issues.
Additional Information:
Error: 160 (One or more arguments are not correct.)
In System, I can see anything special.
Have you tried an authoritative sync?
Yes I did it twice, and got the same error. On PDC event ID 1202 as above.
Just to be clear you tried both non authoritative then also an authoritative?
Yes both.
I read some articles that they say if we're using DFSR instead of FRS, there should be a folder SYSVOL under C:\Windows, but at my 2 servers, none of them has this folder, is it OK?
Sysvol should exist regardless or FRS / DFSR. You may need to restore from a known good backup and try again.
--please don't forget to upvote and Accept as answer if the reply is helpful--
Just checking if there's any progress or updates?
--please don't forget to upvote and Accept as answer if the reply is helpful--