In a single domain controller environment (think small shop!), if you encounter this error message and you follow the prescribed steps (the event log says to create a registry setting "Enable Journal Wrap Automatic Restore" to 1, however this will actually cause some damage because there is no other domain controller on the network to download a copy of the sysvol from. Ouch! Now no one can logon to the network. Panic!

The fix is to perform a non-authoritative restore of FRS using these steps:

1. Click Start, and then click Run.
2. In the Open box, type cmd and then press ENTER.
3. In the Command box, type net stop ntfrs.

(make a backup copy of the contents of the Pre-existing folder if it exists, then copy those to the parent folder)
4. Click Start, and then click Run.
5. In the Open box, type regedit and then press ENTER.
6. Locate the following subkey in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\NtFrs\Parameters\Backup/Restore\Process at Startup
7. In the right pane, double-click BurFlags.
8. In the Edit DWORD Value dialog box, type D2 and then click OK.
9. Quit Registry Editor, and then switch to the Command box.
10. In the Command box, type net start ntfrs.
11. Quit the Command box.

Within a minute or two, you should see event ID 13516 post in the event viewer:

“The File Replication Service is no longer preventing the computer (computer name) from becoming a domain controller. The system volume has been successfully initialized and the Netlogon service has been notified that the system volume is now ready to be shared as SYSVOL.
Type "net share" to check for the SYSVOL share.”

Then users should be able to logon to the network. Now get out there and add a 2nd domain controller so you can avoid this problem! =)

See also

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

 

 

Warranty/Disclaimer: There is no warranty expressed or implied in this blog. This is for educational purposes only and if you destroy your AD server, that is your own responsibility =)