DFS Replication issue with event ID 4012 (windows server 2016

Question

DFS Replication issue with event ID 4012 (windows server 2016

Ziyad Tbeni 81

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 )

Russ Rizzo 0 Reputation points

2024-05-20T16:33:53.0533333+00:00

Taking into consideration the main topic was True to say that there WERE 2 Domain Controllers where one was a 2016 Server and the NEW One is 2022. DFS was initially setup to actually migrate to the new server and once done the 2016 was decommissioned. So now there is only one DC that is a 2022 Server with DFS running for the folder shares however the SYSVOL is no longer synching because the partner was removed and thus getting same error. The old server cannot be turned up so I need to know the quickest guaranteed solution to resolve the DFSR Event ID: 4012 as this will remain a single DC w/ DFS running

Answer accepted by question author

3 additional answers

Your answer

Russ Rizzo 0 Reputation points

2024-05-20T16:33:53.0533333+00:00

Taking into consideration the main topic was True to say that there WERE 2 Domain Controllers where one was a 2016 Server and the NEW One is 2022. DFS was initially setup to actually migrate to the new server and once done the 2016 was decommissioned. So now there is only one DC that is a 2022 Server with DFS running for the folder shares however the SYSVOL is no longer synching because the partner was removed and thus getting same error. The old server cannot be turned up so I need to know the quickest guaranteed solution to resolve the DFSR Event ID: 4012 as this will remain a single DC w/ DFS running

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--

Anonymous

2022-06-03T12:50:59.247+00:00

Just checking if there's any progress or updates?

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

Answer 2

George R. Johnson 36

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.

Gary 11 Reputation points

2022-11-30T11:43:42+00:00

That easy and just two cents, thank you bro !!!!
Sachin Kumar 1 Reputation point

2023-02-15T12:26:36.9033333+00:00

We are getting some GPO ACL issue after perform above shared steps .

Could you please suggest next action for this issue.
Ian Fulcher 5 Reputation points

2023-09-19T17:10:53.96+00:00

But note it's wmic.exe /namespace:\root... i.e. \
Ian Fulcher 5 Reputation points

2023-09-19T17:12:21.1733333+00:00

It's escaping the double backspace: \root should be a double backspace
Michael Cusumano 5 Reputation points

2023-10-26T19:18:15.7333333+00:00

Thanks George! This helped me a lot!
Dwayne Smith 0 Reputation points

2025-01-23T01:16:24.31+00:00

I dropped into an environment and encountered this error, however, the disconnected days is 2774 and this is the primary DC. If I use this command to increase MaxOfflineTimeInDays=3000, will the replication process do a two-way check of the GPT version number and only update those that need to be updated? In my case the primary DC is 2012 and the secondaries are 2012 and 2008 with a newly added 2022 that should be taking over and the other decommissioned.

Answer 3

Just to clear up George answer:

like this:

wmic.exe /namespace:\\root\microsoftdfs path DfsrMachineConfig set MaxOfflineTimeInDays=500

NOT LIKE THIS:

wmic.exe /namespace:\root\microsoftdfs path DfsrMachineConfig set MaxOfflineTimeInDays=500

Validate the status after like this:

For /f %i IN ('dsquery server -o rdn') do @echo %i && @wmic /node:"%i" /namespace:\\root\microsoftdfs path dfsrreplicatedfolderinfo WHERE replicatedfoldername='SYSVOL share' get replicationgroupname,replicatedfoldername,state

Reference here for this last command:

https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/troubleshoot-missing-sysvol-and-netlogon-shares?source=recommendations

Answer 4

Satya INV 5

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

Jonathan Stegner 0 Reputation points

2023-09-08T21:12:42.9633333+00:00

its just missing a \

wmic.exe /namespace:\\root\microsoftdfs path DfsrMachineConfig set MaxOfflineTimeInDays=500
Satya INV 5 Reputation points

2023-09-14T10:29:41.75+00:00

I ran below command as it is " a \ wmic.exe /namespace:\root\microsoftdfs path DfsMachineConfig get MaxofflineTimeInDays set MaxofflineTimeDays=700 "

Got error: 'a' is not recognized as an internal or external command, operable program or batch file.
Steve Hathaway 21 Reputation points

2023-09-26T03:18:50.1833333+00:00

He means an extra \ before root

wmic.exe /namespace:\<extra>root\microsoftdfs path DfsrMachineConfig set MaxOfflineTimeInDays=700

This editor appears to suppress double backslash
Karsten Palmvig (KAVM) 0 Reputation points

2023-09-26T08:39:09.19+00:00

Try double backslash before "root": wmic.exe /namespace:\root\microsoftdfs path DfsrMachineConfig set MaxOfflineTimeInDays=500
Gorvam Jeet Pal 15 Reputation points

2024-01-20T18:18:20.3633333+00:00

wmic.exe /namespace:\root\microsoftdfs path DfsrMachineConfig set MaxOfflineTimeInDays=500
this command does not work at all, invalid namesaopce all the time i ran it.
Ben Blissett 25 Reputation points

2024-03-07T14:33:31.3733333+00:00

The double backslash before root was the answer. Cheers
Alex Racine 10 Reputation points

2024-08-02T21:45:50.3833333+00:00

like this:

wmic.exe /namespace:\\root\microsoftdfs path DfsrMachineConfig set MaxOfflineTimeInDays=500

NOT LIKE THIS:

wmic.exe /namespace:\root\microsoftdfs path DfsrMachineConfig set MaxOfflineTimeInDays=500

Validate the status after like this:

For /f %i IN ('dsquery server -o rdn') do @echo %i && @wmic /node:"%i" /namespace:\\root\microsoftdfs path dfsrreplicatedfolderinfo WHERE replicatedfoldername='SYSVOL share' get replicationgroupname,replicatedfoldername,state

Reference here:

https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/troubleshoot-missing-sysvol-and-netlogon-shares?source=recommendations

Share via

DFS Replication issue with event ID 4012 (windows server 2016

3 additional answers

Your answer