NtFrs not replicating 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
 
you need to make sure the time zones are correct. Windows will translate
the time into UTC on both ends and that is what it goes by. each server
needs to be set for the correct time zone. When you sync to a external time
source you time will be given in that time zone you have set on the server.
as for only being out 30 minutes i am not sure unless that was atleast 30
minutes.
 
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
 
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.

This should reinit the FRS and reset the file times.
It's worth a try before a full rebuild no?

(e-mail address removed)

This posting is provided "AS IS"
with no warranties, and confers no rights
--------------------
| From: "Damien Phillips" <[email protected]>
| References: <#[email protected]>
<#[email protected]>
| Subject: Re: NtFrs not replicating due to time difference
| Date: Tue, 13 Jan 2004 16:02:18 -0000
| Lines: 94
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
| Message-ID: <[email protected]>
| Newsgroups: microsoft.public.win2000.active_directory
| NNTP-Posting-Host: mail.lawpack.co.uk 217.154.48.38
| Path:
cpmsftngxa07.phx.gbl!cpmsftngxa10.phx.gbl!TK2MSFTNGXA05.phx.gbl!TK2MSFTNGP08
..phx.gbl!TK2MSFTNGP12.phx.gbl
| Xref: cpmsftngxa07.phx.gbl microsoft.public.win2000.active_directory:62518
| X-Tomcat-NG: microsoft.public.win2000.active_directory
|
| 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
|
| | > you need to make sure the time zones are correct. Windows will
translate
| > the time into UTC on both ends and that is what it goes by. each server
| > needs to be set for the correct time zone. When you sync to a external
| time
| > source you time will be given in that time zone you have set on the
| server.
| > as for only being out 30 minutes i am not sure unless that was atleast
30
| > minutes.
| >
| > --
| > HTH
| >
| > Paul McGuire
| >
| >
| >
| > | > > 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
| > >
| > >
| > >
| >
| >
|
|
|
 
Thanks for that.

As the servers had only just been installed, I had them rebuilt anyway. It
just delayed the switch from old network to new network by a day.

Damien
 
Back
Top