DFS Replication issue with event ID 4012 (windows server 2016

Question

I have two DC windows servers 2016 one primary and additional and I replication between two servers
when creating a new group policy on the primary domain the group policy file in sysvol file was created in the additional domain And vice versa, the same. and I checked the event viewer in DFS replication and have a log with event ID 4012

( The DFS Replication service stopped replication on the folder with the following local path: D:\Windows\SYSVOL\domain. This server has been disconnected from other partners for 501 days, which is longer than the time allowed by the MaxOfflineTimeInDays 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.

Additional Information:
Error: 9061 (The replicated folder has been offline for too long.)
Replicated Folder Name: SYSVOL Share
Replicated Folder ID: 4F50CD31-0AA1-4E05-B113-AB7FDBE3751C
Replication Group Name: Domain System Volume
Replication Group ID: 6150A1BF-88D1-4A55-8A45-028CF7AFA0BF
Member ID: 995C3B0E-ED51-43D7-AC89-B56175465AF1 )

Answer 1

Since this one has tombstoned you'll need to seize roles (if necessary) take offline, do cleanup and rebuild it.
https://learn.microsoft.com/en-us/troubleshoot/windows-server/identity/transfer-or-seize-fsmo-roles-in-ad-ds

https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/deploy/ad-ds-metadata-cleanup
https://techcommunity.microsoft.com/t5/itops-talk-blog/step-by-step-manually-removing-a-domain-controller-server/ba-p/280564

I'd use dcdiag / repadmin tools to verify health correcting all errors found before starting any operations. Then stand up the new 2016, patch it fully, license it, join existing domain, add active directory domain services, promote it also [making it a GC][1] (recommended), [transfer FSMO roles over][2] (optional), transfer pdc emulator role (optional), use dcdiag / repadmin tools to again verify health, when all is good you can decommission / demote old one.

--please don't forget to upvote and Accept as answer if the reply is helpful--

Answer 2

Just my 2 cents.
In my case I did check the health of the PDC and then used the following command to resume the replication.
wmic.exe /namespace:\root\microsoftdfs path DfsrMachineConfig set MaxOfflineTimeInDays=500
In your case the value for "MaxOfflineTimeInDays" needs to be higher than 501.
If you do that and fire up the replication using repadmin, it should work for you too.

Answer 3

After I ran above command, i got ERROR: Description = Invalid namespace