File Replications Service Errors

[Brandon Cramer]

What does this mean? I'm pretty sure I'm having a
replication problem with our domain controllers.

Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13562
Date: 1/21/2004
Time: 6:34:43 PM
User: N/A
Computer: MCC-DC2
Description:
Following is the summary of warnings and errors
encountered by File Replication Service while polling the
Domain Controller mcc-dc2.molalla.com for FRS replica set
configuration information.


What can I do to fix this?

Thanks,

Brandon

 

[Jason Robarts [MSFT]]

Are there any other FRS errors and warnings in the event log? Posting them
may give a clue.

In general
http://www.microsoft.com/windowsserver2003/technologies/fileandprint/file/dfs/tshootfrs.mspx
has resources on triaging FRS replication issues.

Jason

 

[Brandon Cramer]

No this is the only error that I'm getting.

Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13562
Date: 1/28/2004
Time: 1:35:06 PM
User: N/A
Computer: MCC-FSMO
Description:
Following is the summary of warnings and errors
encountered by File Replication Service while polling the
Domain Controller mcc-fsmo.molalla.com for FRS replica
set configuration information.

The nTDSConnection object cn=mcc-fsmo,cn=ntds
settings,cn=mcc-dc2,cn=servers,cn=mcc-
site,cn=sites,cn=configuration,dc=molalla,dc=com is
conflicting with cn=0996ee14-85ee-4f23-a0c2-
8a1cd570e203,cn=ntds settings,cn=mcc-
dc2,cn=servers,cn=mcc-
site,cn=sites,cn=configuration,dc=molalla,dc=com. Using
cn=mcc-fsmo,cn=ntds settings,cn=mcc-dc2,cn=servers,cn=mcc-
site,cn=sites,cn=configuration,dc=molalla,dc=com

The nTDSConnection object cn=mcc-dc2,cn=ntds
settings,cn=mcc-fsmo,cn=servers,cn=mcc-
site,cn=sites,cn=configuration,dc=molalla,dc=com is
conflicting with cn=0c5b118b-a491-4e11-ab94-
754fd18dd16e,cn=ntds settings,cn=mcc-
fsmo,cn=servers,cn=mcc-
site,cn=sites,cn=configuration,dc=molalla,dc=com. Using
cn=mcc-dc2,cn=ntds settings,cn=mcc-fsmo,cn=servers,cn=mcc-
site,cn=sites,cn=configuration,dc=molalla,dc=com

This error is very frustrating.

Thanks,

Brandon

 

[Jason Robarts [MSFT]]

Below is a thread I had a colleague of mine from the FRS team. I'd suggest
looking over his suggestions from the Ultrasound help file.

-----Original Message-----
From: (WINDOWS)
Sent: Wednesday, January 28, 2004 10:30 PM
To: Jason Robarts
Subject: RE: File Replications Service Errors

FRS is supposed to choose one and use that one. I'm not sure which one it

will choose, so it's probably best to get rid of one of the connections.

He can do an ntfrsutl sets to see which of the two connections looks like

it's doing something.

--Richard

-----Original Message-----
From: Jason Robarts
Sent: Wednesday, January 28, 2004 7:15 PM
To: (WINDOWS)
Subject: RE: File Replications Service Errors

In his case he has 2 connections - one manual, one KCC generated. Is that

going to cause a problem?

-----Original Message-----
From: (WINDOWS)
Sent: Wednesday, January 28, 2004 7:11 PM
To: Jason Robarts
Subject: RE: File Replications Service Errors

This might help. It's from the Ultrasound help file.

FRS Missing Member and Subscriber Objects

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.



-----Original Message-----
From: Jason Robarts
Sent: Wednesday, January 28, 2004 6:46 PM
To: (WINDOWS)
Subject: Fw: File Replications Service Errors


This appeared on the W2K AD newsgroup. Any ideas?