Hi Steve,
I did some research and found the solution which was given in Microsoft
Knowledge Base Article - 312862
Go thru the article at
http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q312862#appliesto
Steve, I have listed only few points since the artilce is very huge, better
view in html page in the above URL. Please let me know if you have any
specific questions on this regard.
SUMMARY
==========
File Replication service (FRS) is a multi-threaded, multi-master
replication engine that replaces the LMREPL service in Microsoft Windows NT
3.x and in Microsoft Windows NT 4.0. Windows 2000-based and Windows Server
2003-based domain controllers and servers use FRS to replicate system
policy and logon scripts for clients that run Windows Server 2003 and
earlier. You can also use FRS to replicate files and folders between
Windows 2000-based and Windows Server 2003-based servers that host the same
fault-tolerant Distributed File System (DFS) root or child replicas.
This article describes:
How the deletion of FRS objects and FRS attributes occurs.
How to detect missing Server-Reference attributes and member objects in
SYSVOL replica sets.
How to repair missing attributes by using null Server-Reference attributes
as an example.
How to repair missing objects by using missing member objects as an example.
How to repair missing connection objects by using existing connection
objects as an example.
Detecting Null Server-Reference Attributes
======================================
When FRS replicates the contents of the SYSVOL folder, FRS uses connection
objects that are located in the configuration partition of Active
Directory. You can manually create these connection objects; however, KCC
automatically generates the connection objects by default. An NTDS Settings
object is one of two critical objects that distinguish domain controllers
from other computer accounts in Active Directory. Among other things, the
NTDS Settings object is the parent container for inbound connections from
other domain controllers in the domain and in the forest.
The domain name path of the Server-Reference attribute on FRS member
objects becomes null (empty) if you delete NTDS Settings objects from the
Configuration partition in Active Directory. This behavior is detected or
recorded by the following tools or logs:
The output of the ntfrsutl ds command: MEMBER: ARRENC1
DN : cn=DC1,cn=domain system volume (sysvol share),cn=file
replication service...
Guid : c8b10337-4e63-402c-b4a3c1f387284b7d
Server Ref : (null)
Computer Ref : cn=DC1,ou=domain controllers,dc=a,dc=com
Cracked Domain : a.com
Cracked Name : 00000002 A\DC1$
Cracked Domain : a.com
Cracked Name : fffffff4
S-1-5-21-1908895637-3267214997-978106868-1105
Computer's DNS : DC1.a.com
WARN - DC1 lacks a settings reference
Event 13562 in the FRS event log on computers that are running Service Pack
2 (SP2) or later:
Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13562
Date: mm/dd/yyyy
Time: hh:mm:ss AM|PM
User: N/A
Computer: computername
Description:
Following is the summary of warnings and errors encountered by File
Replication service while polling the Domain Controller dc1.a.com for FRS
replica set configuration information.
The nTFRSMember object cn=dc1,cn=domain system volume (sysvol
share),cn=file replication service,cn=system,dc=a,dc=com has a invalid
value for the attribute ServerReference.
Errors in the FRS debug logs:
NtFrs_000X.log:FrsNewDsGetSysvolCxtions: S0: HH:MM:SS
S: WARN - Member
(cn=DC1,cn=domain system volume (sysvol share),cn=file replication
service,cn=system,dc=a,dc=com) of sysvol replica set lacks server
reference; skipping
Repairing the Null Server-Reference Attributes
=======================================
You can use LDP.exe or ADSIedit.msc to repair missing Server-Reference
attributes. These tools repair the attribute by resetting the value in the
configuration naming context or partition to the distinguished name (DN) of
the server's NTDS Settings object. To repair null Server-Reference
attributes:
Use one of the following methods to locate the DN path of the NTDS Settings
object for the computer that has the missing (null) Server-Reference
attribute:
In LDP or ADSIedit, copy the DN path of the NTDS Settings object from the
Configuration container in the root domain of the forest to Clipboard.
-or-
From the domain partition of Active Directory, copy the value of the
Server-Reference attribute from a healthy domain controller to Clipboard.
This domain controller needs to be in the same Active Directory domain and
site as the broken computer, otherwise you have to edit the DN path.
Locate the member object that has the null Server-Reference attribute:
Start ADSIedit. In the Domain partition of Active Directory, locate the
member object (nTFRSMember) that lacks the settings reference. The DN path
is: DN Path ObjectClass
DC=A,DC=COM Root Domain NC
CN=SYSTEM, Container
CN=File Replication Service nTFRSSettings
CN=Domain System Volume (SYSVOL share) nTFRSReplicaSet
CN=DC1 nTFRSMember
CN=DC2 nTFRSMember
Right-click the member object that has the null Server-Reference attribute,
and then click Properties.
Edit the value for the Server-Reference attribute:
Configure the Attributes tab in ADSIedit:
Select which properties to view: Set this to OPTIONAL.
Select a property to view: Click the Server-Reference property.
Under Edit Attribute, paste the DN path of the NTDS Settings object from
Clipboard. The DN path for an NTDS Settings should have the following
format
CN=NTDS Settings, CN=Computer name,CN=Site name, CN=Sites,
CN=Configuration, DC=Root domain of forest,DC=COM
where Computer name is the name of the domain controller with the null
Server-Reference attribute and where Site name is the name of the Active
Directory site where that server's NTDS Settings object lives.
Click SET, and then confirm the value that is written to Active Directory.
Wait or force FRS to poll Active Directory:
FRS polls Active Directory at regular intervals to discover configuration
changes. You can use either of the following methods to have polling occur:
Use the net stop ntfrs command to stop FRS, and then use the net start
ntfrs command to restart FRS.
-or-
Use the ntfrsutl poll /now command line to force FRS to poll:
Wait until the short or long polling interval expires. This is a five
minute default on domain controllers.
FRS registers the change during its next DS polling cycle. Monitor the FRS
event log for replication by using the output from the ntfrsutl sets
command.
Note: Please look at the above URL for detailed step by step instructions.
Thanks,
(e-mail address removed)
This posting is provided "AS IS" with no warranties, and confers no rights.
