Discussion:
DFS Replication Failing - Event 4312 Source DFSR
(too old to reply)
Steve
2009-09-08 19:31:17 UTC
Permalink
Hi, I am receiving an Event ID 4312 (Source DFSR) Warning on our Server
(2008 Standard) that I believe is causing DFS Replication to fail. The
initial replication has never ran.

"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: D:\Users\RV\4210\

Replicated Folder Root: D:\Users

File ID: {00000000-0000-0000-0000-000000000000}-v0

Replicated Folder Name: Users

Replicated Folder ID: FEA37A2C-E042-4970-ABE2-47D3A1E348BD

Replication Group Name: Server1 to Server2 (Users)

Replication Group ID: 0606CF1C-1D5D-4A06-B3E5-91E52C6B4754

Member ID: 8AA9F550-CC51-410C-8624-3D5FA6B79AF4

Based on the time that the message is generated, it only seems to appear
when the files are being backed up at night. The nightly backups are good.
Other than that the DFS Replication Log is clean.

Just wondering if anybody had any other thoughts on how to go about
resolving the issue.

Thank you!

Steve
Steve
2009-09-11 23:22:10 UTC
Permalink
Responding to my own post in case anybody comes across it in the future.

Initially we were replicating data using a 3rd party utility. Even though it
was a scheduled task to run after hours, it created locks on several files.
Because of the files being locked, the initial replication never took place.
Post by Steve
Hi, I am receiving an Event ID 4312 (Source DFSR) Warning on our Server
(2008 Standard) that I believe is causing DFS Replication to fail. The
initial replication has never ran.
"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."
Folder: D:\Users\RV\4210\
Replicated Folder Root: D:\Users
File ID: {00000000-0000-0000-0000-000000000000}-v0
Replicated Folder Name: Users
Replicated Folder ID: FEA37A2C-E042-4970-ABE2-47D3A1E348BD
Replication Group Name: Server1 to Server2 (Users)
Replication Group ID: 0606CF1C-1D5D-4A06-B3E5-91E52C6B4754
Member ID: 8AA9F550-CC51-410C-8624-3D5FA6B79AF4
Based on the time that the message is generated, it only seems to appear
when the files are being backed up at night. The nightly backups are good.
Other than that the DFS Replication Log is clean.
Just wondering if anybody had any other thoughts on how to go about
resolving the issue.
Thank you!
Steve
IT Staff
2009-09-15 05:19:51 UTC
Permalink
which 3rd party utility do u use to replicate files ?

You shld let DFS do its own replication
Post by Steve
Responding to my own post in case anybody comes across it in the future.
Initially we were replicating data using a 3rd party utility. Even though
it was a scheduled task to run after hours, it created locks on several
files. Because of the files being locked, the initial replication never
took place.
Steve
2009-09-15 16:13:27 UTC
Permalink
We were initially using Karen's Replicator.
Post by IT Staff
which 3rd party utility do u use to replicate files ?
You shld let DFS do its own replication
Post by Steve
Responding to my own post in case anybody comes across it in the future.
Initially we were replicating data using a 3rd party utility. Even though
it was a scheduled task to run after hours, it created locks on several
files. Because of the files being locked, the initial replication never
took place.
Continue reading on narkive:
Loading...