FRS SYSVOL error on lone DC

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello:

I am hoping that somebody might point me in the right direction. Despite
the many issues similar, I haven't found a good answer yet.
BACKGROUND: A while back my company had two DCs going, but then one was
decommissioned due to motherboard failure. I was able to seize control of
the primary functions. Now however, I was working with group policy
assignments through AD and found that my WindowsXP clients weren't being
updated whereas the Windows2K clients were. I suspect this has something to
do with the previous replication that went on between the two DCs and how it
isn't now. Now there is a only one DC and the dcdiag results showing error
are below.

The errors I receive relate to JRNL_WRAP_ERROR. I have tried the
JRNL_WRAP_ERROR registry mod with no luck.

Any offerings of assistance???!?!?! I will be happy to provide any
additional information as requested.

Thanks! - KES

DC Diagnosis
Starting test: frssysvol
Error: No record of File Replication System, SYSVOL started.
The Active Directory may be prevented from starting.
......................... PULSAR passed test frssysvol
Starting test: FsmoCheck
......................... paragonsdc.com passed test FsmoCheck
 
I assume you tried setting the Burflags to D2? That's a non-authorative
restore -no good for a single DC environment. You'll need to restore the
SYSVOL from a previous, good backup and change the reg-value to
D4 -authorative restore.

-- http://support.microsoft.com/?id=290762#5


JSIInc also has some good info. on this topic if you need more
information...


* Also, have you cleaned up the directory since the other DC failed?? If
not, you should perform this:
-- http://support.microsoft.com/?id=216498


--

Paul Williams
_________________________________________
http://www.msresource.net


Join us in our new forums!
http://forums.msresource.net
_________________________________________


I neglected to mentioned that the lone DC is running Win2K Server SP4.
 
Thanks for the suggestions.

apparently this has been an ongoing problem... my backups are no good. same
problem, or else the problem has propagated to the restored version.

went through the directory again, and didn't find anything out of place....
no reference to the old domain controller.

any other thoughts??
 
The exact error shows:

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.
 
OK, so you've already tidied up after the death of the other DC - good for
you.

The Journal Wrap error still needs to resolved. How far back do your
backups go? If you don't have a good backup of the SYSVOL to do the
authorative restore with, I'd suggest calling PSS -I don't know what to do
without a backup to restore with (non-authorative or authorative). Perhaps
somebody else knows of a kind of reset??


--

Paul Williams
_________________________________________
http://www.msresource.net


Join us in our new forums!
http://forums.msresource.net
_________________________________________


The exact error shows:

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.
 
In
ptwilliams said:
OK, so you've already tidied up after the death of the other DC -
good for you.

The Journal Wrap error still needs to resolved. How far back do your
backups go? If you don't have a good backup of the SYSVOL to do the
authorative restore with, I'd suggest calling PSS -I don't know what
to do without a backup to restore with (non-authorative or
authorative). Perhaps somebody else knows of a kind of reset??
Click to expand...

My curiosity is asking if the sysvol data physically exists in the Sysvol
folder?

Was sysvol at anytime scanned with AV scanner?

If the data is in there, are there any or a bunch of NTFRS_* with a random
number on the the end of it folders? If so, see these articles if they
apply:

328492 Folder Name Is Changed to "FolderName_NTFRS_
http://support.microsoft.com/?id=328492
http://www.techsupportforums.com/showthread.php?s=&threadid=7337&forumid=8
http://www.experts-exchange.com/Networking/Q_20728335.html#9307104

Is there another DC in the domain?

Was a Metadata Cleanup performed to remove the old DC references?


--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.
 
Back
Top