A few items to note.
1) This appears to be a domain based DFS root\link which is located at :
d:\public\geos2
2) It also appears that you may be scanning d:\public\geos2 with some type
of anti-virus solution, hence the event ID 13567, when the AV software
checks these files, FRS is triggered and may think it needs to replicate the
data since it has been touched and "changed" - when in fact there is no real
change. It is up to you to scan this data or not, there are some AV vendors
which have addressed this and are "FRS-safe"
3) Can you please use ldifde to dump this data (from BOTH DC's) - like so:
ldifde -f mercury.txt -d "cn=ntfrs subscriptions,cn=mercury,ou=domain
controllers,dc=ulib,dc=ox,dc=ac,dc=uk"
ldifde -f zeus.txt -d "cn=ntfrs subscriptions,cn=zeus,ou=domain
controllers,dc=ulib,dc=ox,dc=ac,dc=uk"
I dont know the general rules of this list, (a bit new here) but you can
send the results directly to me, or post them on a web\ftp site if you like,
then send a link.
-steve
----- Original Message -----
From: "Svetlana Kouznetsova" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, June 02, 2004 2:14 AM
Subject: [ActiveDir] FRS errors
Guys, please, can you help - FRS errors:
Two W2K DCs, one has got directory "geos2", which supposed to replicate
to another DC for redundancy purposes.
The "master" copy is on - DC1, replica - DC2.
The replication doesn't work with following error messages:
On DC1 (ZEUS):
Once a day - event id 13508:
The File Replication Service is having trouble enabling replication from
MERCURY to ZEUS for d:\public\geos2 using the DNS name MERCURY FRS will
keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name MERCURY from this
computer.
[2] FRS is not running on MERCURY.
[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.
*No expected messages about problem fixed.
AFTER RESTART frs - event id 13567:
File Replication Service has detected and suppressed an average of 15 or
more file updates every hour for the last 3 hours because the updates
did not change the contents of the file. The tracking records in FRS
debug logs will have the filename and event time for the suppressed
updates. The tracking records have the date and time followed by :T: as
their prefix.
Updates that do not change the content of the file are suppressed to
prevent unnecessary replication traffic. Following are common examples
of updates that do not change the contents of the file.
[1] Overwriting a file with a copy of the same file.
[2] Setting the same ACLs on a file multiple times.
[3] Restoring an identical copy of the file over an existing one.
Suppression of updates can be disabled by running regedit.
Click on Start, Run and type regedit.
Expand HKEY_LOCAL_MACHINE, SYSTEM, CurrentControlSet, Services, NtFrs,
Parameters, and create or update the value "Suppress Identical Updates
To Files" to 0 (Default is 1) to force identical updates to replicate.
On DC2 (MERCURY):
Once a day - event id 13562:
Following is the summary of warnings and errors encountered by File
Replication Service while polling the Domain Controller MERCURY for FRS
replica set configuration information.
The nTFRSSubscriber object
cn=dfs|geos2,cn=dfs,cn=652103c0-3567-45e2-89d6-3773e36c8e9d,cn=dfs
volumes,cn=ntfrs subscriptions,cn=mercury,ou=domain
controllers,dc=ulib,dc=ox,dc=ac,dc=uk has a invalid value for the
attribute frsMemberReference.
The File Replication Service is having trouble enabling replication from
MERCURY to ZEUS for d:\public\geos2 using the DNS name MERCURY. FRS will
keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name MERCURY from this
computer.
[2] FRS is not running on MERCURY.
[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.
The same "one-off" event id 13567 after restarting frs
DNS tested and seems to be fine and replmon show no AD replication
problems, FRS service is running on both DC. Permissions on directories
set up to Everyone- full control.
I don't suppose netdom.exe would be a relevant fix for that, as it's not
like - AD related, right? In fact it would be useful to know, if this is
affecting AD replication in any ways at all, as my initial problem was -
W2K3 domain controller didn't not replicate outbound after dcpromo
["FATAL kerberos error on W2K3 server" thread]. So I've demoted it back
to member server and trying to clean up event logs on W2K DC's
Many many thanks in advance for any suggestions
Lana
List info : http://www.activedir.org/mail_list.htm
List FAQ : http://www.activedir.org/list_faq.htm
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
List info : http://www.activedir.org/mail_list.htm
List FAQ : http://www.activedir.org/list_faq.htm
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
