ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    JRNL_WRAP_ERROR (SYSVOL)

    IT Discussion
    sysvol replication error windows server domain controller
    5
    15
    3.6k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • wirestyle22W
      wirestyle22
      last edited by wirestyle22 

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

      My co-worker tried to create something in group policy and eventually realized that it wasn't applying. I checked to see if everything was replicating correctly. I did notice that SYSVOL doesn't seem to be replicating and I see a JRNL_WRAP_ERROR listed in the event viewer. I also ran a report that listed this:

      0_1494960455003_eventid.png

      0_1494960459087_eventid2.png

      1 Reply Last reply Reply Quote 1
      • momurdaM
        momurda
        last edited by

        Did the hdd run out of space? Did you do what it says with the registry? Is the FRS service running?
        Side note, all these problems are probably due to your dns configuration across the multiple domains you have set up.
        dcdiag.exe /v /test:dns and dcdiag.exe /v /test:replications should return no errors. If you get your environment there, i suspect these problems will disappear forever.

        1 Reply Last reply Reply Quote 2
        • wirestyle22W
          wirestyle22
          last edited by

          @momurda

          1. The HDD did in fact run of of space at one point.
          2. I did do what it says with the registry but it did not solve the issue.
          3. The FRS service is running

          dcdiag.exe /v /test:dns
          0_1494961088199_DNS Test.png

          dcdiag.exe /v /test:replications
          0_1494961097646_Replication Test.png

          1 Reply Last reply Reply Quote 0
          • momurdaM
            momurda
            last edited by

            You can try restarting the FRS, see if that clears it up if the server has free space now. Also possible you might have to demote then promote to get it working again.

            wirestyle22W 1 Reply Last reply Reply Quote 0
            • wirestyle22W
              wirestyle22 @momurda
              last edited by wirestyle22

              @momurda said in JRNL_WRAP_ERROR (SYSVOL):

              You can try restarting the FRS, see if that clears it up if the server has free space now. Also possible you might have to demote then promote to get it working again.

              That's what I read which is really unfortunate because some of my DC's are file servers (inherited). We will see if I see more of these logs populate. Thanks for the help.

              DashrenderD dbeatoD 2 Replies Last reply Reply Quote 0
              • DashrenderD
                Dashrender @wirestyle22
                last edited by

                @wirestyle22 said in JRNL_WRAP_ERROR (SYSVOL):

                @momurda said in JRNL_WRAP_ERROR (SYSVOL):

                You can try restarting the FRS, see if that clears it up if the server has free space now. Also possible you might have to demote then promote to get it working again.

                That's what I read which is really unfortunate because some of my DC's are file servers (inherited). We will see if I see more of these logs populate. Thanks for the help.

                So reboot after hours, problem solved.

                wirestyle22W 1 Reply Last reply Reply Quote 1
                • wirestyle22W
                  wirestyle22 @Dashrender
                  last edited by wirestyle22

                  @Dashrender said in JRNL_WRAP_ERROR (SYSVOL):

                  @wirestyle22 said in JRNL_WRAP_ERROR (SYSVOL):

                  @momurda said in JRNL_WRAP_ERROR (SYSVOL):

                  You can try restarting the FRS, see if that clears it up if the server has free space now. Also possible you might have to demote then promote to get it working again.

                  That's what I read which is really unfortunate because some of my DC's are file servers (inherited). We will see if I see more of these logs populate. Thanks for the help.

                  So reboot after hours, problem solved.

                  I'm not paid to stay and neither is anyone else. Boss is away for a month. Unsure how it's going to work. I'm trying to stop putting myself into positions where i have to stay without pay.

                  scottalanmillerS 1 Reply Last reply Reply Quote 0
                  • scottalanmillerS
                    scottalanmiller @wirestyle22
                    last edited by

                    @wirestyle22 said in JRNL_WRAP_ERROR (SYSVOL):

                    @Dashrender said in JRNL_WRAP_ERROR (SYSVOL):

                    @wirestyle22 said in JRNL_WRAP_ERROR (SYSVOL):

                    @momurda said in JRNL_WRAP_ERROR (SYSVOL):

                    You can try restarting the FRS, see if that clears it up if the server has free space now. Also possible you might have to demote then promote to get it working again.

                    That's what I read which is really unfortunate because some of my DC's are file servers (inherited). We will see if I see more of these logs populate. Thanks for the help.

                    So reboot after hours, problem solved.

                    I'm not paid to stay and neither is anyone else. Boss is away for a month. Unsure how it's going to work. I'm trying to stop putting myself into positions where i have to stay without pay.

                    Yeah, no pay means it's not even legal to stay.

                    1 Reply Last reply Reply Quote 0
                    • scottalanmillerS
                      scottalanmiller
                      last edited by

                      Sounds like this was determined to "not matter". Problem solved.

                      wirestyle22W 1 Reply Last reply Reply Quote 1
                      • wirestyle22W
                        wirestyle22 @scottalanmiller
                        last edited by

                        @scottalanmiller said in JRNL_WRAP_ERROR (SYSVOL):

                        Sounds like this was determined to "not matter". Problem solved.

                        It matters, just not enough to put me in indentured servitude

                        scottalanmillerS 1 Reply Last reply Reply Quote 0
                        • scottalanmillerS
                          scottalanmiller @wirestyle22
                          last edited by

                          @wirestyle22 said in JRNL_WRAP_ERROR (SYSVOL):

                          @scottalanmiller said in JRNL_WRAP_ERROR (SYSVOL):

                          Sounds like this was determined to "not matter". Problem solved.

                          It matters, just not enough to put me in indentured servitude

                          The amount that it matters is to them. You are an employee, it doesn't matter at all to you.

                          DashrenderD 1 Reply Last reply Reply Quote 1
                          • DashrenderD
                            Dashrender @scottalanmiller
                            last edited by

                            @scottalanmiller said in JRNL_WRAP_ERROR (SYSVOL):

                            @wirestyle22 said in JRNL_WRAP_ERROR (SYSVOL):

                            @scottalanmiller said in JRNL_WRAP_ERROR (SYSVOL):

                            Sounds like this was determined to "not matter". Problem solved.

                            It matters, just not enough to put me in indentured servitude

                            The amount that it matters is to them. You are an employee, it doesn't matter at all to you.

                            This is a HARD thing to accept - Scott only care about things he's paid to care about - or is his family 😛 But when it comes to work, he if the company isn't paying him to care about, he doesn't give it a second thought.

                            Sadly, I am not that way about most of my job, which, as has been rightly pointed out to me, gets me into trouble worrying about things that aren't my concern.

                            wirestyle22W 1 Reply Last reply Reply Quote 0
                            • wirestyle22W
                              wirestyle22 @Dashrender
                              last edited by

                              @Dashrender said in JRNL_WRAP_ERROR (SYSVOL):

                              @scottalanmiller said in JRNL_WRAP_ERROR (SYSVOL):

                              @wirestyle22 said in JRNL_WRAP_ERROR (SYSVOL):

                              @scottalanmiller said in JRNL_WRAP_ERROR (SYSVOL):

                              Sounds like this was determined to "not matter". Problem solved.

                              It matters, just not enough to put me in indentured servitude

                              The amount that it matters is to them. You are an employee, it doesn't matter at all to you.

                              This is a HARD thing to accept - Scott only care about things he's paid to care about - or is his family 😛 But when it comes to work, he if the company isn't paying him to care about, he doesn't give it a second thought.

                              Sadly, I am not that way about most of my job, which, as has been rightly pointed out to me, gets me into trouble worrying about things that aren't my concern.

                              I'm trying to change

                              1 Reply Last reply Reply Quote 1
                              • dbeatoD
                                dbeato @wirestyle22
                                last edited by

                                @wirestyle22 You can still do the following as well:
                                http://kpytko.pl/active-directory-domain-services/authoritative-sysvol-restore-frs/
                                https://blogs.msmvps.com/acefekay/2013/08/28/how-to-recover-a-journal-wrap-error-jrnl_wrap_error-and-a-corrupted-sysvol-from-a-good-dc-what-option-do-i-use-d4-or-d2-whats-the-difference-between-d4-and-d2/

                                Maybe also move to DFRS instead of FRS, you would only use FRS if it is Server 2003 as part of one of your DCs

                                wirestyle22W 1 Reply Last reply Reply Quote 1
                                • wirestyle22W
                                  wirestyle22 @dbeato
                                  last edited by

                                  @dbeato said in JRNL_WRAP_ERROR (SYSVOL):

                                  @wirestyle22 You can still do the following as well:
                                  http://kpytko.pl/active-directory-domain-services/authoritative-sysvol-restore-frs/
                                  https://blogs.msmvps.com/acefekay/2013/08/28/how-to-recover-a-journal-wrap-error-jrnl_wrap_error-and-a-corrupted-sysvol-from-a-good-dc-what-option-do-i-use-d4-or-d2-whats-the-difference-between-d4-and-d2/

                                  Maybe also move to DFRS instead of FRS, you would only use FRS if it is Server 2003 as part of one of your DCs

                                  Possibly in the future but I have so many other things to focus on

                                  1 Reply Last reply Reply Quote 0
                                  • 1 / 1
                                  • First post
                                    Last post