File Replication Service is initializing the system volume with data from another domain controller

[Fritz]

"File Replication Service is initializing the system volume with data from
another domain controller. Computer SERVERNAME cannot become a domain
controller until this process is complete. The system volume will then be
shared as SYSVOL.

To check for the SYSVOL share, at the command prompt, type:
net share

When File Replication Service completes the initialization process, the
SYSVOL share will appear.

The initialization of the system volume can take some time. The time is
dependent on the amount of data in the system volume, the availability of
other domain controllers, and the replication interval between domain
controllers. "

There is also another message in the Event Log saying to delete
C:\WINNT\NETLOGON.CHG but I haven't been able to do so. It says that the
file is being used even though the Netlogon service is stopped. I even
tried the SafeMode. Still it says that the file is being used.

Help!

Thanks!

 

[ptwilliams]

What are you asking us here? This is a standard message. Another message
will follow shortly stating that the file replication service is no longer
stopping this machine from being a DC (I can't remember the event IDs I'm
afraid).
Only if after some time does this message not appear -and you get other
warnings and errors- is this is problem. Then you will need to investigate
and troubleshoot accordingly. But in order for us to help you with that,
we'll need the Event IDs so we can try and work out what is wrong.

There is also another message in the Event Log saying to delete
C:\WINNT\NETLOGON.CHG but I haven't been able to do so. It says that the
file is being used even though the Netlogon service is stopped. I even
tried the SafeMode. Still it says that the file is being used.

Deny SYSTEM full control and reboot. Then delete the file and reboot again.

--

Paul Williams

http://www.msresource.net/
http://forums.msresource.net/

 

[Fritz]

The NETLOGON and the SYSVOL shares aren't there. It doesn't look like the
system is authenticating users either.

 

[Guest]

Ah...that changes things...

Best thing to do is perform a non-authorative restore of SYSVOL. To do
this, stop NtFrs, drill down to the following registry key:

HKLM\ SYSTEM\ CurrentControlSet\ Services\ NtFrs\ Parameters\
Backup/Restore\ Process at Startup

and add a DWORD value called BurFlags. Set the value to D2 and restart NtFrs.

Go make a cup of coffee...

Once you've drank your coffee, check the NtFrs logs for the warning event
that says that NtFrs is no longer stopping your server from being a DC. Then
run dcdiag /v and netdiag /v and peruse the output for errors and warnings.
Post the relevant bits here...

 

[Fritz]

That didn't do the trick. It looks like the SYSVOL restore is complete and
now I have this message in the Event Log:


"The File Replication Service is having trouble enabling replication from
\\otherDCname.domainname.com to serverName for c:\winnt\sysvol\domain using
the DNS name \\otherDCname.domainname.com. FRS will keep retrying.
Following are some of the reasons you would see this warning.

[1] FRS can not correctly resolve the DNS name \\otherDCname.domainname.com
from this computer.
[2] FRS is not running on \\otherDCname.domainname.com.
[3] The topology information in the Active Directory for this replica has
not yet replicated to all the Domain Controllers.

This event log message will appear once per connection, After the problem
is fixed you will see another event log message indicating that the
connection has been established. "

Replmon is showing that the DCs are replicating correctly though.

 

[ptwilliams]

After a bit of waiting, do you get the other event that says it's enabled
SYSVOL replication?

How many of these events are you seeing?

 

[Fritz]

I have two instances of the above warning in the Event Log. Those are the
last two Event in the FRS log. I'm not getting the even about enabled
SYSVOL replication.

 

[ptwilliams]

Restart NtFrs again, give it about a bunch of minutes and check again. If
all's not well, we'll have to do some more digging...

 

[Fritz]

BurFlags got reset to 0 after the restore. Should I change it again before
restarting NTFRS?

Thanks for all your help!

 

[Fritz]

Still having trouble getting this to work. Here's repadmin output:

