Event: FrsErrorMismatchedJournalId

[Jake]

Hi,

One secondary PDC gives the "FrsErrorMismatchedJournalId" FRS error in
the event log. What should we do to correct the problem...?

I suspect that the problem arised after a domain rename, but I hope
there is a way to resolve it w/o reinstalling the secondary DC...

regards jake

Message in event log:


The File Replication Service is unable to add this computer to the
following replica set:
"DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"

This could be caused by a number of problems such as:
-- an invalid root path,
-- a missing directory,
-- a missing disk volume,
-- a file system on the volume that does not support NTFS 5.0

The information below may help to resolve the problem:
Computer DNS name is "peter.mydomain.LAN"
Replica set member name is "PETER"
Replica set root path is "c:\windows\sysvol\domain"
Replica staging directory path is "c:\windows\sysvol\staging\domain"
Replica working directory path is "c:\windows\ntfrs\jet"
Windows error status code is
FRS error status code is FrsErrorMismatchedJournalId

[Rudolf Meier]

Hi

One secondary PDC gives the "FrsErrorMismatchedJournalId" FRS error in the
event log. What should we do to correct the problem...?
I suspect that the problem arised after a domain rename, but I hope there
is a way to resolve it w/o reinstalling the secondary DC...
regards jake
The File Replication Service is unable to add this computer to the
"DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
-- an invalid root path,
-- a missing directory,
-- a missing disk volume,
-- a file system on the volume that does not support NTFS 5.0
Computer DNS name is "peter.mydomain.LAN"
Replica set member name is "PETER"
Replica set root path is "c:\windows\sysvol\domain"
Replica staging directory path is "c:\windows\sysvol\staging\domain"
Replica working directory path is "c:\windows\ntfrs\jet"
Windows error status code is
FRS error status code is FrsErrorMismatchedJournalId

You could try to do this: http://support.microsoft.com/kb/925633/en-us
I once had a similar problem, after changing a failed harddisk in a DC.
Because the ID of the disk changed, the service also stopped and reported
something similar to what you got. After the restore action it worked again.
I hope this helps...

Rudolf Meier

[e***@gompersstudent.org]

Post by Jake
Hi,
One secondary PDC gives the "FrsErrorMismatchedJournalId" FRS error in
the event log. What should we do to correct the problem...?
I suspect that the problem arised after a domain rename, but I hope
there is a way to resolve it w/o reinstalling the secondary DC...
regards jake
ens dfgnnv goolie cfgnzfrn fisde h sfjdyfn fry's electronics
The File Replication Service is unable to add this computer to the
"DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
-- an invalid root path,
-- a missing directory,
-- a missing disk volume,
-- a file system on the volume that does not support NTFS 5.0
Computer DNS name is "peter.mydomain.LAN"
Replica set member name is "PETER"
Replica set root path is "c:\windows\sysvol\domain"
Replica staging directory path is "c:\windows\sysvol\staging\domain"
Replica working directory path is "c:\windows\ntfrs\jet"
Windows error status code is
FRS error status code is FrsErrorMismatchedJournalId