• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 203
  • Last Modified:

File replication error - fix it or forget it??

Started getting the following error 2 months ago in the event viewer:

File replication Service error 13568.  Sysvol share is in JRNL_WRAP_ERROR.  I found some info at the following site:
I did not understand much of what I read there, but it did appear to me that the FRS is only relevant when replicating to other domain servers.  Since we only have 1 server, which is the domain controller, is it really necessary to fix this "problem".  Or can I just leave it.  Could this have some unforseen negative consequences??

  • 4
  • 4
1 Solution
The journal is a file of changes that needs to be applied to sysvol.  You should reinitialize even though you only have 1 dc.  The event will keep your dc from sharing out sysvol on a reboot, which will affect your network, sooner or later.

Take a look at support.microsoft.com/kb/290762.  Its a fairly simple procedure.  Takes about 2 minutes.
Hope you haven't done this yet.  It just hit me that you only have 1 dc.  The procedure above will clear sysvol and restore it from another dc.  Sorry, its early.  

Do you have a backup of your system state?  If you do then you may want to restore the system state to get rid of the journal wrap condition.  If not use the procedure in the event to try and alleviate.
Alistair7Author Commented:
Thanks ocon for the tips.

No I don't have a system state backup. I only have an image of the whole server HD that is 4 months old which I don't want to use because of its age.

Just to satisfy my own curiousity, I looked at the server to see if SYSVOL had vanished, but it was still there and I had no trouble accessing it from a client.  Does that tell you something unexpected?

The following is a copy of some of the event advice.  Is this what you suggest I do? I don't particularly like to modify the registry.  But if unavoidable I will:

The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.
 Replica set name is    : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
 Replica root path is   : "c:\windows\sysvol\domain"
 Replica root volume is : "\\.\C:"
 Setting the "Enable Journal Wrap Automatic Restore" registry parameter to 1 will cause the following recovery steps to be taken to automatically recover from this error state.
 [1] At the first poll, which will occur in 5 minutes, this computer will be deleted from the replica set. If you do not want to wait 5 minutes, then run "net stop ntfrs" followed by "net start ntfrs" to restart the File Replication Service.
 [2] At the poll following the deletion this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set.
WARNING: During the recovery process data in the replica tree may be unavailable. You should reset the registry parameter described above to 0 to prevent automatic recovery from making the data unexpectedly unavailable if this error condition occurs again.
To change this registry parameter, run regedit.
Click on Start, Run and type regedit.
Click down the key path:
Double click on the value name
   "Enable Journal Wrap Automatic Restore"
and update the value.
If the value name is not present you may add it with the New->DWORD Value function under the Edit Menu item. Type the value name exactly as shown above.

I have no idea what is meant with "full tree sync for the replica set" Where is this replica set when I only have 1 DC?

Perhaps it's not necessary to understand everything.  But I just want to confirm with you the above procedure before I do it.
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

Alistair7Author Commented:
By the way, if do the above, will I lose any of my profile folders under SYSVOL\domain\scripts? (In addition to Default User I also have 3 other profile folders saved there which I simply rename to "Default User" when required.)
YesI think that you might lose everything under sysvol.  Get a system state backup.  
Can you promote another server to a dc?  If you can then you can see if FRS replicates successfully to it.  The event 13516 will be listed in the FRS event log, if all goes well.

If you can't then a current backup of the system state will enable you to recover if you find that you have to reload some time in the future.

Since there is only one dc in your domain, I would leave the error alone, but have a backup of everything in the event that you have to do something that might make sysvol inaccessible.  
Alistair7Author Commented:
I have no other servers, only this 1 which is the DC.

Since SYSVOL still appears to be available and functioning, I don't understand what has broken down or what to look out for, or what might happen.....
As stated before, the journal is a list of changes to be added to sysvol.  For some reason the journal file has reached its maximum size (I forget the default size).  Therefore any subsequent entries will overwrite ones that haven't been commited to sysvol.  I have no idea why this would happen in your environment.  I generally see this in a multi-domain controller environment where there has been on-going connectivity issues.
Alistair7Author Commented:
Thanks so much ocon.  Very helpful and informative.

I ended up going back to an image 9 months old, and building it up from there.
Fortunately there was not to much work, and the system has been working fine since. (1 month). I have started taking system state backups now.

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!

  • 4
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now