Microsoft KB Archive/893092

= A replication may only occur on one FRS replica set when the FRS tries to replicate files from one FRS replica set to another FRS replica set in Windows Server 2003 =

Article ID: 893092

Article Last Modified on 7/24/2007

-

APPLIES TO


 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
 * Microsoft Windows Server 2003, Web Edition
 * Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems

-





SYMPTOMS
The File Replicaton service (FRS) tries to replicate files from another replica set member that is in the following state:

Config Flags: Multimaster Seeding Online

This replication does not succeed. Also, you receive the following message on one of the FRS replica set servers if you use the Connstat.cmd tool:

Config Flags: Multimaster Seeding Online

Replica partners have a &quot;LastJoinTime&quot; date and time stamp of &quot;Mon Jan 1, 1601 00:00:00.&quot; Also, either of the following log connection status entries is logged continuously in the ntfrs_0000.log debug logs: Paused InitSync

InitSyncHung

Note These symptoms may also occur on a Microsoft Windows 2000-based computer. For more information about a workaround for Windows 2000-based computers, see the &quot;Workaround for Windows 2000-based computers&quot; section.



CAUSE
These symptoms occur because a connection from one of the replica partners has joined but has not cleared the “InitSync” flag.



Service pack information
To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

889100 How to obtain the latest service pack for Windows Server 2003

Hotfix information
A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

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
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 item in Control Panel. Windows Server 2003, Itanium-based versions Date        Time   Version            Size    File name     Platform -  26-Jan-2005  09:39  5.2.3790.258    1,781,248  Ntfrs.exe     IA-64 26-Jan-2005 10:01  5.2.3790.258      772,096  Wntfrs.exe      x86

Windows Server 2003, x86-based versions

Date        Time   Version            Size    File name --  27-Jan-2005  02:01  5.2.3790.258      772,096  Ntfrs.exe



STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the &quot;Applies to&quot; section.

This bug was corrected in Windows Server 2003 Service Pack 1.



The hotfix has to be installed on the server in the following state:

Config Flags: Multimaster Seeding Online



Workaround for Windows 2000-based computers
To work around this problem on the Windows 2000-based domain controllers that exhibit the symptoms that are described in the &quot;Symptoms&quot; section, follow these steps:  Increase frs debug logging levels as noted in the following list:  Increase the frs debug level to 4. Increase the number of frs debug logs to 25 or more. Increase the number of log messages to 25000.</li></ul>

Note The registry entries that control NTFRS logging are located in the following registry subkey:

</li> After you complete step 1, allow for a full replication cycle to occur and for the frs debug logs to fill before you continue with this procedure.</li> Run the File Replication Service Diagnostics Tool (FRSDiag.exe) by using default settings on the Windows 2000-based domain controllers. To obtain this tool, visit the following Microsoft Web site:

http://www.microsoft.com/downloads/details.aspx?FamilyId=43CB658E-8553-4DE7-811A-562563EB5EBF&displaylang=en

</li> In the ntfrs_000 n.log files, find the &quot;InitSyncStartJoin&quot; string. To do this, run the following command at a command prompt to create an ntfrs_out.txt file:

find /I “InitSyncStartJoin” ntfrs_00**.log > ntfrs_out.txt

</li>  In the ntfrs_out.txt file, look for connections that are currently replicating and that still have the &quot;InitSync&quot; flag set in the “Flags” section of the output.

Note Use the connstat.txt from the frsdiag report to identify connections that have replicated or that have not replicated. Cross reference these connections against the connections that have the “InitSync” flag set.

Example of ntfrs_out.txt output <InitSyncStartJoin:            3556:  1548: S4: 16:00:09>    Cxtion: FROM-ROOTDC1 (XXXXXXXX-XXXX-XXXX-XXXXXXXXXXXXXXXX)

<InitSyncStartJoin:            3556:  1548: S4: 16:00:09>       Partner      : ROOTDC1 (XXXXXXXX-XXXX-XXXX-XXXXXXXXXXXXXXXX)

<InitSyncStartJoin:            3556:  1548: S4: 16:00:09>       PartDnsName  : rootdc1.contoso.com

