Dyslexic much? I figured you'd transposed a number, but I didn't want to guess. It's Error *13568*, and you'd previously posted 13586. There's a bunch of stuff on Google that comes up when you put in the right error code. Secondly, the directions for recovering from this error are actually in the error code, did you follow those and are you still encountering problems?
On Tue, Sep 20, 2011 at 10:36 AM, [email protected] <[email protected]> wrote: > ------------------------------------------------------------**** > > FRSDiag v1.7 on 09/19/2011 3:15:20 PM**** > > .\030405MF663P44 on 2011-09-19 at 3.15.20 PM**** > > ------------------------------------------------------------**** > > ** ** > > Checking for errors/warnings in FRS Event Log .... **** > > NtFrs 08/23/2011 8:45:26 AM Error 13568 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. **** > > NtFrs 08/21/2011 10:54:06 AM Error 13568 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. **** > > NtFrs 08/13/2011 9:11:28 PM Error 13568 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. **** > > NtFrs 08/08/2011 9:09:45 AM Error 13568 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. **** > > NtFrs 04/03/2011 7:16:29 PM Warning 13508 The File > Replication Service is having trouble enabling replication from > 031004LD5Z3H77 to 030405MF663P44 for c:\windows\sysvol\domain using the DNS > name 031004LD5Z3H77.IMCU.local. FRS will keep retrying. Following are > some of the reasons you would see this warning. [1] FRS can not > correctly resolve the DNS name 031004LD5Z3H77.IMCU.local from this > computer. [2] FRS is not running on 031004LD5Z3H77.IMCU.local. [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. **** > > NtFrs 04/02/2011 7:16:28 PM Warning 13508 The File > Replication Service is having trouble enabling replication from > 031004LD5Z3H77 to 030405MF663P44 for c:\windows\sysvol\domain using the DNS > name 031004LD5Z3H77.IMCU.local. FRS will keep retrying. Following are > some of the reasons you would see this warning. [1] FRS can not > correctly resolve the DNS name 031004LD5Z3H77.IMCU.local from this > computer. [2] FRS is not running on 031004LD5Z3H77.IMCU.local. [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. **** > > NtFrs 04/01/2011 6:16:28 PM Warning 13508 The File > Replication Service is having trouble enabling replication from > 031004LD5Z3H77 to 030405MF663P44 for c:\windows\sysvol\domain using the DNS > name 031004LD5Z3H77.IMCU.local. FRS will keep retrying. Following are > some of the reasons you would see this warning. [1] FRS can not > correctly resolve the DNS name 031004LD5Z3H77.IMCU.local from this > computer. [2] FRS is not running on 031004LD5Z3H77.IMCU.local. [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.**** > > WARNING: Found Event ID 13508 errors without trailing 13509 > ... see above for (up to) the 3 latest entries!**** > > ** ** > > ......... failed 5**** > > Checking for errors in Directory Service Event Log .... passed**** > > Checking for minimum FRS version requirement ... passed**** > > Checking for errors/warnings in ntfrsutl ds ... passed**** > > Checking for Replica Set configuration triggers... passed**** > > Checking for suspicious file Backlog size... passed**** > > Checking Overall Disk Space and SYSVOL structure (note: integrity is not > checked)... passed**** > > Checking for suspicious inlog entries ... passed**** > > Checking for suspicious outlog entries ... passed**** > > Checking for appropriate staging area size ... passed**** > > Checking for errors in debug logs ... passed**** > > Checking NtFrs Service (and dependent services) state...**** > > ERROR : Required Service not Running : "Windows Time" is > currently "Stopped"**** > > ......... failed 1**** > > Checking NtFrs related Registry Keys for possible problems...passed**** > > Checking Repadmin Showreps for errors...passed**** > > ** ** > > *From:* Jonathan Link [mailto:[email protected]] > *Posted At:* Tuesday, September 20, 2011 9:55 AM > > *Posted To:* [email protected] > *Conversation:* DC's and FRS errors > *Subject:* Re: DC's and FRS errors**** > > ** ** > > Those logs have long since been flushed, I don't recall the error numbers > off the top of my head.**** > > **** > > I'll admit, a bit of googling doesn't show much on those errors, perhaps > posting a more complete detail of the error would be helpful?**** > > On Tue, Sep 20, 2011 at 9:43 AM, [email protected] <[email protected]> > wrote:**** > > 13086 and 13586 errors? I am still looking in google but thought I would > through them out there.**** > > **** > > **** > > *From:* Jonathan Link [mailto:[email protected]] > *Posted At:* Monday, September 19, 2011 10:11 AM**** > > > *Posted To:* [email protected]**** > > *Conversation:* DC's and FRS errors**** > > > *Subject:* Re: DC's and FRS errors**** > > **** > > +1 I had FRS errors a few months ago, GTS (Google Technical Support) was > very effective at pointing out methods for resolution. I'd use them again > in the future... :-)**** > > > > **** > > On Mon, Sep 19, 2011 at 10:07 AM, Martin Blackstone <[email protected]> > wrote:**** > > What’s the error say? You can more than likely plug it in to Google and get > your answer.**** > > **** > > *From:* [email protected] [mailto:[email protected]] **** > > *Sent:* Monday, September 19, 2011 6:54 AM**** > > > *To:* NT System Admin Issues**** > > *Subject:* DC's and FRS errors**** > > **** > > Ok I think I need to start over. I think my 3 DC's are not talking to each > other because the Group Policies on one don't match the Group policies on > the others. Running DC Diag I notice FRS has an error.**** > > I am on a Windows 2003 Active Directory. I have 3 DC's that were talking > to each other at one point but now have a hiccup someplease. How can I > troubleshoot this??**** > > Thanks**** > > David**** > > **** > > *From:* Free, Bob [mailto:[email protected]] > *Posted At:* Friday, September 09, 2011 2:23 PM > *Posted To:* [email protected] > *Conversation:* WSUS 3 sp2 > *Subject:* RE: WSUS 3 sp2**** > > **** > > As relevant as ever - http://kb.ultratech-llc.com/~moreinfo.txt**** > > **** > > **** > > *From:* [email protected] [mailto:[email protected]] **** > > *Sent:* Friday, September 09, 2011 11:17 AM > *To:* NT System Admin Issues > *Subject:* WSUS 3 sp2**** > > **** > > Trying to get this to work it seems that 1 of my DC's is not talking to the > other 2.**** > > Windows 2003 domain.**** > > FRS is failing when I run dcdiag???**** > > **** > > **** > > This e-mail and any files transmitted with it are property of Indiana Members > Credit Union, are confidential, and are intended solely for the use of the > individual or entity to whom this e-mail is addressed. If you are not one of > the named recipient(s) or otherwise have reason to believe that you have > received this message in error, please notify the sender and delete this > message immediately from your computer. Any other use, retention, > dissemination, forwarding, printing, or copying of this email is strictly > prohibited.**** > > Please consider the environment before printing this email.**** > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~**** > > > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to [email protected] > with the body: unsubscribe ntsysadmin**** > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to [email protected] > with the body: unsubscribe ntsysadmin**** > > This e-mail and any files transmitted with it are property of Indiana Members > Credit Union, are confidential, and are intended solely for the use of the > individual or entity to whom this e-mail is addressed. If you are not one of > the named recipient(s) or otherwise have reason to believe that you have > received this message in error, please notify the sender and delete this > message immediately from your computer. Any other use, retention, > dissemination, forwarding, printing, or copying of this email is strictly > prohibited.**** > > Please consider the environment before printing this email.**** > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~**** > > > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to [email protected] > with the body: unsubscribe ntsysadmin**** > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to [email protected] > with the body: unsubscribe ntsysadmin**** > > **** > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to [email protected] > with the body: unsubscribe ntsysadmin**** > > This e-mail and any files transmitted with it are property of Indiana Members > Credit Union, are confidential, and are intended solely for the use of the > individual or entity to whom this e-mail is addressed. If you are not one of > the named recipient(s) or otherwise have reason to believe that you have > received this message in error, please notify the sender and delete this > message immediately from your computer. Any other use, retention, > dissemination, forwarding, printing, or copying of this email is strictly > prohibited.**** > > Please consider the environment before printing this email.**** > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to [email protected] > with the body: unsubscribe ntsysadmin**** > > ** ** > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to [email protected] > with the body: unsubscribe ntsysadmin**** > > This e-mail and any files transmitted with it are property of Indiana Members > Credit Union, are confidential, and are intended solely for the use of the > individual or entity to whom this e-mail is addressed. If you are not one of > the named recipient(s) or otherwise have reason to believe that you have > received this message in error, please notify the sender and delete this > message immediately from your computer. Any other use, retention, > dissemination, forwarding, printing, or copying of this email is strictly > prohibited. > Please consider the environment before printing this email. > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to [email protected] > with the body: unsubscribe ntsysadmin > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
