Having some problems on my DC's FRS logs that I can't sort out.
This issue appears to go back to February but does not appear to be adversely effecting my domain to any extent that I can discover. However, I do want to resolve these errors just in case there is an underlying problem.
This is the error I receive on my Schema Master, which is my first DC in my domain:
****************************************************************************************************************************************************************************************
Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13568
Date: 4/30/2006
Time: 8:13:17 PM
User: N/A
Computer: Servername1
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.
****************************************************************************************************************************************************************************************
On my other two DC's in my domain I receive this error:
Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13508
Date: 4/30/2006
Time: 7:37:35 PM
User: N/A
Computer: Servername2
Description:
The File Replication Service is having trouble enabling replication from Servername1 to Servername2 for c:\winnt\sysvol\domain using the DNS name lymanfs.sewlyman.com. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name servername1.com from this computer.
[2] FRS is not running on servername1.com.
[3] The topology information in the Active Directory for this replica has not yet replicated to all the Domain Controllers.
This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.
Data:
0000: d5 04 00 00 Õ...
****************************************************************************************************************************************************************************************
I am preparing to introduce Windows 2003 Servers into my domains and replace my existing DC's with new 2003 Servers, so I want to resolve any abnormalities prior to introducing new systems.
I have confirmed that replication of the indicated sysvol folder is not working, as I placed text files in each of the DC's folder and they did not replicate.
There are several duplicate folder names in the sysvol folder with extended names, so I'm sure something is messed up, but I'm not sure how to proceed.
I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.
This issue appears to go back to February but does not appear to be adversely effecting my domain to any extent that I can discover. However, I do want to resolve these errors just in case there is an underlying problem.
This is the error I receive on my Schema Master, which is my first DC in my domain:
****************************************************************************************************************************************************************************************
Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13568
Date: 4/30/2006
Time: 8:13:17 PM
User: N/A
Computer: Servername1
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.
****************************************************************************************************************************************************************************************
On my other two DC's in my domain I receive this error:
Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13508
Date: 4/30/2006
Time: 7:37:35 PM
User: N/A
Computer: Servername2
Description:
The File Replication Service is having trouble enabling replication from Servername1 to Servername2 for c:\winnt\sysvol\domain using the DNS name lymanfs.sewlyman.com. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name servername1.com from this computer.
[2] FRS is not running on servername1.com.
[3] The topology information in the Active Directory for this replica has not yet replicated to all the Domain Controllers.
This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.
Data:
0000: d5 04 00 00 Õ...
****************************************************************************************************************************************************************************************
I am preparing to introduce Windows 2003 Servers into my domains and replace my existing DC's with new 2003 Servers, so I want to resolve any abnormalities prior to introducing new systems.
I have confirmed that replication of the indicated sysvol folder is not working, as I placed text files in each of the DC's folder and they did not replicate.
There are several duplicate folder names in the sysvol folder with extended names, so I'm sure something is messed up, but I'm not sure how to proceed.
I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.