I have a Domain Controller Windows 2000 server standard, it's the only
one DC of my domain (it's serving about 20 PCs).
I have 2 errors on this DC, and with this replication errors I can't
add a second DC 2003 that I planned to do.
I've already found a lot of material searching on google (i.e.:
eventid.net, MS KB, etc.) but really I don't know how to fix them now
(there are too much solutions available), I've a mess in my mind.
Please could someone help me ?
Here the 2 errors:
The first one:
-------------------------------------
DCDIAG / test:frssysvol results:
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Nome-predefinito-primo-sito\SERVERNT
Starting test: Connectivity
......................... SERVERNT passed test Connectivity
Doing primary tests
Testing server: Nome-predefinito-primo-sito\SERVERNT
Starting test: frssysvol
Error: No record of File Replication System, SYSVOL started.
The Active Directory may be prevented from starting.
......................... SERVERNT passed test frssysvol
Running enterprise tests on : azienda.locale
-------------------------------------
The second one:
-------------------------------------
Event ID 13568
Source NtFrs
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.
-------------------------------------
Thanks in advance for the help.
Bye, Rosgiof.
Did you follow "Troubleshooting FRS Event 13568" in:
http://technet.microsoft.com/en-us/library/bb727056.aspx#EFAA
Are SP4 and all latest patches installed on the DC?
Also see:
http://support.microsoft.com/kb/315457/en-us
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
Hello, thank you very much for your kind answer.
I'll follow the two articles and then will post here the result.
Thanks again, bye.
Rosgiof.