HELP - SYSVOL folder is not replicating

[halifax21]

Hi all

I have 2 windows 2000 server DC, one is the default first site name server.

It only be lately that i have added the second DC. The are both configured as GC servers.

However, on the second DC that I have installed I am still getting the error below -

Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13508
Date: 22/09/2003
Time: 12:03:11
User: N/A
Computer: PDCBACKUP
Description:
The File Replication Service is having trouble enabling replication from INTOUCHPDC to PDCBACKUP for c:\winnt\sysvol\domain using the DNS name intouchpdc.intouch.com. FRS will keep retrying.
Following are some of the reasons you would see this warning.

[1] FRS can not correctly resolve the DNS name intouchpdc.intouch.com from this computer.
[2] FRS is not running on intouchpdc.intouch.com.
[3] The topology information in the Active Directory for this replica has not yet replicated to all the Domain Controllers.

This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.

On teh Second DC i can see all the users and group information however, It looks like the SYSVOL share on the first Dc is not beeing copied across to the new second DC.

I looked the debug log folder on the first DC and had a look at the NtFrs_0005.log and found

<FrsDsVerifyPromotionParent: 2868: 5190: S0: 13:49:40> :S: ERROR - DOMAIN SYSTEM VOLUME (SYSVOL SHARE) does not exist on INTOUCHPDC!
<LOCAL_FrsRpcVerifyPromotionParent:2868: 1425: S0: 13:49:40> ++ ERROR - verifying set DOMAIN SYSTEM VOLUME (SYSVOL SHARE) on parent INTOUCHPDC; WStatus: ERROR_NOT_FOUND
<SERVER_FrsRpcStartPromotionParent:2868: 1528: S0: 13:49:40> ++ ERROR - verify; WStatus: FRS_ERR_SYSVOL_POPULATE
<FrsDsFindComputer: 2812: 8375: S2: 13:49:59> S: Computer FQDN is cn=intouchpdc,ou=domain controllers,dc=intouch,dc=com
<FrsDsFindComputer: 2812: 8381: S2: 13:49:59> S: Computer's dns name is intouchpdc.intouch.com
<FrsDsFindComputer: 2812: 8395: S2: 13:49:59> S: Settings reference is cn=ntds settings,cn=intouchpdc,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=intouch,dc=com
<ThSupWaitThread: 2212: 501: S1: 13:50:59> :S: ReplicaCs: Waiting
<ThSupWaitThread: 2212: 529: S1: 13:50:59> :S: ReplicaCs: normal wait

It says the (SYSVOL SHARE) does not exist on INTOUCHPDC -

But it does and it is shared

Here is the result for the dcdiag below

Of the errors from the first DC

Starting test: frssysvol
Error: No record of File Replication System, SYSVOL started.
The Active Directory may be prevented from starting.
......................... INTOUCHPDC passed test frssysvol

ANd errors form the Second DC -

Starting test: Advertising
Warning: DsGetDcName returned information for \\intouchpdc.intouch.com,
when we were trying to reach PDCBACKUP.
Server is not responding or is not considered suitable.

Starting test: frssysvol
Error: No record of File Replication System, SYSVOL started.
The Active Directory may be prevented from starting.
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.

Something is not right I see- but what?

I have check the DNS name on our DNS server and all seems fine.

It looks like the first DC SYSVOL folder is not replicating to the second server- how can i solve this problem?

Thanks

James

 

[ReddLefty]

It could be DNS issues but I had the exact above error and I had reinstalled and moved DCs serveral times but I could never get the replica to start and that exact error would always occur, saying that the FRS and SysVOL were preventing the replication. I won't get into the reasons why, but are there any values inside the following registry key of the newest DC?

HKEY_LOCAL_MACHINE \ System \ CurrentControlSet \ Services \ NTFRS \ Sysvol

If so, in order for the replication to begin, there must be no entries inside the Sysvol key. If there is, remove the entries inside the key but do not remove the key itself.

Hope this helps.



&quot;In space, nobody can hear you click...&quot;

 

[halifax21]

Hi

I just had a look in HKEY_LOCAL_MACHINE \ System \ CurrentControlSet \ Services \ NTFRS \ Sysvol on teh newest Dc

And there was a Default REG_SZ (Value not set)

Should I delete this?

If i do will replication of teh Sysvol work?

Thanks

James

 

[ReddLefty]

No, that setting is fine.

Check also in

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters]

and make sure that Sysvol path is ok and that SysVolReady = 1 (yes). 0(zero) = no.

Restart your NTFRS service if you change anything in those registry setting... and make a backup first



