Would someone please help share the knowledge to correct
the problem below

Source NtFrs
Event ID 13552

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 "MDISRV.mdiagnostics.com"
Replica set member name is "MDISRV"
Replica set root path is "d:\winnt\sysvol\domain"
Replica staging directory path
is "d:\winnt\sysvol\staging\domain"
Replica working directory path is "c:\winnt\ntfrs\jet"
Windows error status code is
FRS error status code is FrsErrorMismatchedJournalId

Other event log messages may also help determine the
problem. Correct the problem and the service will attempt
to restart replication automatically at a later time.



Thanks

Terry

Dude

May not make you feel any better but we are experienceing
the same issue on a DC that is also a GC/SM/DM/RID.

We then get event 13555

(I've just made the same post in here)

Searching Technet kinda sugests the following.

Q819268 that states this problem may occur after you apply
the fix that is described in the following Microsoft
Knowledge Base article: - Q811370 Issues That Are Fixed in
the Post-Service Pack 3 Release of Ntfrs.exe

I've not got any further as yet troubleshooting this one.

Should I get a resolution I'll let you know.

Johnny Red


>-----Original Message-----
>Would someone please help share the knowledge to correct
>the problem below
>
>Source NtFrs
>Event ID 13552
>
>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 "MDISRV.mdiagnostics.com"
>Replica set member name is "MDISRV"
>Replica set root path is "d:\winnt\sysvol\domain"
>Replica staging directory path
>is "d:\winnt\sysvol\staging\domain"
>Replica working directory path is "c:\winnt\ntfrs\jet"
>Windows error status code is
>FRS error status code is FrsErrorMismatchedJournalId
>
>Other event log messages may also help determine the
>problem. Correct the problem and the service will
attempt
>to restart replication automatically at a later time.
>
>
>
>Thanks
>
>Terry
>.
>

Well we are having the same problem with the PDC. This could be related to the fact that we had to change the
static IP of our PDC and then make changes to DHCP DNS to all other DCs. However, this is the only DC that has
the 13552 and 13555 errors which if you search the debug log comes down to a journal version error. Event ID
has a neat solution but not willing to try it yet. I cant use a restore because that would give the PDC all the old settings!

Therefore perhaps deleting the jet file and logs would allow AD to restore our PDC?

Let me know what you think.

(E-Mail Removed)

Try reposting to microsoft.public.windows.server.dfs_frs.

--Richard

Please post FRS related questions to microsoft.public.windows.server.dfs_frs
and prefix the subject line with "FRS:" to make it easier to spot. Note
that FRS is used to replicate SYSVOL on domain controllers and DFS root and
link targets.

For additional FRS resources, please visit http://www.microsoft.com/frs.

This posting is provided "AS IS" with no warranties, and confers no rights.

"lmarcus" <(E-Mail Removed)> wrote in message
news:82718482-E710-4342-9CE6-(E-Mail Removed)...
> Well we are having the same problem with the PDC. This could be related
to the fact that we had to change the
> static IP of our PDC and then make changes to DHCP DNS to all other DCs.
However, this is the only DC that has
> the 13552 and 13555 errors which if you search the debug log comes down to
a journal version error. Event ID
> has a neat solution but not willing to try it yet. I cant use a restore
because that would give the PDC all the old settings!
>
> Therefore perhaps deleting the jet file and logs would allow AD to restore
our PDC?
>
> Let me know what you think.
>
> (E-Mail Removed)