Show Connection Objects
CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=domainname,DC=com:
PDCSERVER\a474a200-d428-48df-be5f-2012de7253a4
enabledConnection: TRUE
fromServer: Default-First-Site-Name\BDCSERVER
TransportType: intrasite RPC
options: isGenerated
ReplicatesNC: CN=Configuration,DC=domainname,DC=com
Reason: RingTopology
ReplicatesNC: CN=Schema,CN=Configuration,DC=domainname,DC=com
Reason: RingTopology
ReplicatesNC: DC=domainname,DC=com
Reason: RingTopology
whenChanged: 20050402210930.0Z
whenCreated: 20050402204929.0Z
BDCSERVER\2e8b8376-2027-47b5-a746-c608eda56436
enabledConnection: TRUE
fromServer: Default-First-Site-Name\PDCSERVER
TransportType: intrasite RPC
options: isGenerated
ReplicatesNC: CN=Configuration,DC=domainname,DC=com
Reason: RingTopology
ReplicatesNC: CN=Schema,CN=Configuration,DC=domainname,DC=com
Reason: RingTopology
ReplicatesNC: DC=domainname,DC=com
Reason: RingTopology
whenChanged: 20050402210818.0Z
whenCreated: 20050402205318.0Z
Default-First-Site-Name\BDCSERVER
DSA Options : (none)
objectGuid : bf5f3079-8a8e-44d2-a998-fbee16558a2d
invocationID: 32e49649-40b3-471b-91c2-3ef6dcabb600

==== INBOUND NEIGHBORS ======================================

CN=Schema,CN=Configuration,DC=domainname,DC=com
Default-First-Site-Name\PDCSERVER via RPC
objectGuid: 6432f664-565e-40bf-a7ba-cd48c8750881
Last attempt @ 2005-04-07 11:51.06 was successful.

CN=Configuration,DC=domainname,DC=com
Default-First-Site-Name\PDCSERVER via RPC
objectGuid: 6432f664-565e-40bf-a7ba-cd48c8750881
Last attempt @ 2005-04-07 12:39.31 was successful.

DC=domainname,DC=com
Default-First-Site-Name\PDCSERVER via RPC
objectGuid: 6432f664-565e-40bf-a7ba-cd48c8750881
Last attempt @ 2005-04-07 12:44.03 was successful.

==== OUTBOUND NEIGHBORS FOR CHANGE NOTIFICATIONS ============

CN=Schema,CN=Configuration,DC=domainname,DC=com
Default-First-Site-Name\PDCSERVER via RPC
objectGuid: 6432f664-565e-40bf-a7ba-cd48c8750881

CN=Configuration,DC=domainname,DC=com
Default-First-Site-Name\PDCSERVER via RPC
objectGuid: 6432f664-565e-40bf-a7ba-cd48c8750881

DC=domainname,DC=com
Default-First-Site-Name\PDCSERVER via RPC
objectGuid: 6432f664-565e-40bf-a7ba-cd48c8750881

 

[ptwilliams]

No, that's to be expected.

 

[ptwilliams]

Are you still getting the warnings that it's having trouble replicating with
a partner?

Did you get the message that the SYSVOL had initialised?

Are you seeing replication issues in the event logs?

 

[Fritz]

1. Yes, I'm still getting this same message over and over again:
"The File Replication Service is having trouble enabling replication from
\\PrimaryDC.domainname.com to BackupDC for c:\winnt\sysvol\domain using the
DNS name \\PrimaryDC.domainname.com. FRS will keep retrying.
Following are some of the reasons you would see this warning.

[1] FRS can not correctly resolve the DNS name \\PrimaryDC.domainname.com
from this computer.
[2] FRS is not running on \\PrimaryDC.domainname.com.
[3] The topology information in the Active Directory for this replica has
not yet replicated to all the Domain Controllers.

This event log message will appear once per connection, After the problem
is fixed you will see another event log message indicating that the
connection has been established. "

2. No, I didn't get a message that SYSVOL had initialized.
3. Only the one above.