Discussion:
NTFRS errors 13552 and 13555 -- How do I fix?
(too old to reply)
cr
2005-05-01 01:26:04 UTC
Permalink
Hi,

I have two errors in the File Replication Service Logs whenever I reboot the
Windows 2003 SBS server.

I do not have a backup to restore the system state from.

The errors are:

Event ID: 13552
The File Replication Service is unable to add this computer to the following
replica set: "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" .....
Windows error status code is
FRS error status code is FrsErrorMismatchedJournalId

and

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

Which of these should I use or should I do something else?

Thanks

cr
Frank McCallister SBS MVP
2005-05-01 04:03:45 UTC
Permalink
Was this a Migration or a fresh install? Are there any other DCs in the
Domain?
--
Frank McCallister SBS MVP
COMPUMAC
Post by cr
Hi,
I have two errors in the File Replication Service Logs whenever I reboot the
Windows 2003 SBS server.
I do not have a backup to restore the system state from.
Event ID: 13552
The File Replication Service is unable to add this computer to the following
replica set: "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" .....
Windows error status code is
FRS error status code is FrsErrorMismatchedJournalId
and
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
[1] The error state may clear itself if you stop and
restart the FRS service. This can be done by performing
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
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
(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-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.
Which of these should I use or should I do something else?
Thanks
cr
cr
2005-05-01 11:48:02 UTC
Permalink
Post by Frank McCallister SBS MVP
Was this a Migration or a fresh install? Are there any other DCs in the
Domain?
--
Frank McCallister SBS MVP
COMPUMAC
Post by cr
Hi,
I have two errors in the File Replication Service Logs whenever I reboot the
Windows 2003 SBS server.
I do not have a backup to restore the system state from.
Event ID: 13552
The File Replication Service is unable to add this computer to the following
replica set: "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" .....
Windows error status code is
FRS error status code is FrsErrorMismatchedJournalId
and
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
[1] The error state may clear itself if you stop and
restart the FRS service. This can be done by performing
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
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
(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-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.
Which of these should I use or should I do something else?
Thanks
cr
Hi Frank,
It is a single SBS installation, we've had power problems in the building
and that killed the UPS which then crashed the server.

There are no other DC's in the domain.

cr
Frank McCallister SBS MVP
2005-05-01 14:18:37 UTC
Permalink
Is this a new server? Why don't you have a Total backup yet?
--
Frank McCallister SBS MVP
COMPUMAC
Post by cr
Post by Frank McCallister SBS MVP
Was this a Migration or a fresh install? Are there any other DCs in the
Domain?
--
Frank McCallister SBS MVP
COMPUMAC
Post by cr
Hi,
I have two errors in the File Replication Service Logs whenever I
reboot
the
Windows 2003 SBS server.
I do not have a backup to restore the system state from.
Event ID: 13552
The File Replication Service is unable to add this computer to the following
replica set: "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" .....
Windows error status code is
FRS error status code is FrsErrorMismatchedJournalId
and
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
[1] The error state may clear itself if you stop and
restart the FRS service. This can be done by performing
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
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
(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-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.
Which of these should I use or should I do something else?
Thanks
cr
Hi Frank,
It is a single SBS installation, we've had power problems in the building
and that killed the UPS which then crashed the server.
There are no other DC's in the domain.
cr
cr
2005-05-01 18:04:01 UTC
Permalink
Hi Frank,

I do not have a backup that doesn't have the corrupted ntfrs.

I just need to know how to proceed from here.

cr
Post by Frank McCallister SBS MVP
Is this a new server? Why don't you have a Total backup yet?
--
Frank McCallister SBS MVP
COMPUMAC
Post by cr
Post by Frank McCallister SBS MVP
Was this a Migration or a fresh install? Are there any other DCs in the
Domain?
--
Frank McCallister SBS MVP
COMPUMAC
Post by cr
Hi,
I have two errors in the File Replication Service Logs whenever I
reboot
the
Windows 2003 SBS server.
I do not have a backup to restore the system state from.
Event ID: 13552
The File Replication Service is unable to add this computer to the following
replica set: "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" .....
Windows error status code is
FRS error status code is FrsErrorMismatchedJournalId
and
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
[1] The error state may clear itself if you stop and
restart the FRS service. This can be done by performing
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
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
(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-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.
Which of these should I use or should I do something else?
Thanks
cr
Hi Frank,
It is a single SBS installation, we've had power problems in the building
and that killed the UPS which then crashed the server.
There are no other DC's in the domain.
cr
cr
2005-05-01 22:47:03 UTC
Permalink
Hi,

Found information to delete the files and restart the service and this took
care of clearing the error in the File Replication Services.

cr
Post by Frank McCallister SBS MVP
Hi Frank,
I do not have a backup that doesn't have the corrupted ntfrs.
I just need to know how to proceed from here.
cr
Post by Frank McCallister SBS MVP
Is this a new server? Why don't you have a Total backup yet?
--
Frank McCallister SBS MVP
COMPUMAC
Post by cr
Post by Frank McCallister SBS MVP
Was this a Migration or a fresh install? Are there any other DCs in the
Domain?
--
Frank McCallister SBS MVP
COMPUMAC
Post by cr
Hi,
I have two errors in the File Replication Service Logs whenever I
reboot
the
Windows 2003 SBS server.
I do not have a backup to restore the system state from.
Event ID: 13552
The File Replication Service is unable to add this computer to the following
replica set: "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" .....
Windows error status code is
FRS error status code is FrsErrorMismatchedJournalId
and
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
[1] The error state may clear itself if you stop and
restart the FRS service. This can be done by performing
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
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
(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-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.
Which of these should I use or should I do something else?
Thanks
cr
Hi Frank,
It is a single SBS installation, we've had power problems in the building
and that killed the UPS which then crashed the server.
There are no other DC's in the domain.
cr
Frank McCallister SBS MVP
2005-05-02 03:43:36 UTC
Permalink
Thanks for the feedback. Be sure and get a good Total backup now
--
Frank McCallister SBS MVP
COMPUMAC
Post by cr
Hi,
Found information to delete the files and restart the service and this took
care of clearing the error in the File Replication Services.
cr
Post by Frank McCallister SBS MVP
Hi Frank,
I do not have a backup that doesn't have the corrupted ntfrs.
I just need to know how to proceed from here.
cr
Post by Frank McCallister SBS MVP
Is this a new server? Why don't you have a Total backup yet?
--
Frank McCallister SBS MVP
COMPUMAC
Post by cr
Post by Frank McCallister SBS MVP
Was this a Migration or a fresh install? Are there any other DCs in the
Domain?
--
Frank McCallister SBS MVP
COMPUMAC
Post by cr
Hi,
I have two errors in the File Replication Service Logs whenever I
reboot
the
Windows 2003 SBS server.
I do not have a backup to restore the system state from.
Event ID: 13552
The File Replication Service is unable to add this computer to the
following
replica set: "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" .....
Windows error status code is
FRS error status code is FrsErrorMismatchedJournalId
and
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
[1] The error state may clear itself if you stop and
restart the FRS service. This can be done by performing
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
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
(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-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.
Which of these should I use or should I do something else?
Thanks
cr
Hi Frank,
It is a single SBS installation, we've had power problems in the building
and that killed the UPS which then crashed the server.
There are no other DC's in the domain.
cr
Continue reading on narkive:
Loading...