File Replication Service is taking a long time to scan the system volumn

There were multuple event ID 13568 errors in the application event log.  I performed the recommendation to set the "Enable Journal Wrap Automatic Restore" registry setting to recover.  Now I am getting event id 13566 stating that the File Replication Service is scanning the data in the system volume.  This has been going on for over 2 hours.

This is a sbs 2003 sp2 server.  There are not any other domain servers.  I have checked repeatedly for the sysvol share but it is not available.

Thanks for the help

Bret

July 9th, 2010 3:56pm

Refer to http://social.technet.microsoft.com/Forums/en-US/winserverMigration/thread/208fb7ec-11e5-4b8f-944b-58badeb8115c

Note that this includes (besides suggestions how this problem can be resolved) links to SBS forum - use that in regard to SBS specific issues

hth
Marcin

  • Marked as answer by Bruce-Liu Tuesday, July 13, 2010 6:36 AM
Free Windows Admin Tool Kit Click here and download it now
July 9th, 2010 4:15pm

Using the BurFlags registry key to reinitialize File Replication Service replica sets

://support.microsoft.com/kb/290762

take care when you set registry value for  burflags=D4 then all sysvol content on this domain controller will be deleted , so you must copy it before change registry value for burflags

  • Proposed as answer by Minammx Friday, December 26, 2014 7:19 PM
  • Edited by Minammx Friday, December 26, 2014 9:52 PM
December 26th, 2014 7:08pm

i got the same event id 13566 stating that the File Replication Service is scanning the data in the system volume when i try to restore the domain controller in the virtual lab (for testing ) by using windows bare metal recovery and the sysvol share didn't created and the domain controller didn't work his function

How to rebuild the SYSVOL tree and its content in a domain 

support.microsoft.com/kb/315457

1-On the reference domain controller, build a good set of policies and scripts, and then put them in a temporary folder outside the SYSVOL replica set folders on the FRS reference domain controller

by other meaning

Move all files and folders that should reside in the SYSVOL tree to a temporary folder on the reference domain controller. The temporary folder should be located on the same partition the SYSVOL tree is located.

2-Restart the FRS on the reference domain controller with the D4 registry entry set.

To configure the SYSVOL replica set to be authoritative, follow these steps:
  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the BurFlags entry under the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Cumulative Replica Sets\<var>GUID</var> <var>GUID</var> is the GUID of the domain system volume replica set that is shown in the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Replica Sets\<var>GUID</var>
  3. Right-click  BurFlags, and then click  Modify.
  4. Type D4 in the Value Data field (HexaDecimal), and then click OK.
3-On the reference domain controller, move the policies and scripts folders and the folder contents from the temporary location that you used in step 1 to the FRS replica set root folder. For the SYSVOL folder, the default location for the replica set root is the following folder: C:\WINNT\SYSVOL\domain




  • Edited by Minammx Friday, December 26, 2014 9:49 PM
  • Proposed as answer by Minammx Friday, December 26, 2014 9:49 PM
Free Windows Admin Tool Kit Click here and download it now
December 26th, 2014 9:14pm

You!  You are beautiful, and you are brilliant and don't ever let anyone say otherwise!

I'm resuscitating a years-neglected domain without any valid replication partners and because of you I might actually be able to go to sleep sometime in the next 6 hours!

Worked perfectly, thanks!

August 22nd, 2015 2:39am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics