Journal wrap error during part 1 swing migration

25 Dec

Windows Server 2003: Clear the Journal Wrap Error in File Replication Service

This will help to resolve the journal wrap error on Windows servers in most situations. Additional details are available in Microsoft KB article 292438 (“Troubleshooting Journal_Wrap Errors on Sysvol and DFS Replica Sets”)

Preliminary:
> Make a backup copy of all folders and files under c:\windows\sysvol.
> Make a backup copy of all group policy objects by using the Group Policy Editor.
> Make sure that you know how to restore these items if needed!

Start RegEdit.

Move to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NTFRS\Parameters

Create the following DWORD values:
Ntfs Journal Size in MB” (maximum decimal value = 128)
Enable Journal Wrap Automatic Restore” (set value = 1)

After you create the entries and close RegEdit, restart the NTFRS service.

Note that the folders/files that you copied earlier may now be missing. Restore any missing folders/files from the backup copies that you previous made in the Preliminary section of this TechTip.

Is the c:\windows\sysvol\sysvol\<domain>\scripts folder still shared as Netlogon? If not, then search the Registry for all instances of SysVolReady and change the value from 0 to 1.  Restart the NTFRS service.

After anywhere from ten minutes to eight hours (be patient), you should see an indication of successful replication with no more journal wrap errors in the event logs.

Go into the Group Policy Editor and click each group policy. You may receive a warning about inconsistent permissions. Click OK to correct the inconsistency.