Replication Error - Event ID 13508

Posted on 2007-08-03
Medium Priority
Last Modified: 2013-11-05
Recently  I added a Windows 2003 DC into my Win 2000 Domain  .... And now , in Event Log, I see the following error message , how to fix this issue ..

he File Replication Service is having trouble enabling replication from SULTAN_DOMAIN to DOM0307 for c:\windows\sysvol\domain using the DNS name sultan_domain.Sultan.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 sultan_domain.Sultan.Com from this computer.  ( NO WAY,  I CAN PING WITH OUT ANY PROBLEM )
 [2] FRS is not running on sultan_domain.Sultan.Com.  ( IT IS RUNNING )
 [3] The topology information in the Active Directory for this replica has not yet replicated to all the Domain Controllers. ( THERE ARE ONLY TWO DCs  ... )
 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.

what to do, ?   In my  WINDOWS 2000 DC  , I had seen the following error, but only once

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.
Click down the key path:
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.

advise plzzzzzzzzzzzzz
Question by:manu4u
  • 2
LVL 13

Expert Comment

ID: 19624743
The journal is a file of changes that needs to be applied to sysvol.  the wrap condition occurs when the file fills, for whatever reason, and the next record will overwrite the first.  This wrap condition will prevent your DC from sharing sysvol if you reboot.  Do the procedure (non-authorative restore) in support.microsoft.com/kb/290762 on the offending dc.  It takes about 2 minutes.  

Author Comment

ID: 19630435
I did a Non authorative restore, but now I am screwed totally ...
No user can login to DOMAIN , Authentication is not happening, they get DOMAIN is not available ...
Both DCs are online and Netlogon service is running, but Authentication is not happening ...
I have been trying from the mroning, but after 4 hours, still no lujck .... .. .


Accepted Solution

manu4u earned 0 total points
ID: 19630536
Well, Finally I fixed it ...

SYSVOL folder, I removed the sharing and then shared again, and everything got ok ..
what the hell , i have never been fuked up like this before ...  anyway, it is fixed ..

thank u dear .

Expert Comment

ID: 20898488
Your question has the answer ->  If you have JRNL_WRAP_ERROR then you must add the registry entry on the DC with the sysvol that needs to be replicated.  The next repl poll will cause a rebuild of the important stuff.  You can force the rebuild by restarting the FRS service on both DC's.  Be sure to set the registry value back to "0" after it's fixed.

Featured Post

Get free NFR key for Veeam Availability Suite 9.5

Veeam is happy to provide a free NFR license (1 year, 2 sockets) to all certified IT Pros. The license allows for the non-production use of Veeam Availability Suite v9.5 in your home lab, without any feature limitations. It works for both VMware and Hyper-V environments

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Auditing domain password hashes is a commonly overlooked but critical requirement to ensuring secure passwords practices are followed. Methods exist to extract hashes directly for a live domain however this article describes a process to extract u…
After seeing many questions for JRNL_WRAP_ERROR for replication failure, I thought it would be useful to write this article.
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This video shows how to use Hyena, from SystemTools Software, to update 100 user accounts from an external text file. View in 1080p for best video quality.
Suggested Courses

862 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question