General discussion

Locked

Group Policy replication problems

By campbelltaylor ·
Around three months ago we updated a Windows 2000 Server (running as an AD DC with Exchange on it) to Service Pack 4. We now cannot transfer GPO's to this DC. The Sysvol Policy folder does not update.

We have looked in the Replication log and there is an error regarding a Jrnl Wrap error Event id 13568 Source NTFRS. We think this may be something to do with lack of space on the boot drive - we currently only have 350MBs spare (unfortunately we cannot make much more space). We have looked at Microsoft KB Article 837325 which says about deleting and recreating the journal and changing the reserved space to 128 MB. The article recommend that "If the FRS has a Sysvol share on the partition, move the share to another partition."

At the present the sysvol is on the same boot partition - is it necessary we move the Syvol tree as recommended or can we use another fix that does not require moving the Sysvol? What is purpose in moving the Sysvol? Moving the Sysvol seems to be an involved task as outlined in KB article 842162.

Are we on the right track? Or do you have any other suggestions/fixes?

Cheers for your time

This conversation is currently closed to new comments.

4 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by curlergirl In reply to Group Policy replication ...

The only thing I can take credit for on this answer is that I have paid for and use a subscription to EventID.net. This fix came directly from that source, so I hope it helps you:

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.

Expand HKEY_LOCAL_MACHINE.
Click down the key path:
"System\CurrentControlSet\Services\NtFrs\Parameters"
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.

Hope this helps!

Collapse -

by campbelltaylor In reply to

Thanks for that answer - We won't have a chance to try it for a few days but it certainly looks feasible and even if it isn't the solution we end up using at least its given us a second choice to solving our problem

Collapse -

by campbelltaylor In reply to Group Policy replication ...

This question was closed by the author

Collapse -

by campbelltaylor In reply to Group Policy replication ...

In the end we made space on the OS partition (C:) so that there was over 512MB and then followed your tip from EventID to make the registry change

Expand HKEY_LOCAL_MACHINE.
Click down the key path:
"System\CurrentControlSet\Services\NtFrs\Parameters"
Double click on the value name
"Enable Journal Wrap Automatic Restore"
and update the value.

Thnaks for your help - we now have policies replicating

Back to Networks Forum
4 total posts (Page 1 of 1)  

Related Discussions

Related Forums