Windows Server

Guest · Posted: Sun Oct 23, 2005 6:23 am Post subject: FRS Errors - Seeking advice

I am prepping my domain for 2003.

While patching the DC's today, I notice a pile of FRS errors on one DC
(Event ID's 13555 and 13552)

This DC happens top be an Exchange box. Everything seems to work just
fine. Email works for all domain users from this box. I fear that
forest and domain prep will fail if I do not resolve this issue.

Since this is the only box with the problem, I would have normally
nuked this DC manually. However, I need to keep this box alive since it
is our Exchange.

I have searched through Usenet and I am afraid I cannot find my
solution. All of the backups I have are with this error, so performing
a restore of the system state are out of the question.

Thanks for any and all help.

-tom

<info below>

I ran dcdiag with these results:

Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.

C:\Documents and Settings\Administrator.server>dcdiag

DC Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial non skippeable tests

Testing server: Default-First-Site-Name\server02
Starting test: Connectivity
......................... server02 passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\server02
Starting test: Replications
......................... server02 passed test Replications
Starting test: NCSecDesc
......................... server02 passed test NCSecDesc
Starting test: NetLogons
......................... server02 passed test NetLogons
Starting test: Advertising
......................... server02 passed test Advertising
Starting test: KnowsOfRoleHolders
......................... server02 passed test
KnowsOfRoleHolders
Starting test: RidManager
......................... server02 passed test RidManager
Starting test: MachineAccount
......................... server02 passed test MachineAccount
Starting test: Services
......................... server02 passed test Services
Starting test: ObjectsReplicated
......................... server02 passed test
ObjectsReplicated
Starting test: frssysvol
Error: No record of File Replication System, SYSVOL started.
The Active Directory may be prevented from starting.
......................... server02 passed test frssysvol
Starting test: kccevent
......................... server02 passed test kccevent
Starting test: systemlog
......................... server02 passed test systemlog

Running enterprise tests on : server.com
Starting test: Intersite
......................... server.com passed test Intersite
Starting test: FsmoCheck
......................... server.com passed test FsmoCheck

C:\Documents and Settings\Administrator.server>

Here is my 13552:
-----------------------------snip---------------------
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 "server02.server.com"
Replica set member name is "SERVER02"
Replica set root path is "c:\winnt\sysvol\domain"
Replica staging directory path is "c:\winnt\sysvol\staging\domain"
Replica working directory path is "c:\winnt\ntfrs\jet"
Windows error status code is
FRS error status code is FrsErrorJournalInitFailed

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.

Here is 13555:
-----------------------------snip--------------------------

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 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.

Paul Williams [MVP] · Guest

Perform a non-authorative restore of SYSVOL.

Stop FRS (net stop ntfrs)
Set BurFlags to D2 [1]
Start FRS (net start ntfrs)
Wait a while and then check the event logs. There should be some warnings
and info.'s. Read them.

---
[1] BurFlags is a value under this key:

HKLM\ SYSTEM\ CurrentControlSet\ Services\ NtFrs\ Parameters\
Backup/Restore\ Process at Startup

--
Paul Williams
Microsoft MVP - Windows Server - Directory Services
http://www.msresource.net | http://forums.msresource.net

Guest · Posted: Mon Oct 24, 2005 4:51 pm Post subject: Re: FRS Errors - Seeking advice

Paul,

Thank you. for the reply.

I have let the machine sit overnight after making the suggested change.
The problem still persists.

Regards,
Tom

Paul Williams [MVP] · Guest

Can you paste both events here?

--
Paul Williams
Microsoft MVP - Windows Server - Directory Services
http://www.msresource.net | http://forums.msresource.net

	Windows Server Forum Index -> DFS and FRS	All times are GMT
Page 1 of 1