NtFrs Unable to replicate due to time difference

  • Thread starter Thread starter Damien Phillips
  • Start date Start date
D

Damien Phillips

We've recently set up two Win2k AS servers (PDC and ADC). Care was taken to
ensure that correct time zones were used, before using the windows time
service to lock them both to a uk based NTP server.

However we recieved the following error when the NtFrs tries to intialise
SYSVOL on the ADC.

----------------------------------------------------------------------------
-------------------------------------
Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13549
Date: 13/01/2004
Time: 10:45:23
User: N/A
Computer: LIBERTY
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.

The file name is: "Policies"
The connection to the partner computer is:
"DOMAIN SYSTEM VOLUME (SYSVOL
SHARE)\LIBERTY\E1C75DC3-1333-4266-B2C8-73459BE08521 <- HQ\JUSTICE$
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.
----------------------------------------------------------------------------
-------------------------------------

As far as I can tell the servers have never been more than a few seconds out
of sync with each other (or the NTP server)

Anybody got any advice?

Thanks in advance.

Damien
 
Look at the date and time properties of the Policies folder in
sysvol\domainname
Look at the created and modified dates. This is what is causing the error.

You can force FRS to reset using this article but you would want to use the
server that you set to d4 as the one with the correct info and the correct
date time on the policies folder.
315457 How to Rebuild SYSVOL and Its Content in a Domain
http://support.microsoft.com/?id=315457

289668 Advancing Time on Production Computers and the Effect on Active
http://support.microsoft.com/?id=289668
 
There seems to have been a balls up setting the bios system clock prior to
installation, and the pdc was installed at the incorrect date of 9/12/04
instead of 9/12/03, the adc was installed at the correct date of 10/12/03.

The minion who prepared the machine will be having a late night tonight
reinstalling the servers with the correct date!

Damien

Richard McCall said:
Look at the date and time properties of the Policies folder in
sysvol\domainname
Look at the created and modified dates. This is what is causing the error.

You can force FRS to reset using this article but you would want to use the
server that you set to d4 as the one with the correct info and the correct
date time on the policies folder.
315457 How to Rebuild SYSVOL and Its Content in a Domain
http://support.microsoft.com/?id=315457

289668 Advancing Time on Production Computers and the Effect on Active
http://support.microsoft.com/?id=289668

--
Richard McCall [MSFT]

"This posting is provided "AS IS" with no warranties, and confers no
rights."
Damien Phillips said:
We've recently set up two Win2k AS servers (PDC and ADC). Care was taken to
ensure that correct time zones were used, before using the windows time
service to lock them both to a uk based NTP server.

However we recieved the following error when the NtFrs tries to intialise
SYSVOL on the ADC.

--------------------------------------------------------------------------
--
-------------------------------------
Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13549
Date: 13/01/2004
Time: 10:45:23
User: N/A
Computer: LIBERTY
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.

The file name is: "Policies"
The connection to the partner computer is:
"DOMAIN SYSTEM VOLUME (SYSVOL
SHARE)\LIBERTY\E1C75DC3-1333-4266-B2C8-73459BE08521 <- HQ\JUSTICE$
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.
--------------------------------------------------------------------------
--
-------------------------------------

As far as I can tell the servers have never been more than a few seconds out
of sync with each other (or the NTP server)

Anybody got any advice?

Thanks in advance.

Damien
Click to expand...
Click to expand...
 
Back
Top