Replication failing - SYSVOL data doesn't match between servers

  • Thread starter Thread starter Stuart
  • Start date Start date
S

Stuart

Hi. We have a Win2k Adv Server network with some servers, 2 DCs. We had a
motherboard failure in our main DC and the secondary DC took over as
expected. On replacing the failed hardware and restarting the main DC
everything started working again as expected and appeared to be for the last
few days.

I have since made changes to Group Policy and added and removed some users.
I noticed today that Ntfrs is reporting JRNL_WRAP_ERRORs with Event ID 13568
on one server and it looks as though replication is not taking place. If I
restart one server the the other starts to display the JRNL_WRAP_ERROR.
I've been through all the basic testing with DCDiag, NetDiag, Gpotool as
well as confrming DNS settings and attempting to initiate replication
between the servers via Active Directory. The general server settings seems
correct but on checking the SYSVOL I have found the servers contain
different group policies, one contains all the latest policies and seems
upto date, but the second DC has a lot of the old policied and a couple of
the new ones but with incorrect time stamps.

I really need to get this problem resolved. I've searched online and so far
the only document which I haven't tried is using the BurFlags registry key
to reinitialise file replication. On reading the document though it doesn't
seem the most optimistic or 'safe' way to resolve the problem.

Can anyone advise what other options I should consider ? e.g. should I
demote the server back to a member server and then promote it back to a DC
to allow replication to restart ?

Thanks for any help,
Stuart.

[Sorry for posting seperately to two groups, I forgot to cross-post]
 
As long as all the FSMO roles have been transferred to the secondary server,
and if DNS and DHCP are stable on the secondary server, I'd demote and
promote the primary server to see if that clears up the problem. I'd bet it
will. Did the motherboard have an onboard NIC? If so that may be
contributing to your problem.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm
 
Hi Richard. Thanks for your reply. I will check on the servers but
confusingly I belive all FSMO roles are still on the primary server. I'm
wondering whether there were any particular configufration issues prior to
the primary failure causing the secondary not to take full control. The
primary server was only down for a day or so. I will double check, but if
this is the case how would this influence your suggestion ? The other issue
is that the Primary server which is now the one logging JRNL_WRAP_ERRORs is
the server which has all the correct SYSVOL entries and seems to be the most
upto date. If I demoted the primary how would this affect the older
policies still stored on the secondary server ?

The motherboard does have an onboard NIC but it isn't being used.

Thanks again,
Stuart.

Richard G. Harper said:
As long as all the FSMO roles have been transferred to the secondary
server, and if DNS and DHCP are stable on the secondary server, I'd demote
and promote the primary server to see if that clears up the problem. I'd
bet it will. Did the motherboard have an onboard NIC? If so that may be
contributing to your problem.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


Stuart said:
Hi. We have a Win2k Adv Server network with some servers, 2 DCs. We had
a
motherboard failure in our main DC and the secondary DC took over as
expected. On replacing the failed hardware and restarting the main DC
everything started working again as expected and appeared to be for the
last
few days.

I have since made changes to Group Policy and added and removed some
users.
I noticed today that Ntfrs is reporting JRNL_WRAP_ERRORs with Event ID
13568
on one server and it looks as though replication is not taking place. If
I
restart one server the the other starts to display the JRNL_WRAP_ERROR.
I've been through all the basic testing with DCDiag, NetDiag, Gpotool as
well as confrming DNS settings and attempting to initiate replication
between the servers via Active Directory. The general server settings
seems
correct but on checking the SYSVOL I have found the servers contain
different group policies, one contains all the latest policies and seems
upto date, but the second DC has a lot of the old policied and a couple
of
the new ones but with incorrect time stamps.

I really need to get this problem resolved. I've searched online and so
far
the only document which I haven't tried is using the BurFlags registry
key
to reinitialise file replication. On reading the document though it
doesn't
seem the most optimistic or 'safe' way to resolve the problem.

Can anyone advise what other options I should consider ? e.g. should I
demote the server back to a member server and then promote it back to a
DC
to allow replication to restart ?

Thanks for any help,
Stuart.

[Sorry for posting seperately to two groups, I forgot to cross-post]
Click to expand...
Click to expand...
 
At this point you will likely need to do some fixing-up of policies and such
on the remaining server, but with a little luck you may get one last
successful replication from the old primary server before it goes down. I
wouldn't want you to count on it, but you might get lucky.

I would start here and try to transfer the roles using the built-in GUI
tools:

http://support.microsoft.com/?kbid=255690

But it may come down to this rather ugly process instead:

http://support.microsoft.com/kb/255504

Oh yes, and be sure you have a Global Catalog on the remaining server before
demoting the first server if you don't have the GC there already:

http://support.microsoft.com/?kbid=313994

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm
 
I suspect that the primary did not have the global catalog and the
secondary did. It didn't transfer the FSMO or AD roles on it's own
and you have a partial GC working on one of the secondary DC's.
Try transferring the GC to your main DC or primary DC. Force
replication via the Sites and Services NTDS area, then put the Global
catalog back on your secondary. Check out if you're getting a Schema
error and try reloading it.

Just some thoughts....
 
Back
Top