SBS2000 and AD looks as if it’s down

My managed SBS2000 had some warnings regarding NTFrs:

Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13561
Date: 6/2/2006
Time: 2:32:55 PM
User: N/A
Computer: MYDC
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:winntsysvoldomain"
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:".

Following recovery steps will 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.
[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.

Event error code 13561, module NtFrs.

A while back, it had some unexpected power failure, and I’ev had to use chkdsk to recover the server (BSoD, with "Inaccessible boot device").

This error message repeated for quite a while. I’ve gotten this error message just as well:

Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13568
Date: 5/19/2006
Time: 7:37:07 PM
User: N/A
Computer: MYDC
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:winntsysvoldomain"
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:
"SystemCurrentControlSetServicesNtFrsParameters"
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 have followed these suggestions, and things looked OK. However, after a reboot, later this week, I’ve discovered that the DC failed to start correctly. Netlogon, DNS, everything went up fine, but clients were unable to auth…

I’ve got this error in my Eventviewer:

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1000
Date: 6/4/2006
Time: 10:19:38 AM
User: NT AUTHORITYSYSTEM
Computer: MYDC
Description:
Windows cannot determine the user or computer name. Return value (1355).

Which led me to believe it’s some DC related problem.

I’ve searched the web, and got to this link in ExpertExchange. It did point me in the correct direction, as following its procedure in here, I was able to recover my NtFrs, and get the netlogon and sysvol up again. So everythin was working fine.

Regarding creation of "reparse points", or "Junctions", this link has it all. However, for us Unix originated people, who know soft and hard links, it’s the other way around. MS define source and target in reverse, so when they reffer to linkd.exe source target, the idea is somewhat like "linkd.exe target source". Example:

"linkd c:myfolder c:me", will create a c:myfolder which is a junction of c:me, and not the other way around.