My recommendation at this point ould be to simply restart the DC's (if possible). Restart them one at a time starting with the DC that owns the FSMO roles and the GC role.
Dean -- Dean Wells MSEtechnology * Tel: +1 (954) 501-4307 * Email: [EMAIL PROTECTED] http://msetechnology.com -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Julian Lyndon-Smith Sent: Tuesday, December 11, 2001 8:10 AM To: '[EMAIL PROTECTED]' Subject: RE: [ActiveDir] AD problems. Please help !! This is such a great list, thanks for all the help so far - it is much appreciated ! Ok, I've done that - I've now got errors in the frs event viewer - I now presume that's why replication is not working .. Event Type: Error Event Source: NtFrs Event Categrory: None Event ID: 13555 Date: 11/12/2001 Time: 16:01:33 User: N/A Computer: MachineA Description: The File Replication Service is in an error state. Files will not replicate to or from one or all of the replica sets on his computer until the following recovery steps are performed: Recovery Steps: [1] The error state may clear itself if you stop and restart the FRS service. This can be done by performing the following in a command window: net stop ntfrs net start ntfrs If this fails to clear up the problem then proceed as follows. [2] For Active Directory Domain Controllers that DO NOT host any DFS alternates or other replica sets with replication enabled: If there is at least one other Domain Controller in this domain then restore the "system state" of this DC from backup (using ntbackup or other backup-restore utility) and make it non-authoritative. If there are NO other Domain Controllers in this domain then restore the "system state" of this DC from backup (using ntbackup or other backup-restore utility) and choose the Advanced option which marks the sysvols as primary. If there are other Domain Controllers in this domain but ALL of them have this event log message then restore one of them as primary (data files from primary will replicate everywhere) and the others as non-authoritative. [3] For Active Directory Domain Controllers that host DFS alternates or other replica sets with replication enabled: (3-a) If the Dfs alternates on this DC do not have any other replication partners then copy the data under that Dfs share to a safe location. (3-b) If this server is the only Active Directory Domain Controller for this domain then, before going to (3-c), make sure this server does not have any inbound or outbound connections to other servers that were formerly Domain Controllers for this domain but are now off the net (and will never be coming back online) or have been fresh installed without being demoted. To delete connections use the Sites and Services snapin and look for Sites->NAME_OF_SITE->Servers->NAME_OF_SERVER->NTDS Settings->CONNECTIONS. (3-c) Restore the "system state" of this DC from backup (using ntbackup or other backup-restore utility) and make it non-authoritative. (3-d) Copy the data from step (3-a) above to the original location after the sysvol share is published. [4] For other Windows 2000 servers: (4-a) If any of the DFS alternates or other replica sets hosted by this server do not have any other replication partners then copy the data under its share or replica tree root to a safe location. (4-b) net stop ntfrs (4-c) rd /s /q c:\winnt\ntfrs\jet (4-d) net start ntfrs (4-e) Copy the data from step (4-a) above to the original location after the service has initialized (5 minutes is a safe waiting time). Note: If this error message is in the eventlog of all the members of a particular replica set then perform steps (4-a) and (4-e) above on only one of the members. ########## Event Type: Error Event Source: NtFrs Event Category: None Event ID: 13550 Date: 11/12/2001 Time: 16:01:33 User: N/A Computer: MachineA Description: The File Replication Service is unable to open the customer designated staging directory for replica set DOMAIN SYSTEM VOLUME (SYSVOL SHARE). The path used for the staging directory is, "g:\winnt\sysvol\staging\domain" The customer designated root path for this replica set is: "g:\winnt\sysvol\domain" The service is unable to start replication on this replica set. Among the possible errors to check are: -- an invalid staging path, -- a missing directory, -- a missing disk volume, -- a file system on the volume that does not support ACLs, -- a sharing conflict on the staging directory with some other application. Correct the problem and the service will attempt to restart replication automatically at a later time. ############## Event Type: Error Event Source: NtFrs Event Category: None Event ID: 13552 Date: 11/12/2001 Time: 16:01:33 User: N/A Computer: MachineA Description: The File Replication Service is unable to add this computer to the following replica set: "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" This could be caused by a number of problems such as: -- an invalid root path, -- a missing directory, -- a missing disk volume, -- a file system on the volume that does not support NTFS 5.0 The information below may help to resolve the problem: Computer DNS name is "MachineA.OurDomain.com" Replica set member name is "MachineA" Replica set root path is "g:\winnt\sysvol\domain" Replica staging directory path is "g:\winnt\sysvol\staging\domain" Replica working directory path is "c:\winnt\ntfrs\jet" Windows error status code is FRS error status code is FrsErrorStageDirOpenFail Other event log messages may also help determine the problem. Correct the problem and the service will attempt to restart replication automatically at a later time. Regards, Julian. Julian Lyndon-Smith IT Director Dot R Limited http://www.dotr.com [EMAIL PROTECTED] -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Dean Wells Sent: 11 December 2001 15:39 To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] AD problems. Please help !! Thta's likely your problem, configure the two domain controllers to resolve against one another as they're preferred DNS server and against themselves as the alternate. Restart the NETLOGON service on both DC's, force the KCC to run on both DCs (repadmin /kcc) or DSSITE.MSC. Refresh the connection objects beneath the NTDS settings within the UI and force replication. HTH Dean -- Dean Wells MSEtechnology * Tel: +1 (954) 501-4307 * Email: [EMAIL PROTECTED] http://msetechnology.com -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Julian Lyndon-Smith Sent: Tuesday, December 11, 2001 7:34 AM To: '[EMAIL PROTECTED]' Subject: RE: [ActiveDir] AD problems. Please help !! Yes, the DNS is integrated, and we have no errors in either of the event logs. Regards, Julian. Julian Lyndon-Smith IT Director Dot R Limited http://www.dotr.com [EMAIL PROTECTED] 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/
