Announcement

Collapse
No announcement yet.

SYSVOL not replicating between DC's

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • SYSVOL not replicating between DC's

    This is my current setup.

    Site1: two domain controllers running server 2003
    Server1: RID,PDC,Infastrcuture and a GC with SP1 on it
    Server2: Domain Naming,Schema and is running exchange. i know i shouldn't have exchange on a domain controller! This site already had it installed though.


    Site2: Domain Controller running server 2003
    Server1: Running GC

    The issue:

    Sysvol isn't replicating across the domain. AD seems to be working fine. IE chance passwords and creating groups and such.

    I have run DCdiag and Netdiag on all 3 DC's and no errors are present.

    I can access the the sysvol share via the FQDN.

    These are the following event log errors on the following servers

    Site1
    Server1:


    Event Type: Warning
    Event Source: NtFrs
    Event Category: None
    Event ID: 13508
    Date: 3/4/09
    Time: 11:51:16 AM
    User: N/A
    Computer: Server1
    Description:
    The File Replication Service is having trouble enabling replication from Server2 to Server1 for e:\sysvol\domain using the DNS name domain.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 Server2domain.com from this computer.
    [2] FRS is not running on Server2.domain.com.
    [3] The topology information in the Active Directory for this replica has not yet replicated to all the Domain Controllers.

    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.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: d5 04 00 00 ...

    Site1
    Server2:


    Event Type: Error
    Event Source: NtFrs
    Event Category: None
    Event ID: 13568
    Date: 1/12/2009
    Time: 4:47:54 PM
    User: N/A
    Computer: Server2
    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 : "e:\sysvol\domain"
    Replica root volume is : "\\.\E:"
    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 "\\.\E:" has been formatted.
    [2] The NTFS USN journal on volume "\\.\E:" has been deleted.
    [3] The NTFS USN journal on volume "\\.\E:" 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 "\\.\E:".
    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\Parameter s"
    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.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


    I have not tried this reg fix because i have never done it and i am not sure what will happen. So if someone could explain it to me.


    Site2

    Server1:



    The FRS service will not start. it gives me an error 1053.

  • #2
    Re: SYSVOL not replicating between DC's

    Am i right in assuming that the DC in Site 2 is running 2003 with no service pack?
    If so make sure you install this Hotfix: http://support.microsoft.com/kb/886695 or even better make sure they all are fully patched with the latest SP.

    Cheers
    Caesar's cipher - 3

    ZKHQ BRX HYHQWXDOOB GHFLSKHU WKLV BRX ZLOO UHDOLVH LW ZDV D ZDVWH RI WLPH!

    SFX JNRS FC U6 MNGR

    Comment


    • #3
      Re: SYSVOL not replicating between DC's

      Correct. Server1 at Site2 is not running any SP's. Can i jump directly to SP2?

      Comment


      • #4
        Re: SYSVOL not replicating between DC's

        Yes, go for it. And make sure you update regularly.
        It is highly probable that the problem with the Frs service you are having is the one described on the Hotfix i posted.
        Hopefully installing the SP should sort it. Let us know how you get on.

        Ta
        Caesar's cipher - 3

        ZKHQ BRX HYHQWXDOOB GHFLSKHU WKLV BRX ZLOO UHDOLVH LW ZDV D ZDVWH RI WLPH!

        SFX JNRS FC U6 MNGR

        Comment


        • #5
          Re: SYSVOL not replicating between DC's

          But what about the sysvol replicating problem between server1 and server2 on site1. The FRS service is running.

          Comment


          • #6
            Re: SYSVOL not replicating between DC's

            Well that didn't work. I applied the hotfix from the link you gave and no such luck. Same error.

            Comment


            • #7
              Re: SYSVOL not replicating between DC's

              First post on here so go easy on me

              I would backup the registry key

              HKLM\System\CurrentControlSet\Services\NtFrs\Param eters

              on Server2 (Site 1) and apply the previously mentioned registry change

              Reboot and retry

              Comment


              • #8
                Re: SYSVOL not replicating between DC's

                Also, because Server 2 (Site 1) appears to be in a journal wrap condition it will not replicate any files until this has been restored.

                I think in this situation you will need to stop the FRS service and perform a non-authoritative restore of the data by changing the BurFlag value to d2

                See here for more info

                Comment


                • #9
                  Re: SYSVOL not replicating between DC's

                  Originally posted by derk View Post
                  Well that didn't work. I applied the hotfix from the link you gave and no such luck. Same error.
                  Can you elaborate a bit on that please. Did you just apply the hotfix or did you install the SP?

                  First of all you'll need to troubleshoot the FRS service issue. What's stopping it from starting.
                  Journal wrap errors occur if a sufficient number of changes take place while FRS service is not running.
                  You can give the Registry key mentioned before a go but it's not recommended by MS to be used post Win 2000 server sp3 and it defeats the object as the cause of the problem is still not being addressed.
                  Also, a restore should be the last resort after any other troubleshooting options have been exhausted.

                  This is what I recommend:

                  Try and do the SP update on all the servers first.
                  Try FRSDiag.exe.
                  Check the state of the FRS service and try to start it manually, check credentials, dependencies and related events generated by the service.

                  Post back all the findings and/or solutions.

                  Cheers
                  Caesar's cipher - 3

                  ZKHQ BRX HYHQWXDOOB GHFLSKHU WKLV BRX ZLOO UHDOLVH LW ZDV D ZDVWH RI WLPH!

                  SFX JNRS FC U6 MNGR

                  Comment


                  • #10
                    Re: SYSVOL not replicating between DC's

                    No i just applied the hotfix. Ok so i came across this article that some guy had noticded the file dbghelp.dll was missing. he copied the file from another server and the ntfrs service was able to start. So for the hell of it i did this and the service started. now it is in the event log for FRS it is giving giving me journal wrap error now.

                    Comment


                    • #11
                      Re: SYSVOL not replicating between DC's

                      Personally mate I would try the SYSVOL non-auth restore as I mentioned in my previous post.

                      Also, and I know this is a little off topic, but it' not recommended to have your Infrastructure Master also acting as a Global Catalog.

                      Comment


                      • #12
                        Re: SYSVOL not replicating between DC's

                        I am going to try that tonight. So i should remove the GC from Server1 at site1? What is the advantage of this?

                        Comment


                        • #13
                          Re: SYSVOL not replicating between DC's

                          For info regarding conflict between IM and GC see http://support.microsoft.com/kb/248047

                          Personally I would transfer the IM role to your Server 2 in Site 1

                          Let us know how you get on with the SYSVOL restore

                          Comment


                          • #14
                            Re: SYSVOL not replicating between DC's

                            As you only have one domain, you don't need to worry about the placement of the Infrastructure master role.

                            Comment


                            • #15
                              Re: SYSVOL not replicating between DC's

                              Well i performed the D2 on server 2 at site1. sysvol is now replicating. i am going to perform this on Site2 server 1.

                              Comment

                              Working...
                              X