Select the product you need help with
FRS Event 13567 Is Recorded in the File Replication Service Event Log After You Install Service Pack 3Article ID: 315045 - View products that this article applies to. This article was previously published under Q315045 IMPORTANT: This article contains information about modifying the registry. Before you
modify the registry, make sure to back it up and make sure that you understand how to restore
the registry if a problem occurs. For information about how to back up, restore, and edit the
registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986
(http://support.microsoft.com/kb/256986/EN-US/
)
Description of the Microsoft Windows Registry
SYMPTOMS
After you install Windows 2000 Service Pack 3 (SP3), the following event may be recorded in the File Replication Service (FRS) event log:
Event Type: Warning Event Source: NtFrs Event Category: None Event ID: 13567 Date: 12/12/2001 Time: 2:03:32 PM User: N/A Computer: NA-DC-01 Description: File Replication Service has detected and suppressed an average of %1 or more file updates every hour for the last %2 hours because the updates did not change the contents of the file. The tracking records in FRS debug logs will have a filename and event time for the suppressed updates. The tracking records have the date and time followed by :T: as their prefix. Updates that do not change the content of the file are suppressed to prevent unnecessary replication traffic. Following are common examples of updates that do not change the contents of the file. [1] Overwriting a file with a copy of the same file. [2] Setting the same ACLs on a file multiple times. [3] Restoring an identical copy of the file over an existing one. Suppression of updates can be disabled by running regedit. Click on Start, Run and type regedit. Expand HKEY_LOCAL_MACHINE, SYSTEM, CurrentControlSet, Services, NtFrs, Parameters, and create or update the value "Suppress Identical Updates to Files" to 0 (Default is 1) to force identical updates to replicate. CAUSE
FRS was updated in SP3 to detect and suppress duplicate updates. This conserves network bandwidth. Event 13567 is logged to inform the administrator that this suppression has occurred. More specifically, this event is logged when FRS detects that 15 identical updates were made to FRS replicated files within a one-hour period and this condition has occurred over 3 consecutive hours. The duplicate changes might have occurred on a single file 15 times, or 15 unique files one time each, or any combination between those two. Identical updates are changes to existing files where the MD5 checksum for the last change is identical to the previous change to that same file. Duplicate changes are common when administrators or programs make repetitive changes to FRS replicated files, which may result in excessive replication or backlogs that delay data consistency between replication partners. The above thresholds apply only to event logging. FRS suppression works continuously. FRS suppression does not apply to folders. Therefore, frequent changes to folders may affect FRS replication and staging even when suppression is turned on. Common causes of duplicate changes in FRS replicated folders include:
RESOLUTIONWARNING: If you use Registry Editor incorrectly, you may cause serious problems that may
require you to reinstall your operating system. Microsoft cannot guarantee that you can solve
problems that result from using Registry Editor incorrectly. Use Registry Editor at your own
risk. You can prevent the suppression by modifying the registry. To prevent suppressing duplicate updates:
MORE INFORMATION
For additional information about SP3 updates to FRS, click the following article number to view the article in the Microsoft Knowledge Base:
307319
(http://support.microsoft.com/kb/307319/
)
Changes to the File Replication Service
PropertiesArticle ID: 315045 - Last Review: March 2, 2007 - Revision: 3.2
| Article Translations |


Back to the top








