Alert: The File Replication Service is not running on Domain Controller

Issue: File replication service constantly stopps and restarts, providing the following Event:

ntfrs (2224) A bad page link (error -338) has been detected in a B-Tree (ObjectId: 31, PgnoRoot: 139) of database c:\windows\ntfrs\jet\ntfrs.jdb (6587 => 6904, 6905).

and

The File Replication Service failed a consistency check
(!\”ISCU_INS_OUTLOG failed\”)
in \”ChgOrdIssueCleanup:\” at line 8306.

Resolution: Event ID 447 indicates that the logical database structure has become corrupted. This may occur for one or more of the following reasons:
- Disk caching has not committed transactions to the hard disk and the server has stopped responding (crashed).
- Incorrect log files were replayed during a database restoration.
- The server has a defective hard disk controller.
- Database log files have been removed that were not fully committed to the database.

http://support.microsoft.com/kb/810190/en-us

copied the ESEUTIL files to the Server and ran ESUTIL /p on the database to repair it.

Submitted By: Mirco Wilhelm