Sysvol Not Replicating

[James Palic]

We have a very simple setup with two sites each with a W2K3 DC.
Apparently back in February the SYSVOL stopped replicating. AD info
seems to be replicating just fine. DNS seems to be working. DCDIAG
doesn't report any issues.

The only errors I'm seeing in regard to the files not replicating are
in the %systemroot%\debug\ntfrs_????.log files. I'm getting a series
that looks like this for each file that is attempting to replicate:

=============================================
<StuOpenDestinationFile: 1536: 653: S0: 17:14:07> :: CoG
65016561, CxtG 4e1ae42a, FV 3, FID 00060000 0000352a, FN: bath.txt
, [FrsForceOpenId failed. (ERROR_INVALID_PARAMETER)]

<StuExecuteInstall: 1536: 2271: S1: 17:14:07> WARN -
StuOpenDestinationFile failed. WStatus: ERROR_FILE_NOT_FOUND

<ProcessOpenByIdStatus: 1536: 3010: S1: 17:14:07> ++ 001D0000
00003416 Fid Open failed; NTStatus: STATUS_INVALID_PARAMETER

<FrsOpenSourceFileById: 1536: 3360: S0: 17:14:07> ++ ERROR -
NtCreateFile failed : NTStatus: STATUS_INVALID_PARAMETER
=============================================

Additionally I'm seeing this:

<FrsDsGetSubscribers: 340: 8239: S0: 17:14:31> S: No
NTFRSSubscriber object found under cn=dfs volumes,cn=ntfrs
subscriptions,cn=tombstone,ou=domain
controllers,dc=wilmnt,dc=onlc,dc=com!

The only other clue I've got going is that I'm seeing this when the
DNS starts:

=============================================
The zone wilmnt.onlc.com was previously loaded from the directory
partition MicrosoftDNS but another copy of the zone has been found in
directory partition DomainDnsZones.wilmnt.onlc.com. The DNS Server
will ignore this new copy of the zone. Please resolve this conflict as
soon as possible.
=============================================

Additionally this DC was upgraded to W2K3 from W2K. And the
default_first_site name was changed.

Everything seems to be working well regarding AD and DNS with the
exception of replication. I'd really like to figure out how to fix
this without totally starting over.

Can anybody offer a clue as to where to start?

Thanks.

Jim

 

[Lata]

Have you tried repadmin, replmon and sonar as troubleshooting tools?

All Windows 2000 support tools, I think..

Lata

 

[James Palic]

Lata,

I fired up sonar and saw that it was showing that the staging
directory was full on one of the DC's.

I stopped the File Replication Service on the computer with the full
staging directory then deleted all the files in the staging directory.
When I restarted FRS on that computer I was getting the classic 13552
and 13555 errors in the event log with the reason given as
FrsErrorMismatchedJournalId.

I stopped FRS on both computers and set the BURFLAG to D4 on the
computer with the good copy of SYSVOL and then started FRS on it. I
set the BURFLAG to D2 on the other computer and started FRS.

And to my amazement it appears to be replicating just fine again. The
computer with the D2 in the BURFLAG moved it's sysvol files to the
NTFRS_Preexisting directory and copied all of the files from the
computer with the D4 set.

So thanks for pointing me in the right direction!

Jim


So then

Have you tried repadmin, replmon and sonar as troubleshooting tools?

All Windows 2000 support tools, I think..

Lata

We have a very simple setup with two sites each with a W2K3 DC.
Apparently back in February the SYSVOL stopped replicating. AD info
seems to be replicating just fine. DNS seems to be working. DCDIAG
doesn't report any issues.

The only errors I'm seeing in regard to the files not replicating are
in the %systemroot%\debug\ntfrs_????.log files. I'm getting a series
that looks like this for each file that is attempting to replicate:

=============================================
<StuOpenDestinationFile: 1536: 653: S0: 17:14:07> :: CoG
65016561, CxtG 4e1ae42a, FV 3, FID 00060000 0000352a, FN: bath.txt
, [FrsForceOpenId failed. (ERROR_INVALID_PARAMETER)]

<StuExecuteInstall: 1536: 2271: S1: 17:14:07> WARN -
StuOpenDestinationFile failed. WStatus: ERROR_FILE_NOT_FOUND

<ProcessOpenByIdStatus: 1536: 3010: S1: 17:14:07> ++ 001D0000
00003416 Fid Open failed; NTStatus: STATUS_INVALID_PARAMETER

<FrsOpenSourceFileById: 1536: 3360: S0: 17:14:07> ++ ERROR -
NtCreateFile failed : NTStatus: STATUS_INVALID_PARAMETER
=============================================

Additionally I'm seeing this:

<FrsDsGetSubscribers: 340: 8239: S0: 17:14:31> S: No
NTFRSSubscriber object found under cn=dfs volumes,cn=ntfrs
subscriptions,cn=tombstone,ou=domain
controllers,dc=wilmnt,dc=onlc,dc=com!

The only other clue I've got going is that I'm seeing this when the
DNS starts:

=============================================
The zone wilmnt.onlc.com was previously loaded from the directory
partition MicrosoftDNS but another copy of the zone has been found in
directory partition DomainDnsZones.wilmnt.onlc.com. The DNS Server
will ignore this new copy of the zone. Please resolve this conflict as
soon as possible.
=============================================

Additionally this DC was upgraded to W2K3 from W2K. And the
default_first_site name was changed.

Everything seems to be working well regarding AD and DNS with the
exception of replication. I'd really like to figure out how to fix
this without totally starting over.

Can anybody offer a clue as to where to start?

Thanks.

Jim