<InitSyncStartJoin:            3556:  1548: S4: 16:00:09>       PartSrvName  : rootdc1$

<InitSyncStartJoin:            3556:  1548: S4: 16:00:09>       PartPrincName: rootdc1$

<InitSyncStartJoin:            3556:  1548: S4: 16:00:09>       PartSid      : S-X-X-XX-XXXXXX-XXXXXXXXX-XXXXXXXXXX-XXXXXX

<InitSyncStartJoin:            3556:  1548: S4: 16:00:09>       OrigGuid     : 00000000-0000-0000-0000000000000000

<InitSyncStartJoin:            3556:  1548: S4: 16:00:09>       State        : 7

<InitSyncStartJoin:            3556:  1548: S4: 16:00:09>       Flags        : c00000c0 Flags [JoinGuidValid UnJoinGuidValid InitSync TriggerSched ]

<InitSyncStartJoin:            3556:  1548: S4: 16:00:09>       CxtionOptions: 00000000 Flags [<Flags Clear>]

<InitSyncStartJoin:            3556:  1548: S4: 16:00:09>       Inbound      : TRUE

<InitSyncStartJoin:            3556:  1548: S4: 16:00:09>       JrnlCxtion   : FALSE

<InitSyncStartJoin:            3556:  1548: S4: 16:00:09>       PartnerAuth  : 0

<InitSyncStartJoin:            3556:  1548: S4: 16:00:09>       TermCoSn     : 0

<InitSyncStartJoin:            3556:  1548: S4: 16:00:09>       JoinCmd      : 0x00000000

<InitSyncStartJoin:            3556:  1548: S4: 16:00:09>       CoCount      : 0

<InitSyncStartJoin:            3556:  1548: S4: 16:00:09>       CommQueue    : 11

<InitSyncStartJoin:            3556:  1548: S4: 16:00:09>       CoPQ         : 00000000

<InitSyncStartJoin:            3556:  1548: S4: 16:00:09>       UnjoinTrigger: 0

<InitSyncStartJoin:            3556:  1548: S4: 16:00:09>       UnjoinReset  : 0

<InitSyncStartJoin:            3556:  1548: S4: 16:00:09>       Comm Packets : 21876

<InitSyncStartJoin:            3556:  1548: S4: 16:00:09>       PartnerMajor : 0

<InitSyncStartJoin:            3556:  1548: S4: 16:00:09>       PartnerMinor : 7

<InitSyncStartJoin:            3556:  1548: S4: 16:00:09>       LastSndStatus: ERROR_SUCCESS

<InitSyncStartJoin:            3556:  1548: S4: 16:00:09>       NoFailedSnds : 0

<InitSyncStartJoin:            3556:  1548: S4: 16:00:09>       Schedule

<InitSyncStartJoin:            3556:  1548: S4: 16:00:09>          Day 1: 101010101010101010101010

<InitSyncStartJoin:            3556:  1548: S4: 16:00:09>          Day 2: 101010101010101010101010

<InitSyncStartJoin:            3556:  1548: S4: 16:00:09>          Day 3: 101010101010101010101010

<InitSyncStartJoin:            3556:  1548: S4: 16:00:09>          Day 4: 101010101010101010101010

<InitSyncStartJoin:            3556:  1548: S4: 16:00:09>          Day 5: 101010101010101010101010

<InitSyncStartJoin:            3556:  1548: S4: 16:00:09>          Day 6: 101010101010101010101010

<InitSyncStartJoin:            3556:  1548: S4: 16:00:09>          Day 7: 101010101010101010101010 </li> Use the &quot;Active Directory Sites and Services&quot; snap-in to delete any connection objects that are replicating and that have the “InitSync” flag set.</li> Connections that were previously waiting for InitSync will start joining and replicating on next replicating cycle.

Note On domain controllers that have slow network connection issues or other performance issues, it may take more than one replication cycle to join all incoming connections. Also, this procedure may have to be repeated if the symptoms that are described in the &quot;Symptoms&quot; section still persist.</li> When the domain controller is replicating from all replication partners, any connection objects that were deleted can be added back or re-created.</li></ol>

<div class="references_section">