A Microsoft Windows Server 2003 pre-Service Pack 1 (SP1)
hotfix is available that includes updates to the File Replication service (FRS)
to improve the robustness of the service. This article describes the changes to
FRS that are included in the hotfix, and it contains information about how to
obtain the hotfix.
Key Terms and Concepts That Are Used in this Article
- Change Order (Also Known as CO)
When a change is made to a file or folder on a replica
member, the information about that change (such as the name of the file or the
ID of the member) that is used to construct a message is named a "change
order." The change order is sent to the member's outbound partners. If the
outbound partners accept the change, the partners request the associated
staging file. After the change is installed on their individual replica tree,
they each propagate the change order to their outbound partners. - File GUID
The file GUID identifies the file or folder. It is
created and managed by the replication service. The file GUID, with the
replication version number and event time, is stored in the File ID table in
the FRS database. Corresponding files and folders across all replica-set
members have the same file GUID. - File ID Table
The File ID table is a table in the FRS database that
contains an entry with version and identity information for each file and
folder in the replica tree. - Identity-Based Replication
All objects in a replica tree are assigned a unique ID.
In FRS, the NTFS object ID attribute that contains a 16-byte GUID is used. The same object
on all replica members has the same object ID. This functionality permits
unambiguous location of the object by using the object's GUID and the
corresponding parent GUID. - Replica Partner
The immediate upstream and downstream partners of a
replica member are referred to as its replication partners. Upstream partners
are also referred to as inbound partners. Downstream partners are also referred
to as outbound partners. - Replica Set
In FRS, two or more computers that are configured to
replicate the contents of a folder are known as a replica set. The individual
computers are referred to as replica members. - Update Sequence Number (USN)
NTFS maintains a monotonically increasing sequence
number for each volume. This number is the update sequence number (USN). Each
time a modification is made to a file on the volume, the USN is incremented.
- Version Vector
This vector is a vector of USNs, where there is one
entry per member of a replica set. All change orders carry the originator GUID
of the originating member and the associated USN. As each member of a replica
set receives the update, it tracks the USN in a vector slot that is assigned to
the originating member. This vector describes how up-to-date the replica tree
is with respect to each member. The version vector is then used to filter
updates from inbound partners that may have already received the update. The
version vector is also delivered to the inbound partner when the two members
join. When a new connection is created, the version vector is used to scan the
File ID table for more recent updates that are not seen by the new outbound
partner.
FRS is a multi-threaded, multi-master replication engine.
Windows Server 2003 and Windows 2000-based domain controllers and servers use
FRS to replicate Group Policy settings and logon scripts for client computers.
FRS can also replicate content between Windows Server 2003 and Windows
2000-based servers that host the same fault-tolerant Distributed File System
(DFS) roots or child node replicas.
List of Issues That Are Resolved in This Hotfix
The hotfix described in this article resolves the following
issues:
- "<StuInstallRename: 420: 1430: S3: 00:00:00> :: CoG 91cc0f81, CxtG 847d1e73, FV 2, FID 00010000 00000026, FN: DirName , [Rename failed (ERROR_ACCESS_DENIED)]" Error Message
This error message may occur in situations when a change
order of an existing file is an implicit rename change order, and it is not
checked for a morph conflict. An incoming change order becomes an implicit
rename change order after it is typically checked for name conflicts. However,
when the change order of an existing file is not checked for a morph conflict
and a morph is not generated, the change order still has the "DirName" name in
Install. As a result, the rename operation cannot be processed during a file
installation because it is blocked by "DirName". - Incomplete Information About Event ID 13508 Warning Messages
Event ID 13508 warning messages that are logged in the
event log contain incomplete information. You may not be able to understand
what you have to do when this message appears in the log. - Event ID 13506 Errors Are Logged and FRS Stops Intermittently Stops Responding
FRS may stop responding every few minutes, and entries
that are similar to the following are logged to the event log:
Error 13505 STOPPED_ASSERT
Info 13502 STOPPING
Error 13555 IN_ERROR_STATE STRINGS:
SystemRoot\ntfrs\jet
Error 13506 ASSERT
STRINGS: ChgOrdDispatch: | 7340 | COE_FLAG_ON(ChangeOrder,
COE_FLAG_NEED_DELETE)
Warn 13508 LONG_JOIN STRINGS: COMP1 | COMP2
Info 13501 STARTING
Error 13505 STOPPED_ASSERT
Info 13502
STOPPING
Error 13555 IN_ERROR_STATE
- Replication Stops Responding (Hangs) When Vvjoin Staging Generation for Large Files Takes a Long Time
When vvjoin staging file generation for large files
takes a long time to complete, fetch request timeouts may occur. This may cause
replication to stop responding (hang). - Sysvol Is Marked As Ready on a Domain Controller Before File System Policy Exists in the Replica Set Root
In some situations, you may find that the Sysvol on a
server that is recently promoted to a domain controller is marked as ready
before file system policy exists in the replica set root. - Memory Leak Condition in Windows Management Instrumentation (WMI)
A handle leak in FRS may cause a memory leak condition
in WMI.
Updates That Are Included in This Hotfix
The hotfix described in this article adds the following new
functionality to FRS:
Hotfix Information
A supported feature that modifies the product's default behavior is now available from Microsoft, but it is only intended to modify the behavior that this article describes. Apply it only to systems that specifically require it. This feature may receive additional testing. Therefore, if the system is not severely affected by the lack of this feature, we recommend that you wait for the next Windows Server 2003 service pack that contains this feature.
To obtain this feature immediately, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Prerequisites
No prerequisites are required.
Restart Requirement
You must restart your computer after you apply this
hotfix.
Hotfix Replacement Information
This hotfix does not replace any other hotfixes.
File Information
If the server to which you apply this fix has an installed version of the Windows Server 2003 Support Tools, you must replace NTFRSUTL.EXE in the Support Tools folder with the new version of NTFRSUTL.EXE. Additionally, you can delete the version of NTFRSUTL.EXE in the Support Tools folder because the new version is installed into %systemroot%\system32.
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the
Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name
-------------------------------------------------------
23-Jan-2004 01:49 5.2.3790.121 772,096 Ntfrs.exe
23-Jan-2004 01:49 5.2.3790.121 57,856 Ntfrsapi.dll
23-Jan-2004 01:49 5.2.3790.121 21,504 Ntfrsprf.dll
23-Jan-2004 01:49 5.2.3790.123 9,728 Ntfrsutl.exe
This hotfix increases the default journal size from 128 MB to 512
MB. You must either manually set the appropriate registry key to prevent the
increase or make sure that you have sufficient free hard disk space to fit the
size increase.
For additional information
about FRS registry entries, click the following article number to view the article in the Microsoft Knowledge Base:
221111
(http://support.microsoft.com/kb/221111/
)
Description of FRS entries in the
registry
Back to the top
