Replication Error - Event ID 13508

Posted on 2007-08-03
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
    LVL 13

    Expert Comment

    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 on the offending dc.  It takes about 2 minutes.  
    LVL 7

    Author Comment

    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 .... .. .

    LVL 7

    Accepted Solution

    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 .
    LVL 1

    Expert Comment

    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.

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    Maximize Your Threat Intelligence Reporting

    Reporting is one of the most important and least talked about aspects of a world-class threat intelligence program. Here’s how to do it right.

    This is my first article in EE and english is not my mother tongue so any comments you have or any corrections you would like to make, please feel free to speak up :) For those of you working with AD, you already are very familiar with the classi…
    This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…
    This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…

    759 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

    Need Help in Real-Time?

    Connect with top rated Experts

    13 Experts available now in Live!

    Get 1:1 Help Now