&quot;In space, nobody can hear you click...&quot;

 

[halifax21]

I just had a look at [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters]

But the not mention of the Sysvol path or SysVolReady = 1 (yes). 0(zero) = no.

what u think?

Thanks

James

 

[halifax21]

On the first DC the [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters] looks ok

I ran the dcdiag and it look ok but for this

Domain membership test . . . . . . : Failed
[WARNING] Ths system volume has not been completely replicated to the local machine. This machine is not working properly as a DC.

However, when i look in the active directory replication monitor - all the replication says it the last attempt was successful.

What you think?

thank

James

 

[mlichstein]

However, when i look in the active directory replication monitor - all the replication says it the last attempt was successful."

File replication and AD replication are different beasts. Replmon monitors AD replication, and sysvol uses file replication. File replication depends on AD replication, so if that is working that is good.

However, you still need to get FRS working correctly. Setting sysvolready to 1 should not be necessary, the system will do it on it's own if it replicates successfully.

I would focus on this error:
Warning: DsGetDcName returned information for \\intouchpdc.intouch.com,
when we were trying to reach PDCBACKUP.

Check your DNS, and make sure the records are correct.

 

[ianbnet]

I'm getting these exact errors and have been banging my head against them for two full days now. AD Replication is working fine, but FRS is failing with a 13508 error. DNS is fine, and both machines can resolve each other.

The only problem I can see that is left is that the browser on the second (i.e. non-replicated) machine is failing with the error:

The browser service has failed to retrieve the backup list too many times on transport \Device\NetBT_Tcpip_{82A513A3-0827-4F26-B867-FE192B23BDB9}. The backup browser is stopping.

I can't see how this is related, but I thought I would post it. So I'm going to be following this thread closely... AARRGH!!

 

[ianbnet]

I also am getting JRNL_WRAP errors on the 1st DC (the one with the working sysvol). I tried to fix these, but have been unable, and figure these might be causing hte problem?

The error is:

Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13568
Date: 4/23/2004
Time: 12:04:30 PM
User: N/A
Computer: FRANKLIN
Description:
The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.

Replica set name is : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
Replica root path is : "c:\winnt\sysvol\domain"
Replica root volume is : "\\.\C:"
A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found. This can occur because of one of the following reasons.

[1] Volume "\\.\C:" has been formatted.
[2] The NTFS USN journal on volume "\\.\C:" has been deleted.
[3] The NTFS USN journal on volume "\\.\C:" has been truncated. Chkdsk can truncate the journal if it finds corrupt entries at the end of the journal.
[4] File Replication Service was not running on this computer for a long time.
[5] File Replication Service could not keep up with the rate of Disk IO activity on "\\.\C:".
Setting the "Enable Journal Wrap Automatic Restore" registry parameter to 1 will cause the following recovery steps to be taken to automatically recover from this error state.
[1] At the first poll, which will occur in 5 minutes, this computer will be deleted from the replica set. If you do not want to wait 5 minutes, then run "net stop ntfrs" followed by "net start ntfrs" to restart the File Replication Service.
[2] At the poll following the deletion this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set.

WARNING: During the recovery process data in the replica tree may be unavailable. You should reset the registry parameter described above to 0 to prevent automatic recovery from making the data unexpectedly unavailable if this error condition occurs again.

To change this registry parameter, run regedit.

Click on Start, Run and type regedit.

Expand HKEY_LOCAL_MACHINE.
Click down the key path:
"System\CurrentControlSet\Services\NtFrs\Parameters"
Double click on the value name
"Enable Journal Wrap Automatic Restore"
and update the value.

If the value name is not present you may add it with the New->DWORD Value function under the Edit Menu item. Type the value name exactly as shown above.

 

[mlichstein]

If you are running SP4, you need to have at least 512Mb of free space, or you will get journal wraps.

 

[ianbnet]

I resolved this today by completely removing the DNS service from the 2nd (non-replicating) domain controller.

Now I just need to figure out what was going wrong...

 

[AndyMac]

Ianbnet, did you manage to get the FRS running again. Have the same FRS error but have been unable to get this to restart even when have made space on the disk. Have run CHKDSK also. Just need to get a replica accross to the new DC and it will not matter. However not running DNS on the new DC which is also 2003.

 

[ReddLefty]

AndyMac,

The error that Ianbnet has posted is not related to the FRS. That error is usually because you have two network cards and both have TCP/IP and NetBIOS over TCP/IP enable.

You need to disable the NetBIOS over TCP/IP on the TCP/IP protocol on one of your network cards. Prefferably the one that is not on your main network.



&quot;In space, nobody can hear you click...&quot;