| Event Id | 13549 |
| Source | ntfrs |
| Description | The File Replication Service is unable to replicate from a partner computer because the event time associated with the file to be replicated is too far into the future. It is 30 minutes greater than the current time. This can happen if the system time on the partner computer was set incorrectly when the file was created or updated. To preserve the integrity of the replica set this file update will not be performed or propagated further. |
| Event Information | This information from some newsgroups may help you: ------------------------------------------------------------------------------ This could possibly indicate that your FRS replication is getting backed up for some reason and the stamp on the replication packet for FRS is too old for the DC receiving it to apply it. In your position I would make sure I was on AT LEAST SP2 and preferably SP3 for all DCs as there have been many FRS fixes and then I would also doublecheck the actual time on all DCs. You can do this via script by querying the currenttime attribute on all DCs. This time is in UTC so it is time zone independent and all of the DCs should be within 5 minutes of each other. You can also try this before you do a full rebuild. 1. Stop NetLogon and FRS on the domain controller. 2. Rename the Ntfrs.jdb file in the Windir\Ntfrs\Jet folder. 3. Rename the Edb.chk file in the Windir\Ntfrs\Jet\Sys folder. 4. Rename the Edb.log file, the Res1.log file, and the Res2.log file in the Windir\Ntfrs\Jet\Log folder. 5. Restart Netlogon. 6. Restart FRS. |
| Reference Links | Advancing Time on Production Computers and the Effect on Active Directory and FRS How to rebuild the SYSVOL tree and its content in a domain |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.