+ Post New Thread
Results 1 to 3 of 3
Windows Server 2000/2003 Thread, FRS, NTFRS in an error state, File Replication. in Technical; Hi all, This is a really long story, but to cut it short: I have noticed that our newish 2008 ...
  1. #1
    Koldov's Avatar
    Join Date
    May 2011
    Location
    Bedfordshire
    Posts
    531
    Thank Post
    110
    Thanked 56 Times in 48 Posts
    Rep Power
    40

    FRS, NTFRS in an error state, File Replication.

    Hi all,

    This is a really long story, but to cut it short:

    I have noticed that our newish 2008 server (which should be a secondary DC) has nothing replicated to it in the SYSVOL folders.

    After much Gooooooooogling found that our primary DC has the above error with the FRS service and was in an error state at the time the secondary DC was promoted.

    This FRS service has been stopped and restarted to no avail.

    Also after much more Goooooogling found that a way to restart the whole thing is to do an authoritative restore using the burflags registry key D4 on DC1.

    There is some mention about backing up the SYSVOL folder first, is this just a drag and drop or NTBACKUP procedure?

    There have been no major issues from this error so far (apart from some usernv errors) but everyone can log on and use the network /shares ok. As far as I can tell it's been like this a long time, but I know if I leave it, it will kick me in the ass one day!

    If anyone has performed this procedure can they share any info?

  2. #2
    Koldov's Avatar
    Join Date
    May 2011
    Location
    Bedfordshire
    Posts
    531
    Thank Post
    110
    Thanked 56 Times in 48 Posts
    Rep Power
    40
    Just to mention our Primary DC is Server 03.

  3. #3
    Koldov's Avatar
    Join Date
    May 2011
    Location
    Bedfordshire
    Posts
    531
    Thank Post
    110
    Thanked 56 Times in 48 Posts
    Rep Power
    40
    To let anyone who searches for this problem know how it panned out...

    Bit the bullet, stopped the ntfrs service on both servers, changed the burrflag registry on the main DC to 4, then restarted the service.
    Changed the secondary DC burrflag registry setting to 2, restarted the service.

    Went to make a coffee....

    Nicely replicated SYSVOL on the secondary DC, lovely messages in event log saying it was now a real DC!

    YMMV

    Kol

SHARE:
+ Post New Thread

Similar Threads

  1. [MDT] Including some commands in an unatttend file
    By balubeto in forum O/S Deployment
    Replies: 0
    Last Post: 16th August 2012, 10:04 AM
  2. File replication service in Svr 2003 sp 3
    By Hedghog in forum Windows
    Replies: 2
    Last Post: 1st October 2008, 05:24 PM
  3. Replies: 4
    Last Post: 19th September 2008, 11:06 AM
  4. File Replication error on W2k servers
    By randle in forum Windows
    Replies: 0
    Last Post: 21st July 2008, 10:42 AM
  5. Office error: This file could not be found
    By webman in forum Windows
    Replies: 2
    Last Post: 17th May 2006, 01:47 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •