Windows 2003 FRS Nightmare: Event ID 13506

  • Thread starter Thread starter Jimbo
  • Start date Start date
J

Jimbo

The following error (ID 13506) appears in the event log which has now been
occurring for the past 24 hours. I am running two way synchronous
replication between two sites with a fault tollerent DFS. We replicate
around 200GB of constantly changing data, and have done so successfully for
the past 2 years (initially on the w2k platform.) This is the first time
I've ever seen this error:

The File Replication Service failed a consistency check (!"DIR_DIR Morph
Conflict where Orig Guid in CO equals IDTrecord") in "ChgOrdGenMorphCo:" at
line 5541.

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.

This error is followed by standard FRS recovery steps message ID 13555 and
then the service stops with its assertion failure message and restarts half
an hour later repeating the whole process.

Any help please FRS whizzes?
 
Both running windows server 2003 standard edition, all critical updates
installed via SUS. Servers are dell poweredge 1750 dual xeons with 2 gb of
ram in each. The FRS jet database is left in the default location on the C:
system partition, the staging directory is on a separate physical disk (D:)
and the data being replicated is on a SAN fibre channel array (Dell CX200.)

There are now two sets of different critical data on each server, so
deleting the jet database and rebuilding on the offending server is out of
the question at this stage. Any help would be much appreciated.
 
That article didn't help, however uninstalling SFM (Services for Macintosh)
did fix the problem. There was a mac share created on one of the folders
that was part of the replication set and i can only assume that FRS hasn't
been designed to work with mac forks. *sigh* Hope this is of help to anyone
else in the future until Microsoft resolve the issue (if it is in fact a MS
issue.)
 
Back
Top