Event ID/Source search
Keyword searchExample: Windows cannot unload your registry file
Event ID: 13549 Source: Ntfrs
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.
The file name is: <file> The connection to the partner computer is: "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)\SECSERVER\<domain> <- <domain> RemoteCxt"
Note: If this time difference is close to a multiple of 60 minutes then it is likely that this file may have been created or updated on the partner computer while the computer was set to the incorrect time zone when its computer time was initially set. Check that the timezone and time are correctly set on the partner computer.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is the role of File Replication Service?
What is a replica set?
Viennatech Solutions Inc.
This error occurs whenever you have a file set into an FRS folder that has a time stamp that is too far in the future (60 minutes by default). Since FRS relies on timestamps as well as its own index to ensure that the most recent file is kept and all older versions are overwritten it demands some time synchronization. If you are using a multi time zone system, ensure that the time zones are set correctly on each computer. Often when the FRS time catches up with the timestamp this error will "correct" itself.
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated