AD GPO Replication

C

Chai

Hi there,

I got 3 DC in my company network. Before that is all
working fine. Recently the file replication service is
stopped at the main DC (first DC) for a while. After I
restart the services then the problems happen.

The Group Policy I created on the first DC is not
replicated to other DCs. After I check and I find that is
due to file replication service issue.

O search the net and perform the net time command on all
DCs - now the other 2 DCs is OK already cause I change the
GP in 1 of the DC automatically it replicated to other.
However, not for the first DCs - I check the event log on
first DC after I restart the file replication service, an
error message appears as below:

Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13568
Date: 20-November-03
Time: 2:52:26 PM
User: N/A
Computer: DC1
Description:
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:\winnt\sysvol\domain"
Replica root volume is : "\\.\C:"
A Replica set hits JRNL_WRAP_ERROR when the record that
it is trying to read from the NTFS USN journal is not
found. This can occur because of one of the following
reasons.

[1] Volume "\\.\C:" has been formatted.
[2] The NTFS USN journal on volume "\\.\C:" has been
deleted.
[3] The NTFS USN journal on volume "\\.\C:" has been
truncated. Chkdsk can truncate the journal if it finds
corrupt entries at the end of the journal.
[4] File Replication Service was not running on this
computer for a long time.
[5] File Replication Service could not keep up with the
rate of Disk IO activity on "\\.\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.

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.

I follow the what the event log say - add the entry on
registry and restart the servives but still the same
error - even I restart the PC.

For other 2 DCs - I recieve the error message indicate
that the file replication cannot replicate from the first
DC to other 2 DCs.

Any ideas?

Thanks

Chai
 
M

Matjaz Ladava [MVP]

check http://support.microsoft.com/?id=292438 to see if it helps.

What you could do is to demote the troubled DC and reinstall Active
Directory trough DC promo. Maybe check you disk space on that server, and
maybe disable any AV tools you are using.
--
Regards

Matjaz Ladava, MCSE, MCSA, MCT, MVP
Microsoft MVP - Active Directory
(e-mail address removed), (e-mail address removed)
http://ladava.com

Chai said:
Hi there,

I got 3 DC in my company network. Before that is all
working fine. Recently the file replication service is
stopped at the main DC (first DC) for a while. After I
restart the services then the problems happen.

The Group Policy I created on the first DC is not
replicated to other DCs. After I check and I find that is
due to file replication service issue.

O search the net and perform the net time command on all
DCs - now the other 2 DCs is OK already cause I change the
GP in 1 of the DC automatically it replicated to other.
However, not for the first DCs - I check the event log on
first DC after I restart the file replication service, an
error message appears as below:

Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13568
Date: 20-November-03
Time: 2:52:26 PM
User: N/A
Computer: DC1
Description:
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:\winnt\sysvol\domain"
Replica root volume is : "\\.\C:"
A Replica set hits JRNL_WRAP_ERROR when the record that
it is trying to read from the NTFS USN journal is not
found. This can occur because of one of the following
reasons.

[1] Volume "\\.\C:" has been formatted.
[2] The NTFS USN journal on volume "\\.\C:" has been
deleted.
[3] The NTFS USN journal on volume "\\.\C:" has been
truncated. Chkdsk can truncate the journal if it finds
corrupt entries at the end of the journal.
[4] File Replication Service was not running on this
computer for a long time.
[5] File Replication Service could not keep up with the
rate of Disk IO activity on "\\.\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.

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.

I follow the what the event log say - add the entry on
registry and restart the servives but still the same
error - even I restart the PC.

For other 2 DCs - I recieve the error message indicate
that the file replication cannot replicate from the first
DC to other 2 DCs.

Any ideas?

Thanks

Chai
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top