Microsoft KB Archive/253859

From BetaArchive Wiki
Knowledge Base

Article ID: 253859

Article Last Modified on 3/1/2007


  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Datacenter Server

This article was previously published under Q253859


The File Replication Service may log the following event error message:

Event ID:13526

The file replication service cannot replicate d:\winnt\sysvol\domain with the computer DC1 because the computer SID cannot be determined from the distinguished name "cn=dc1,ou=domain controller,dc=corp,dc=com" The file Replication Service will try later.
SYSVOL and DFS content is not being replicated.

For new replica domain controllers, FRS replication failures can prevent the sharing of netlogon and sysvol shares, the application of policy, and the machine registering itself in the Active Directory as a domain controller.

For existing computers, files and folders in SYSVOL or DFS replica set are inconsistent between replica members.


This problem occurs because the File Replication service polls the Active Directory at a regular interval to read FRS configuration information. During the polling, an operation is performed to resolve the SID of an FRS replication partner. The binding handle may become invalid should the bound domain controller become unreachable over the network or restart in a single polling interval (default 5 minutes).


Restart the FRS service on the computer logging the event ID 13526.


Microsoft has confirmed this to be a problem in Microsoft Windows 2000.

This problem was corrected in Windows 2000 Service Pack 2.

For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

272567 File Replication Service Improvements in Windows 2000 Service Pack 2


The FRS service logs error events every 24 hours or when restarted.

Additional query words: FRS NTFRS

Keywords: kbbug kbpending KB253859