Hi Richard
Thanks for the response. I'm pasting the error messages from all the DC's. Just to recap
1-Upgrade from WinNT4.0 to Win2k
2-Install FRS on another partition (Raid 5)
3-After restart the server could not recognize the drive and someone formatted the drive. I believe that Win2k did not have the raid drivers installed correctly
Thank
Be
The first two event id's are from the first DC on the network
Event Type: Erro
Event Source: NtFr
Event Category: Non
Event ID: 1355
Date: 1/13/200
Time: 1:51:14 A
User: N/
Computer: Server0
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 this 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 e:\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: Erro
Event Source: NtFr
Event Category: Non
Event ID: 1355
Date: 1/12/200
Time: 1:51:00 A
User: N/
Computer: Server0
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 "riso-fp.riso.local"
Replica set member name is "Server01"
Replica set root path is "e:\winnt\sysvol\domain"
Replica staging directory path is "e:\winnt\sysvol\staging\domain"
Replica working directory path is "e:\winnt\ntfrs\jet"
Windows error status code is
FRS error status code is FrsErrorMismatchedJournalId
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.
The next Event Id is from another DC on the network
Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13508
Date: 1/12/2004
Time: 10:34:29 PM
User: N/A
Computer: Server02
Description:
The File Replication Service is having trouble enabling replication from \\riso-fp.riso.local to Server02 for c:\winnt\sysvol\domain using the DNS name \\server01.domain.local. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name \\server01.domain.local from this computer.
[2] FRS is not running on \\server01.domain.local.
[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.
----- Richard Chinn [MSFT] wrote: -----
microsoft.public.windows.server.dfs_frs would be more appropriate newsgroup
to address this question.
In the meantime, please copy and paste the text from the events in your FRS
event log. Feel free to change machine names to Server1, Server2, etc. if
you like.
--Richard
Please post FRS related questions to microsoft.public.windows.server.dfs_frs
and prefix the subject line with "FRS:" to make it easier to spot. Note
that FRS is used to replicate SYSVOL on domain controllers and DFS root and
link targets.
For additional FRS resources, please visit
http://www.microsoft.com/frs.
This posting is provided "AS IS" with no warranties, and confers no rights.
