Dawn NM
Guest
|
 Posted:
Tue Feb 08, 2005 10:13 pm Post subject:
Event ID 13552 followed by 13555 |
|
|
Hello all. Well, FRS has been working for me for a while, other than the odd
morphed folder or two.
One of the admins had set up a root to replicate without any links or link
targets. I deleted this root, then set up a new one with two link targets
and enabled replication on the links. There are two servers running Windows
Server 2003 in this FRS pair.
Unfortunately, this admin had also set up the staging directory on the C:\
drive and it filled it up on both servers, so replication stopped. I went
through adsiedit.msc and changed the staging directory to the larger drive
set (D:\) which is also where the link targets is, but that cannot be helped
as there is only a C:\ and D:\ on these servers.
After cleaning up C:\ so that it had some room, I have the following
problems on the master server:
Event ID 13552: (usual text, see below for copy)
Windows error status code is
FRS error status code is FrsErrorSuccess
Followed by:
Event ID 13555 (usual text, see below for copy)
I have tried starting and stopping ntfrs but get the same two errors up.
Neither of these servers are DCs, so I want to do the following:
[4] For other Windows 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:\windows\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.
As mentioned in the Resolution for Event ID 13555. BUT, since this machine
is the master and has not replicated all of it's information to the second
machine, I cannot have all the data moved for any length of time, as the
users depend on it. If I remove the \jet directory, what happens?
Dawn
Here is the text from the two error events (with names changed to protect
the innocent):
Event ID 13552
The File Replication Service is unable to add this computer to the following
replica set:
"root|linkA"
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 "servername.Dover.Local"
Replica set member name is "{2403A68A-96CD-4CCB-8FB1-8E6C8ADB192B}"
Replica set root path is "d:\path\link"
Replica staging directory path is "d:\frs-staging"
Replica working directory path is "c:\windows\ntfrs\jet"
Windows error status code is
FRS error status code is FrsErrorSuccess
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.
Event ID: 13555
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 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:\windows\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. |
|
Dawn NM
Guest
|
| Posted:
Wed Feb 09, 2005 3:13 am Post subject:
RE: Event ID 13552 followed by 13555 |
|
|
From bad to worse:
Now I have this entry: (Event ID 13506)
The File Replication Service failed a consistency check
(!Cxtion->Inbound)
in "OutLogCleanupWorker:" at line 5000.
The File Replication Service will restart automatically at a later time. If
this problem persists a subsequent entry in this event log describes the
recovery procedure.
For more information about the automatic restart right click on My Computer
and then click on Manage, System Tools, Services, File Replication Service,
and Recovery.
Help!
"Dawn NM" wrote:
| Quote: | Hello all. Well, FRS has been working for me for a while, other than the odd
morphed folder or two.
One of the admins had set up a root to replicate without any links or link
targets. I deleted this root, then set up a new one with two link targets
and enabled replication on the links. There are two servers running Windows
Server 2003 in this FRS pair.
Unfortunately, this admin had also set up the staging directory on the C:\
drive and it filled it up on both servers, so replication stopped. I went
through adsiedit.msc and changed the staging directory to the larger drive
set (D:\) which is also where the link targets is, but that cannot be helped
as there is only a C:\ and D:\ on these servers.
After cleaning up C:\ so that it had some room, I have the following
problems on the master server:
Event ID 13552: (usual text, see below for copy)
Windows error status code is
FRS error status code is FrsErrorSuccess
Followed by:
Event ID 13555 (usual text, see below for copy)
I have tried starting and stopping ntfrs but get the same two errors up.
Neither of these servers are DCs, so I want to do the following:
[4] For other Windows 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:\windows\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.
As mentioned in the Resolution for Event ID 13555. BUT, since this machine
is the master and has not replicated all of it's information to the second
machine, I cannot have all the data moved for any length of time, as the
users depend on it. If I remove the \jet directory, what happens?
Dawn
Here is the text from the two error events (with names changed to protect
the innocent):
Event ID 13552
The File Replication Service is unable to add this computer to the following
replica set:
"root|linkA"
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 "servername.Dover.Local"
Replica set member name is "{2403A68A-96CD-4CCB-8FB1-8E6C8ADB192B}"
Replica set root path is "d:\path\link"
Replica staging directory path is "d:\frs-staging"
Replica working directory path is "c:\windows\ntfrs\jet"
Windows error status code is
FRS error status code is FrsErrorSuccess
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.
Event ID: 13555
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 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:\windows\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.
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in