RE: Replication works off and on after upgrading to 2003 from 2000 server?

From: Hover Xue [MSFT] (hoverxue_at_online.microsoft.com)
Date: 03/01/04 

Date: Mon, 01 Mar 2004 22:22:44 GMT

Thanks for posting!

I understand the issue is that after upgrading your domain controller to
Windows server2003, you begin to get Event 13508 and Event 13516 errors.
You suspect that this is why your group policy get online and offline every
day.

The issue can happen if:
1. FRS can not correctly resolve the DNS name for server 2 from server 1.
2. FRS is not running on server 2
3. The topology information in the Active Directory for this replica has
not yet replicated to all the Domain Controllers.

Event 13508 in the FRS log is a warning that the FRS service has been
unable to complete the RPC connection to a specific replication partner. It
indicates that FRS is having trouble, enabling replication with that
partner and will keep trying to establish the connection. A single event ID
13508 does not mean anything is broken or not working; simply look for
event ID 13509 to make sure that the problem was resolved. Based on the
time between event IDs 13508 and 13509, you can determine if there is a
real problem that needs to be addressed.

Note that if FRS is stopped after a 13508 event, and then later started at
a time when the communication issue has been resolved, no 13509 will be
entered in the event log, and without a 13508 message reappearing,
replication connections are being made correctly.

Since FRS servers gather their replication topology information from their
closest Active Directory domain controller (itself on a domain controller
that is also an FRS member), there is also an expected case where a replica
partner in another site will not be aware of the replica set until the
topology information has been replicated to domain controllers in that
site. When the topology information finally reaches that distant domain
controller, the FRS partner in that site will be able to participate in the
replica set and lead to FRS event ID 13509. Note that intra-site Active
Directory replication partners replicate every 5 minutes. Inter-site
replication only replicates when the schedule is open (shortest delay is 15
minutes). In addition, FRS polls the topology in the active directory at
defined intervals - 5 minutes on domain controllers, and 1 hour on other
member servers of a replica set. These delays and schedules (and especially
in topologies with multiple hops) can delay propagation of the FRS
replication topology

Here are the procedures for Troubleshooting FRS Event 13508 without Event
13509:
1. Examine the 13508 Event in the FRS Event Log in order to determine which
machine that FRS has been unable to communicate with.

2. Determine whether the remote machine is working properly, and verify
that FRS is running on it. A good method to do this to execute "NTFRSUTL
VERSION <FQDN of remote DC name>" from the machine logging the 13508 event.
If this fails, check network connectivity by pinging the <FQDN of remote DC
name> from the machine logging the 13508 event. If this fails, then
troubleshoot as a DNS or TCP/IP issue. If it succeeds, confirm the FRS
service is started on the remote DC.

3. Determine whether FRS has ever been able to communicate with the remote
computer by looking for 13509 in the event log and review recent change
management to networking, firewalls, DNS configuration, and Active
Directory infrastructure to see if there is a correlation.

4. Determine whether there is anything between the two machines that is
capable of blocking RPC traffic, such as a firewall or router.

5. Confirm that Active Directory replication is working".

For more informaiton, please see:
272279 How to Troubleshoot the File Replication Service and the Distributed
http://support.microsoft.com/?id=272279

Regards,
Hover Xue
MCSE 2000, MCDBA
Microsoft Partner Support
 
Get Secure! - www.microsoft.com/security
 
============================================================================
==============

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

============================================================================
==============

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
| Thread-Topic: Replication works off and on after upgrading to 2003 from
2000 server?
| thread-index: AcP/pmhvnrkKRGACQ7udRDJPer1LKA==
| X-Tomcat-NG: microsoft.public.windows.server.migration
 microsoft.public.windows.server.migration
|
| Replication works off and on after upgrading to 2003 from 2000 server?
Even id 13508 and 13516 loggs every day, sometimes some day apart.

I think this is the problem why my group polisy work of and on.
|

Relevant Pages

  • Re: multiple errors in Active Directory
    ... The File Replication Service is having trouble enabling replication from ... FRS will keep retrying. ... This event log message will appear once per connection, ... Source domain controller address: ...
    (microsoft.public.windows.server.active_directory)
  • Re: Operations Master Replication Issue Event ID 13562
    ... my understanding of this issue is: The FRS replica fails ... and you cannot transfer the FSMO to another server. ... seize the FSMO roles to other domain controller and then refer to KB312862 ... >> This server and others are having problems with replication. ...
    (microsoft.public.win2000.active_directory)
  • Re: NtFrs Replication Errors for deleted link
    ... FRS relies on essential containers, objects, and attributes stored in Active ... Directory and replicated among domain controllers in a given domain. ... Want to learn more about Windows Server file and storage technologies? ... Replication Service while polling the Domain Controller ...
    (microsoft.public.windows.file_system)
  • re:DNS / Netlogon problem
    ... trouble enabling replication from CRCAD1 to CRCAD for ... FRS can not correctly resolve the DNS name ... Controllers. ... message indicating that the connection has been established. ...
    (microsoft.public.windows.server.dns)
  • Re: add a new 2003 server to domain as DC
    ... Replication Service while polling the Domain Controller ... byronbdc.mydomain.net for FRS replica set configuration information. ... with "ntfrsutl ds" I got some vaules not sure for SYSVOL Set: ...
    (microsoft.public.windows.server.active_directory)
Loading