Re: JRNL_WRAP_ERROR on SBS2003 R2 Standard

Tech-Archive recommends: Speed Up your PC by fixing your registry

Your AD database files have become corrupt and they are trying to sync with some non-existent data. If you have a second windows server in your domain and it is also a DC then you can force replication...but since you are posting here, I will assume that your SBS server is your only server. In that case I strongly recommend performing a backup of your server (in case my next step kills you) and then restoring the system-state from a previous backup.

Then go buy a UPS for your server.

I wish I had better news for ya,

-Cliff

"Januar" <Januar@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:7A81A026-DDFE-48B6-8B98-ABD1A4AB2D14@xxxxxxxxxxxxxxxx
Hi,
Recently I got issue with SBS 2003 R2 Standard server. I noticed this after
there was a power failure. When the server is back there are some errors on
the event logs. After one day the server will start to be very slow and it
looks like hang. I got to restart the server to make it operational again.

DNS logs report issue such as:

Event Type: Error
Event Source: DNS
Event Category: None
Event ID: 4015
Date: 5/25/2008
Time: 1:12:35 AM
User: N/A
Computer: SERVER
Description:
The DNS server has encountered a critical error from the Active Directory.
Check that the Active Directory is functioning properly. The extended error
debug information (which may be empty) is "".


Event Type: Error
Event Source: DNS
Event Category: None
Event ID: 4000
Date: 5/25/2008
Time: 3:38:36 PM
User: N/A
Computer: SERVER
Description:
The DNS server was unable to open Active Directory. This DNS server is
configured to obtain and use information from the directory for this zone and
is unable to load the zone without it. Check that the Active Directory is
functioning properly and reload the zone.



Other log from FRS:
Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13568
Date: 5/25/2008
Time: 12:00:04 AM
User: N/A
Computer: SERVER
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:\windows\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.



There is only 1 single server in the domain. Any help is appreciated.

Regards,

.

Relevant Pages

  • Re: ntfrs errors
    ... Originally the was an older server running windows 2000 server. ... The File Replication Service has detected that the replica set "DOMAIN ... Setting the "Enable Journal Wrap Automatic Restore" ...
    (microsoft.public.windows.server.general)
  • Re: Old DC with problem
    ... DCSERVER -> This is the old DC server ... The File Replication Service has detected that the replica set "DOMAIN ... Replica set name is: ... No more error in Event Viewer on FRS feature ...
    (microsoft.public.win2000.active_directory)
  • Re: JRNL_WRAP_ERROR on SBS2003 R2 Standard
    ... If you have a second windows server in your domain and it is also a DC then you can force replication...but since you are posting here, I will assume that your SBS server is your only server. ... The DNS server has encountered a critical error from the Active Directory. ... The File Replication Service has detected that the replica set "DOMAIN ...
    (microsoft.public.windows.server.sbs)
  • Re: ADAM back up and restore
    ... > partitions that were part of a replica set then just injecting the ... > would play havoc if the server thus restored got sight of the original ... > If you look in the ADAM help that comes with ADAM then in the How To ... > is installing ...
    (microsoft.public.windows.server.active_directory)
  • Re: Ntfrs Journal Wrap Error
    ... At the next poll, which will occur in 5 minutes, this computer will be re-added to the replica set. ... The source server has the following error in the File Replication Service Event Log: ... 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. ...
    (microsoft.public.windows.server.sbs)