FRS journal corruption - how to recover?

[Paolo Prinsecchi]

(Windows 2000 SP4)
If possible please reply to paolo.prinsecchi{a%t}kcc.com

Hi all,
I've hit a problem on a single-server AD domain we
have... the FRS service is refurign to start, reporting
errors 13555 and 13552. This last message refers to a FRS
Journal corruption.

Now, the server is the only DC we have in there. It runs
an AD domain all by itself and, as you would guess, there
is no good backup to go back to (the problem originally
happened in April, but was discovered only when we tried
adding a second DC last week). The DC is othervise
functioning normally (users can log-on, sysvol and
netlogon shares published, etc).

Do you know of any way to reset the FRS database witouth
losing the AD? Can I just zap the jet database and re-
start FRS to re-create it from scratch?

Any suggestion appreciated.

Thanks,
Paolo

 

[Simon Geary]

You need to do a non authoritative restore of FRS using the burflags
registry key. The KB article on it seems to have been yanked but this is the
procedure:

Stop the FRS service.
Go to this registry key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs\Parameters\Backup
/Restore\Process at Startup
Change the BurFlags value to D2
Restart the FRS service

These articles have some more background information on the problem.
http://support.microsoft.com/?id=811219
http://support.microsoft.com/?id=292438

 

[Peter Hagen]

Can anyone tell me if this going to work on a post-SP4 DC as well?