NTFRS

[RobWUK]

I have two DCs on a site. One a Windows 2000 SP4 and the other Windows 2003
- no other controllers.

I have no Sysvol on the Windows 2003 server. On the Windows 2000 server I
have a sysvol which is populated correctly. The domain is functioning ok as
long as the sysvol/netlogon server is up.

On the windows 2000 with sysvol I get the dreaded ntfrs Event ID 13568. On
the Windows 2003 its a simple replication failure message - cannot contacted
etc.

On the 2000 box -

The File Replication Service has detected that the replica set "DOMAIN
SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.


I have seen various KBs about this but not sure what my best solution is.
One I have seen suggests the burflag D4 on the Windows 2000 and D2 on the
2003 to get it to authorative restore the sysvol.

Any suggestions welcome.

 

[Meinolf Weber]

Hello RobWUK,

RUn diagnostic tools on both DC's to check for errors. dcdiag /v, netdiag
/v and repadmin /showreps If you get errors post the complete output here.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

 

[RobWUK]

Hi Meinolf,

Yes there are a few errors but he output is too large to post fully.

I get FSMO role error in the Win2000 machine - these are ok on Win2003 which
is the role hold for all but infrastucture.

I have no outbound replication showing from repadmin on Win2003 machine.

Win2000 -
Running enterprise tests on : rasoft.co.uk
Starting test: Intersite
Skipping site Default-First-Site-Name, this site is outside the scope

provided by the command line arguments provided.
......................... rasoft.co.uk passed test Intersite
Starting test: FsmoCheck
GC Name: \\win2000.rasoft.co.uk
Locator Flags: 0xe00001fc
Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355
A Primary Domain Controller could not be located.
The server holding the PDC role is down.
Time Server Name: \\win2000.rasoft.co.uk
Locator Flags: 0xe00001fc
Preferred Time Server Name: \\win2000.rasoft.co.uk
Locator Flags: 0xe00001fc
KDC Name: \\win2000.rasoft.co.uk
Locator Flags: 0xe00001fc
......................... rasoft.co.uk failed test FsmoCheck

The command completed successfully
Default-First-Site-Name\WIN2000
DSA Options : IS_GC
objectGuid : eea5afd6-6376-4fa1-80f4-4f427c7fe1da
invocationID: eea5afd6-6376-4fa1-80f4-4f427c7fe1da

==== INBOUND NEIGHBORS ======================================

CN=Schema,CN=Configuration,DC=rasoft,DC=co,DC=uk
Default-First-Site-Name\WIN2003 via RPC
objectGuid: a2fc0e91-d832-4079-a6f1-a7819d078b3b
Last attempt @ 2008-05-14 09:57.51 was successful.

CN=Configuration,DC=rasoft,DC=co,DC=uk
Default-First-Site-Name\WIN2003 via RPC
objectGuid: a2fc0e91-d832-4079-a6f1-a7819d078b3b
Last attempt @ 2008-05-14 09:57.51 was successful.

DC=rasoft,DC=co,DC=uk
Default-First-Site-Name\WIN2003 via RPC
objectGuid: a2fc0e91-d832-4079-a6f1-a7819d078b3b
Last attempt @ 2008-05-14 10:03.07 was successful.

==== OUTBOUND NEIGHBORS FOR CHANGE NOTIFICATIONS ============

CN=Schema,CN=Configuration,DC=rasoft,DC=co,DC=uk
Default-First-Site-Name\WIN2003 via RPC
objectGuid: a2fc0e91-d832-4079-a6f1-a7819d078b3b

CN=Configuration,DC=rasoft,DC=co,DC=uk
Default-First-Site-Name\WIN2003 via RPC
objectGuid: a2fc0e91-d832-4079-a6f1-a7819d078b3b

DC=rasoft,DC=co,DC=uk
Default-First-Site-Name\WIN2003 via RPC
objectGuid: a2fc0e91-d832-4079-a6f1-a7819d078b3b

 

[Meinolf Weber]

Hello RobWUK,

Please post an unedited ipconfig /all from both DC's. Also check in a command
line on both DC's with "netdom query /domain:yourdomain FSMO" without the
qoutes and put the output here.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

 

[RobWUK]

I think I have resolved it. Added the registry key for auto recovery on the
one with the WRAP_Error and now it has re-enabled replication of the sysvol
on both.

I was worried this would create a new sysvol but it hasn't so it looks to be
working. The window2003 machine is now reporting success on the widnows 2003
machine and sysvol is populated.

Also passing FSMO test on the 2000 machine.

Looks to have been this way for months, I only was looking in detail as I am
adding a Windows 2007 exchange server and wanted to check the domain was ok
before domain prep.

Many thanks.

 

[Meinolf Weber]

Hello RobWUK,

If not run do again a check with dcdiag, netdiag and repadmin. Also wait
some days before starting, to be sure your errors will not come back. I would
also restart the servers to check for errors after reboot, but do one after
the other not both together.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm