The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.
| Request a translation of the event description in plain English! An example of "English please" is available here. | |
| What is the role of File Replication Service? | |
| Ron Paskowski (Last update 12/12/2006): Performing the steps below solved my problem: 1. Expand "HKLM\System\CurrentControlSet\Services\NtFrs\Parameters" 2. Change value for "Enable Journal Wrap Automatic Restore" from 0 to 1. If the DWORD Value does not exist, create a new one with the exact spelling as above, including spaces but without the quotes. 3. Stop the NTFRS Service (open a command prompt and type "net stop ntfrs") 4. Start the NTFRS Service (net start ntfrs) 5. Monitor the File Replication Service Event Logs for events: • 13553 – The DC is performing the recovery process • 13554 – The DC is ready to pull the replica from another DC. • 13516 - At this point go to step 6. (the problem is resolved if you receive this event) 6. Using a command prompt type: "net share" and look for the Netlogon and Sysvol Shares to appear. The Journal Wrap error is only fixed after the Domain Controller receives the new SYSVOL replica from a peer Domain Controller. This may take a period of time depending on where your peer DC is located and on bandwidth. 7. Change value for "Enable Journal Wrap Automatic Restore" from 1 to 0. Mihai Andrei (Last update 10/6/2005): See the link to "Troubleshooting File Replication Service" for a complete description of this event. Ionut Marin (Last update 8/19/2005): M292438 gives information on troubleshooting Journal_Wrap errors on Sysvol and DFS Replica Sets. See M887303 for additional information on this issue. Andi K (Last update 12/5/2003): As per Microsoft: "FRS no longer performs an automatic non-authoritative restore if a journal wrap condition is detected. Instead, it logs an event ID 13568 message in the FRS event log to remind you to perform the operation at a convenient time. A registry key has been included to configure an automatic non-authoritative restore operation if you want to do so. However, if you configure this setting, the contents of the replica tree may be made unavailable while the restore operation is taking place". See M321557 for more details. Tom McMeekin After speaking with MS Technical Support, I was emailed a Q article, which did fix the problem. See M315070 ("Event 13568 Is Logged in the File Replication Service Event Log[ntrelease]"). The Q article does not appear to be available anymore so here is the content (please note that if the article is not available anymore then it probably means that is no longer valid or was wrong!): Event 13568 Is Logged in the File Replication Service Event Log[ntrelease] ID: M315070 CREATED: 18-DEC-2001 MODIFIED: 06-AUG-2002 The information in this article applies to: - Microsoft Windows 2000 Advanced Server - Microsoft Windows 2000 Server ------------------------------------------------------------------------------- [...] SYMPTOMS ======== The following event may be logged in the File Replication service (FRS) event log after you install Windows 2000 Service Pack 3 (SP3): Event Type: Warning Event Source: NtFrs Event Category: None Event ID: 13568 Date: 12/12/2001 Time: 2:03:32 PM User: N/A computer: NA-DC-01 Description: [... event description...] CAUSE ===== This error message is logged because the requested data is not available due to the following series of events: - FRS uses the NTFS file system journal to track changes to files and to folders that are in a replica tree to propagate those changes to other members of the replica set. - If FRS does not record the changes, the journal wraps and FRS does not know which change to process next. FRS may not record the changes because: - FRS is off for an extended period of time. -or- - The changes are occurring faster than FRS can process them. - To recover from this error state, FRS needs to: - Re-initialize the content of the replicated directory. - Resume tracking the NTFS journal from a known good starting point. - To re-initialize the replica tree, FRS moves all content into the NTFRS_Pre-Existing folder, and then FRS rejoins the replica set by sourcing from an upstream partner. Based on the contents of the file, one of the following events occurs: - If a file on the upstream partner is identical to the file that is in the NTFRS_Pre-Existing folder, the local copy is moved into the replica tree. - If the file is different, or if new files have been added to the replica set, FRS replicates the update from the upstream partner and moves it into the replica tree. - During this procedure, the data on that particular member becomes unavailable. In Service Pack 2 (SP2), this re-initialization takes place automatically, which may take the data offline at an inopportune time. In SP3, the event is logged by default and an administrator can re-initialize the replica tree at a convenient time. RESOLUTION ========== [...] To modify the default behavior, make the following changes in the registry to instruct FRS to handle the JRNL_WRAP_ERROR status automatically: 1. Stop FRS. 2. Start Registry Editor (Regedt32.exe). 3. Locate and click the following key in the registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters 4. On the Edit menu, click Add Value, and then add the following registry value: Value name: Enable Journal Wrap Automatic Restore Data type: REG_DWORD Radix: Hexadecimal Value data: 1 (Default 0) 5. Quit Registry Editor. 6. Restart FRS. If these steps do not modify the default settings and the automatic re-initialization is not turned on, you need to manually re-initialize the replica tree. At a convenient time, make the following changes to the registry: 1. Stop FRS. 2. Start Registry Editor (Regedt32.exe). 3. Locate and click the following key in the registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore/Process at Startup 4. On the Edit menu, click Add Value, and then add the following registry value: Value name: BurFlags Data type: REG_DWORD Radix: Hexadecimal Value data: D2 5. Quit Registry Editor. 6. Restart FRS. MORE INFORMATION ================ For additional information about SP3 updates to the File Replication service, click the article number below to view the article in the Microsoft Knowledge Base: M307319 File Replication Service Improvements in Windows 2000 SP3 |
Brak komentarzy:
Prześlij komentarz