FRS relies on essential containers, objects, and attributes
stored in Active Directory and replicated among domain controllers
in a given domain. Critical objects include FRS member and
subscriber objects. Optional attributes include the Schedule
attribute, the FRS-File-Filter attribute, the FRS-Folder-Filter
attribute, and the FRS database location. For more information
about these objects, see article 296183, "Overview of Active
Directory Objects That Are Used by FRS" at http://support.microsoft.com/?id=296183
To troubleshoot this problem, do the following:
Check for existence of FRS event ID 13562 or "Missing Subscriber Object" in
FRSDiag.txt.
Run FRSDiag, and then run TopChk on NTFRS_DS.txt. For
instructions, see TopChk
Remarks.
In Ntfrs_ds.txt (generated by FRSDiag), find which objects are
missing.
Do one of the following:
If referenced server still exists, follow the steps listed
article 312862, "Recovering Missing FRS Objects and FRS Attributes
in Active Directory" at http://support.microsoft.com/?id=312862.
If the referenced server no longer exists: use Metadata Cleanup
to remove the referenced server. Use Replmon to trigger replication
after the deletion, and run TopChk afterward. For more information,
see article 216498, "HOW TO: Remove Data in Active Directory After
an Unsuccessful Demotion" at http://support.microsoft.com/?id=216498.