Solved

How do I resolve Event ID 4012 - DFSR Replication Service Stopped on SysVol - Server 2012 Essentials R2

Posted on 2015-01-08
5
3,218 Views
Last Modified: 2015-06-23
We're getting event ID 4012 logged: which states, 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 250 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.


What I don't get is why we're seeing this in a one server environment. There's only the one DC, so why does anything need to replicate?

I'm also not sure how to resolve ...since all of the articles I've read on the topic relate to servers with multiple DCs.

Need some good advice.

Thanks...
0
Comment
Question by:philodendrin
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
5 Comments
 
LVL 7

Expert Comment

by:Deadman
ID: 40539573
This issue already raised question. check this link to solve your problem

http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Windows_Server_2012/Q_28353972.html
0
 

Author Comment

by:philodendrin
ID: 40539991
Different circumstance... read that some time ago. Why would I demote and promote anything in a single server environment. Too risky, Those are not instructions for a SBS/Essentials environment. Different animal.
0
 
LVL 7

Expert Comment

by:Deadman
ID: 40540068
First make sure you had a backup of the SysVol folder, I ran the following:

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

Wait few minutes and check if the event ID 4002 on DC. IF Yes go to next step

Change the HKLM\System\CurrentControlSet\Services\DFSR\Parameters\StopReplicationOnAutoRecovery registry key to a DWORD value of 0 (or delete it).

In command Prompt

wmic /namespace:\\root\microsoftdfs path dfsrmachineconfig set StopReplicationOnAutoRecovery=FALSE
0
 

Accepted Solution

by:
philodendrin earned 0 total points
ID: 40837516
Issue inexplicably just went away on its own without intervention.
0
 

Author Closing Comment

by:philodendrin
ID: 40845988
Issue inexplicably just went away on its own without intervention.
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The following article is comprised of the pearls we have garnered deploying virtualization solutions since Virtual Server 2005 and subsequent 2008 RTM+ Hyper-V in standalone and clustered environments.
Here's a look at newsworthy articles and community happenings during the last month.
In this Micro Tutorial viewers will learn how to use Windows Server Backup to create full image of their system. Tutorial shows how to install Windows Server Backup Feature on Windows 2012R2 and how to configure scheduled Bare Metal Recovery backup.…
In this Micro Tutorial viewers will learn how to restore their server from Bare Metal Backup image created with Windows Server Backup feature. As an example Windows 2012R2 is used.

691 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question