Jorge, Sorry, I forgot to mention in my previous send that I did that as well on the other two DC's. Thank you for the reminder as it would have come in handy if I had of forgotten.
Rodney -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jorge de Almeida Pinto Sent: Monday, 15 November 2004 8:09 PM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] JRNL_WRAP_ERROR in File Replication Service Event LOG Hi, Remember: * if you're doing a D2 on some DC it is not mandatory to do a D4 on another DC. * if you're doing a D4 on some DC it IS mandatory to do a D2 on all other replica's!!! See http://support.microsoft.com/default.aspx?scid=kb;en-us;290762 section "authoritative restore" Regards, Jorge -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rodney Gardiner Sent: Friday, November 12, 2004 00:24 To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] JRNL_WRAP_ERROR in File Replication Service Event LOG Eric, Thanks for all your information here. I read up on it and consulted Microsoft it was a D4 that was actually required due to this machine being the Main DC. All changes were made on this machine and it was not replicating the changes out to the other servers. I also checked to see why it Journal Wrapped and Microsoft also suggested it was due more than likely due to the stability of the machine. (It use to restart itself for what appeared to be no reason several times a day but that has now been resolved as well.) The change was smooth sailing as it is only a small site. FRS is happening sweetly now. Thanks again. Rodney -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eric Fleischman Sent: Tuesday, 26 October 2004 10:03 AM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] JRNL_WRAP_ERROR in File Replication Service Event LOG It's unpleasant only in that you vvJoin. I'd suggest doing it off hours, but unless it's a HUGE data set, it probably will be smooth sailing. I'd definitely check out some KB articles on it first (search on burflags and D2 to find them) but really, it shouldn't be all that bad. Again, if you have a large data set (many gigs) it's worth talking about. If it's small, no worries. > Also, Ultrasound? Not sure what you mean here. Ah, Ultrasound is the tool we release for monitoring FRS replica sets. http://www.microsoft.com/downloads/details.aspx?FamilyID=61acb9b9-c354-4 f98-a823-24cc0da73b50&displaylang=en ~Eric -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rodney Gardiner Sent: Monday, October 25, 2004 6:49 PM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] JRNL_WRAP_ERROR in File Replication Service Event LOG Eric, I am running SP4. It sounds like a D2 is not a pleasant action to take from your "If Afraid" comment. I will read up on this as much as possible but are there any major dangers of doing a D2 as this error is coming up on our main PDC which is all the Operations Masters and Catalo Server. It is also our Exchange2000 box. I am a little concerned that if I make a change with this D2 that there could be ramifications that cause a bigger problem. Also, Ultrasound? Not sure what you mean here. Yeah, the last statement did make sense. I am not heaps familiar with Win2000. I am learning a lot as I go but we had "Professionals" come in and set things up and we have had many a trouble. I am trying to fix all the troubles as I go along etc. Thanks for your help so far and I appreciate any final thoughts etc that you can give me with doing a D2 and setting up Ultrasound. Rodney -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eric Fleischman Sent: Tuesday, 26 October 2004 6:20 AM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] JRNL_WRAP_ERROR in File Replication Service Event LOG If the value isn't there, then that means you're using Windows defaults. If you're journal wrapping with SP3+, you almost definitely had a long-term replication issue. I'd suggest: 1) D2 the node - that's the recovery from a journal wrap I'm afraid 2) Set up Ultrasound to monitor FRS in the long term. #2 will let you know you have a problem before you have a problem, if that makes sense. :) ~Eric -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rodney Gardiner Sent: Monday, October 25, 2004 12:41 AM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] JRNL_WRAP_ERROR in File Replication Service Event LOG Eric, Thanks for the info. I took a look at the registry setting to see how big the Journal Size was as per the KB Article:- HKLM\System\CCS\Services\NTFRS\Parameters\"Ntfs Journal size in MB" (REG_DWORD) Does this need to be added?? But I do not have that setting in that registry position. The closest I had was:- HKLM\System\CCS\Services\NTFRS\Parameters\Staging Space Limit in KB (REG_DWORD) and it was 675840 I also checked the WinNT\Ntfrs\jet Folder and the NTFRS.JDB is only 1MB in size. I also used the repadmin /showreps tool and it stated that the inbound have all been successful for all 3 (CN=Schema, CN=Configuration, DC=domain). And as for Outbound there were no last attempts for the 3 types. As for the full FRS Event Logs in Event Viewer they are all the same:- It states The FRS Services is starting and then about 3 minutes later the warning I posted below appears. The only other entry in the FRS Event Log is:- Following is the summary of warnings and errors encountered by File Replication Service while polling the Domain Controller VLSEXCH2000.vanguard.com.au for FRS replica set configuration information. Could not find computer object for this computer. Will try again at next polling cycle This cycle has been the same for quite some time now. If you are referring to the NTFRS logs in the WinNT\Debug folders then I will admit that I do not understand them. Even after reading the article not sure where to proceed from here to fix the error. Any further guidance would be appreciated. Rodney -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eric Fleischman Sent: Monday, 25 October 2004 2:50 PM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] JRNL_WRAP_ERROR in File Replication Service Event LOG Hi Rodney, We're actually somewhat "cold" towards this as a recovery step these days. As of 2k SP3, we disabled this by default. We're far more "warm" to recovering the node by hand and increasing the journal size so you don't hit this again (if you need the larger journal size). The increasing of journal size is only if you really need it. If this is a one-off problem, I'd rather set up monitoring (Ultrasound) and catch it before we wrap again. Note that if you do need to do a D2, you will vvJoin the replica set. A few articles that might help understand what I'm talking about. :) http://support.microsoft.com/kb/292438 http://support.microsoft.com/default.aspx?scid=kb;EN-US;290762 It's hard to make a recommendation with the data given so far (I'd need full FRS logs) but I smell a D2 coming. That's just a hunch though. ~Eric -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rodney Gardiner Sent: Sunday, October 24, 2004 11:13 PM To: [EMAIL PROTECTED] Subject: [ActiveDir] JRNL_WRAP_ERROR in File Replication Service Event LOG Yet another problem.... I have seen this before and tried to do what the message states at the bottom about changing "Enable Journal Wrap Automatic Restore" registry parameter to 1. I did this once before and had major problems. Is this anything to be concerned about and how would I go about fixing it? 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. 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. Rodney List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you. List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
