We help IT Professionals succeed at work.

File Replication Service Error - Event ID 13568

Alisanne
Alisanne asked
on
I have searched and read several articles on this error, and I still have a few questions.

Environment: I have a SBS 2003 Server (The only server) and 5-POS (XP embeded) terminals.

Situation: On 5 occasions during the last 2 months the server has locked up and clients have lost connections. Power is on at  server, but it is unresponsive... ...only way to resolve was to power off and restart server.

The common error in the various logs just prior to each event was File Replication Service Error - Event ID 13568

I  followed (I thought) the instructions on the error (See Below), but I set the the registry entry to 1 per the following excerpt:


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

After doing so i got two information messages (13533 and 13516) and assumed it was resolved.

However after reading more articles, it appears that registry values should be D4 for a stand alone server????

Please advise as to the exact proper registry entries when in a single-server environment. As continued lock-ups are hazardous to my career!!!  Each time the server has locked up it has caused havoc at the restaurant!

SEE FULL ERROR DETAILS BELOW:


Event Type:      Error
Event Source:      NtFrs
Event Category:      None
Event ID:      13568
Date:            6/9/2010
Time:            11:00:31 PM
User:            N/A
Computer:      SBS-SERVER
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   : "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.

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

Distinguished Expert 2018
Commented:
The registry key you mention is good to correct long-standing journal-wrap errors, but the fact that these *only* appear right before a hard lockup makes me believe that you are not in that situation.

This sounds like a hardware issue that is causing the journal in NTFS to become corrupt and it repairs itself when you reboot, so the errors are not ongoing. Journal wrap errors will NOT cause a server to freeze. They just cause problems when replicating to another domain controller (either in a multi-DC configuration or during a migratoin).

I'd look at hardware. Failing hard drive or RAID controller are the most likely culprits since journalling is hard drive related.  But bad RAM is not out of the question.
AlisanneLead Condultant

Author

Commented:
Any suggestions as how to determine the most likely culprit? This is a 4-month old server.we had issues on install that seamed to be POS software related, then 3 lockups about 5 weeks ago, then smooth sailing until it froze twice yesterday...

This is a 6am to 11pm shop, so down time is hard to obtain, and i need to be focussed!

Thank you!

Distinguished Expert 2018

Commented:
Stress testing is usually the only way to pinpoint failures like this. And those require downtime.

Most of your LiveCD implementations have burn-in tools onboard.  Knoppix did last I checked. I built a custom WinPE bootable CD with tools. They would help you.

Commented:
It looks to be virtual memory error.

Run procmon, adplus & poolmon(used for memory leak).

It looks to be memory leak issue as server works OK & on rebooting it works fine.

http://support.microsoft.com/kb/286350

The above error is for file replication service & you can correct it with below article.

http://support.microsoft.com/kb/316790

Stop the File Replication service on the domain controller.
Start  Registry Editor (Regedt32.exe).
Locate and then click the BurFlags  value under the following key in the registry:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process  at Startup
On the Edit menu, click DWORD,  click Hex, type D4, and then  click OK.
Quit Registry Editor.
Move data out of  the PreExisting folder.
Restart the File Replication Service.

Take backup of sysvol first.

AlisanneLead Condultant

Author

Commented:
I have additional information:

I am getting UsrEnv Errors 1030 and 1058 as well as NetBT4319.

System is running fine and I can not find any dup computer or ip addresses on network (Only five PCs).

But, all POS units login as same user...

I will try "Run procmon, adplus & poolmon(used for memory leak)" after closing tonight and see what i get.

Any other ideas?

Thank so much!
AlisanneLead Condultant

Author

Commented:
Please clarify:

Which "PreExisting folder?

Commented:
Its inside sysvol & its hidden.

Commented:
Pre-existing data folder
=================

The pre-existing folder, named NtFrs_PreExisting___See EventLog, is an optional folder that is located under the replica root. If the pre-existing data folder is present on a replica member, FRS created it after one of the following events:

The server was added to a replica set but the server already had one or more files in the shared folder that became the replica tree. In this case, FRS moved that data into the pre-existing data folder and then replicated the replica tree from one of the upstream partners to the new member.

The replica member had a nonauthoritative restore (also called D2) performed on it by an administrator. This process is used to bring a replica member back up to date with its partners after problems such as assertions in the FRS service, corruption of the local FRS Jet database, journal wrap errors, and other replication failures. When you perform a nonauthoritative restore on a server, FRS moves the existing data in the replica tree to the pre-existing data folder and then receives the replica tree from one of the upstream partners.

The server was prestaged before it was added to the replica set. During the prestaging process, files in the replica tree are temporarily moved from the replica tree to the pre-existing data folder. For more information about the prestaging process, see “How Prestaging Works” later in this section.

Only one pre-existing data folder can exist at a time. If one of the previously listed events occurs, causing the pre-existing data folder to be created, and then another one of the events occurs, the previous pre-existing data folder is deleted and replaced with another pre-existing data folder.

-------------------------------------------------------------------------------------------------------------------------------------

Just check the below link
http://www.eventid.net/display.asp?eventid=13568&eventno=1743&source=NtFrs&phase=1

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.