Discussion Locked

Server 2003 File Replication Service has stopped

0 helpful
1 reply
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

The alarm was going off on my 1 year old Dell power edge SC server, windows 2003 R2 standard SP 2. Dell told it was the raid alarm, then to restart to let it rebuild itself, next day alarm noise again, restarted but missing start-up files so used 2003 disk to restart server (recovery console). Dell came out to change the hard drive. The problem is the File Replication Service has stopped and won?t restart because it is having a problem with the SYSVOL
Any ideas
Will post more info

1 reply

by c.collins

http://jsifaq.com/sf/tips/tip.aspx?id=3605

The most likely cause of these errors is that the FRS Jet database, or a Jet database log file, is corrupt. To fix the problem:
1. Open a CMD prompt on the domain controller and stop the NetLogon and Ntfrs services:

net stop NetLogon
net stop Ntfrs

2. Type:

del %systemroot%\ntfrs\jet\Ntfrs.jdb
del %systemroot%\ntfrs\jet\Sys\Edb.chk
del %systemroot%\ntfrs\jet\log\edb.log
del %systemroot%\ntfrs\jet\log\res1.log
del %systemroot%\ntfrs\jet\log\res2.log

3. Type:

net start NetLogon
net start Ntfrs

4. Check the FRS event log for expected warning 13514 and 13520.

5. Close the FRS event log and go get a cup of coffee.

6. In five minutes, recheck the FRS event log for informational messages 13553, 13554, and 13516.

NOTE: See tip 3383 ? How do I configure the File Replication Service (NTFRS) via the registry?

NOTE: There is a high risk of data loss if the unexpected event of a bad replication occurs. All files will be moved to NtFrs_PreExisting.

This discussion is closed to new replies.