Dfs replication error 4012

Question

Server 2019 has recorded 9340 instances of this error.

Here are the details

The DFS Replication service stopped replication on the folder with the following local path: C:\Windows \SYSVOL\domain. This server has been disconnected from other partners for 1156 days, which is longer than the time allowed by the MaxOffline TimeInDays parameter (60). DFS Replication considers the data in this folder to be stale, and this server will not replicate the folder until this error is corrected.

To resume replication of this folder, use the DFS Management snap-in to remove this server from the replication group, and then add it back to the group. This causes the server to perform an initial synchronization task, which replaces the stale data with fresh data from other members of the replication group.

Note: Haven't used the virtual server created years ago.

Note 2: info on VSS

Warning 8229

* * *

A VSS writer has rejected an event with error 0x800423f4, The writer experienced a non-transient error. If the back the error is likely to reoccur.

Changes that the writer made to the writer components while handling the event will not be available to the requested event log for related events from the application hosting the VSS writer.

* * *

So....

Can I remove the role to stop these errors,?

Answer 1

Hello sdtechguy,

Thank you for posting on the Microsoft Community Forums.

Could you please confirm the number of domain controllers in your current AD environment?

How many of these domain controllers are encountering the 4012 error message?

1. Please verify the status of AD replication on the domain controllers. Run the following commands on the Primary Domain Controller (PDC):

repadmin /showrepl > C:\rep1.txt

repadmin /replsum > C:\rep2.txt

repadmin /showrepl * /csv > C:\repsum.csv

2. Backup the SYSVOL folder on each domain controller.
3. Is the problematic domain controller not the Primary Domain Controller (PDC)? If indeed it's not the PDC, and if the SYSVOL on this problematic domain controller hasn't replicated with SYSVOL on other domain controllers, and if there are no issues with AD replication across the entire AD environment, you can perform a non-authoritative restore on this problematic domain controller. Force synchronization for Distributed File System Replication (DFSR) replicated sysvol replication - Windows Server | Microsoft Learn
4. Alternatively, you can demote and remove the problematic server from the domain. Demoting Domain Controllers and Domains (Level 200) | Microsoft Learn

Best regards

Neuvi Jiang

============================================

If the answer is helpful, please click "Accept Answer" and vote for it.