Skip to main content

DFSR - eventid 4312 - replication just won't work

This warning isn't documented that well on the googles, so here's some google fodder:

  • You are trying to set up replication for a DFS folder (no existing replication)
  • Source server is 2008R2, 'branch office' server is 2012R2 (I'm moving all our infra to 2012R2)
  • You have no issues getting replication configured
  • You see the DFSR folders get created on the other end, but nothing stages
  • Finally you get EventID 4312:

The DFS Replication service failed to get folder information when walking the file system on a journal wrap or loss recovery due to repeated sharing violations encountered on a folder. The service cannot replicate the folder and files in that folder until the sharing violation is resolved. 
Additional Information: 
Folder: F:\Users$\\Desktop\Random Folder Name\ 
Replicated Folder Root: F:\Users$ 
File ID: {00000000-0000-0000-0000-000000000000}-v0 
Replicated Folder Name: Users 
Replicated Folder ID: 33F0449D-5E67-4DA1-99AC-681B5BACC7E5 
Replication Group Name:\dfs\users 
Replication Group ID: E51C7DB4-0DEE-4D32-A95A-F850207E1C83 
Member ID: 9FCE727C-96CC-445F-A500-E123AFC2632B

I made several incorrect assumptions here:
  1. That DFSR would continue walking the rest of the users folder
  2. That this was just a 'hey, heads-up dude' kind of message
  3. That replication was working at all
After deleting/recreating the RG a few times, ended up moving on and adding the rest of the folders - still nothing replicating!!  Other things I tried:
  1. Restarting the server
  2. Changing the share names
  3. Triple checking ADSI object permissions, NTFS permissions, etc
I ended up creating some dummy DFS/DFSR test folders, and this kicked off replication for some reason - everything else started replicating no problem.

Except for users.  So found more options for nuking DFSR!
  1. Stop DFSR on the source server
  2. On the drive in question, nuke the system volume information\DFSR folder (have to give yourself rights) rd DFSR /s /q
  3. Start DFSR again
The other way is to:
  1. Delete the RG (replication group)
  2. Stop DFSR on both servers
  3. Go into the target folders, from the cmd prompt nuke the dfsrprivate folders
  4. Nuke the system volume info\dfsr dirs on both servers
  5. Start DFSR on both servers
  6. Recreate the RG
Finally, to speed up this process:
  1. On the source server: dfsrdiag pollad
  2. On a DC of choosing: repadmin /syncall /d /e /P dc=domain,dc=com
  3. On the target server: dfsrdiag pollad
  4. On the source server: dfsrdiag pollad (not sure if needed, but hey)
Otherwise you're sitting waiting on site replication - 15 minutes.  (tangent: why is 15m the lowest it can go?)

Anywho still nothing at this point, and I was still seeing that warning - so I nuked that folder (after backing it up), then did a full DFSR nuke/replace.  Works now!

Also came across this handy DFSR design doc:


  1. I would further note that a lack of pre-seeding was also causing me problems. After following the MS doc (, I'm now seeing progress using this command: dfsrdiag backlog (w. options)


Post a Comment

Popular posts from this blog

Fixing duplicate SPNs (service principal name)

This is a pretty handy thing to know:

SPNs are used when a specific service/daemon uses Kerberos to authenticate against AD. They map a specific service, port, and object together with this convention: class/host:port/name

If you use a computer object to auth (such as local service):

If you use a user object to auth (such as a service account, or admin account):

Why do we care about duplicate SPNs? If you have two entries trying to auth using the same Kerberos ticket (I think that's right...), they will conflict, and cause errors and service failures.

To check for duplicate SPNs:
The command "setspn.exe -X

C:\Windows\system32>setspn -X
Processing entry 7
MSSQLSvc/ is registered on these accounts:
CN=SQL Admin,OU=service accounts,OU=resources,DC=company,DC=local

found 1 groups of duplicate SPNs. (truncated/sanitized)

Note that y…

Logstash to Nagios - alerting based on Windows Event ID

This took way longer than it should have to get here's a config and brain dump...

You want to have a central place to analyze Windows Event/IIS/local application logs, alert off specific events, alert off specific situations.  You don't have the budget for a boxed solution.  You want pretty graphs.  You don't particularly care about individual server states.  (see rationale below - although you certainly have all the tools here to care, I haven't provided that configuration)

ELK stack, OMD, NXlog agent, and Rsyslog.  The premise here is as follows:

Event generated on server into EventLogNXlog ships to Logstash inputLogstash filter adds fields and tags to specified eventsLogstash output sends to a passive Nagios service via the Nagios NSCA outputThe passive service on Nagios (Check_MK c/o OMD) does its thing w. alerting
Open Monitoring Distribution, but the real point here is Check_MK (IIRC Icinga uses this...).  It makes Nagios easy to use and main…