File Replication Service errors 13506, 13555, 13552 and 13505

[ebyrne]

We have a single DFS root with 2 DFS Root targets, one a W2K3 TS and one a
W2K3 SBS server.

Hub and spoke replication is enabled, and the following errors are popping
up on the W2K3 SBS server, (which is the Hub server) immediately after the
service starts:

13056
The File Replication Service failed a consistency check
(QKey != QUADZERO)
in "QHashInsertLock:" at line 696.
...

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

The service then stops and 2 more errors are recorded:
13552
The File Replication Service is unable to add this computer to the following
replica set:
"DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
...

13505
The File Replication Service has stopped after taking an assertion failure.
...


The 13555 error messages suggest performing a non-authorative restore of the
DC to fix the problem. Would like some alternative things to perform befor
going down that road....

[Isaac Oben [MCITP:EA, MCSE]]

Hello ebyrne, the
"13056 The File Replication Service failed a consistency check (QKey !=
QUADZERO) in "QHashInsertLock:" at line 696." seems to be a recurring issue
and I haven't seen a comprehensive solution anywhere. You can call Microsoft
product support or do a D2 using instructions from link below
http://support.microsoft.com/?id=290762
First try to install alll latest service packs and see issue still persists

Isaac

Post by ebyrne
We have a single DFS root with 2 DFS Root targets, one a W2K3 TS and one a
W2K3 SBS server.
Hub and spoke replication is enabled, and the following errors are popping
up on the W2K3 SBS server, (which is the Hub server) immediately after the
13056
The File Replication Service failed a consistency check
(QKey != QUADZERO)
in "QHashInsertLock:" at line 696.
...
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
...
13552
The File Replication Service is unable to add this computer to the following
"DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
...
13505
The File Replication Service has stopped after taking an assertion failure.
...
The 13555 error messages suggest performing a non-authorative restore of the
DC to fix the problem. Would like some alternative things to perform befor
going down that road....

[Mike]

Hello ebyrne,

since I am dealing with the same problem, could you please tell us what were
the steps you followed for "breaking and re-creating the replication"?

Is other any specific ms article you could advice?

Thanks in Advance,
Mike.

Fixed the problem by breaking the replication and re-created it.
Thanks for the suggestion though.

[ebyrne]

Fixed the problem by breaking the replication and re-created it.
Thanks for the suggestion though.

Post by Isaac Oben [MCITP:EA, MCSE]
Hello ebyrne, the
"13056 The File Replication Service failed a consistency check (QKey !=
QUADZERO) in "QHashInsertLock:" at line 696." seems to be a recurring issue
and I haven't seen a comprehensive solution anywhere. You can call Microsoft
product support or do a D2 using instructions from link below
http://support.microsoft.com/?id=290762
First try to install alll latest service packs and see issue still persists
Isaac

Post by ebyrne
We have a single DFS root with 2 DFS Root targets, one a W2K3 TS and one a
W2K3 SBS server.
Hub and spoke replication is enabled, and the following errors are popping
up on the W2K3 SBS server, (which is the Hub server) immediately after the
13056
The File Replication Service failed a consistency check
(QKey != QUADZERO)
in "QHashInsertLock:" at line 696.
...
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
...
13552
The File Replication Service is unable to add this computer to the following
"DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
...
13505
The File Replication Service has stopped after taking an assertion failure.
...
The 13555 error messages suggest performing a non-authorative restore of the
DC to fix the problem. Would like some alternative things to perform befor
going down that road....