FRS Replication Issue and a 13508 Event Error
Hi Everyone,
I'm reaching out for some help with an issue with two 2003 DCs. For the background:
I started working for a new company a month ago and found that Group Policy was not working (among other things). So I found that the adapter settings were not configured properly so I fixed it. Group Policy started to work again. But I am still Getting NtFrs errors with Event ID 13508 -
The File Replication Service is having trouble enabling replication from xxx-DC2 to xxx-DC1 for c:\windows\sysvol\domain using the DNS name xxx-dc2.xxx.xxx.org. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name xxx-dc2.xxx.xxx.org from this computer.
[2] FRS is not running on xxx-dc2.xxx.xxx.org.
[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.
DC2 does not have the error and it was the server that had proper settings
DC1 is the problem server (I would assume)
Does anyone have any ideas on how to remedy this? Also, should I be concerned about losing anything in SYSVOL when it starts replicating as DC1 is way out of sync.
Thanks for any help.
I'm reaching out for some help with an issue with two 2003 DCs. For the background:
I started working for a new company a month ago and found that Group Policy was not working (among other things). So I found that the adapter settings were not configured properly so I fixed it. Group Policy started to work again. But I am still Getting NtFrs errors with Event ID 13508 -
The File Replication Service is having trouble enabling replication from xxx-DC2 to xxx-DC1 for c:\windows\sysvol\domain using the DNS name xxx-dc2.xxx.xxx.org. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name xxx-dc2.xxx.xxx.org from this computer.
[2] FRS is not running on xxx-dc2.xxx.xxx.org.
[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.
DC2 does not have the error and it was the server that had proper settings
DC1 is the problem server (I would assume)
Does anyone have any ideas on how to remedy this? Also, should I be concerned about losing anything in SYSVOL when it starts replicating as DC1 is way out of sync.
Thanks for any help.
ASKER
Thanks iSiek,
I will try this and get back to you ASAP!
I will try this and get back to you ASAP!
No problem, you're welcome :)
take your time and read carfully this article. Do not use D4 burflag! Make sure that it was D2
and we'll try to bring back this env to life ;)
Krzysztof
take your time and read carfully this article. Do not use D4 burflag! Make sure that it was D2
and we'll try to bring back this env to life ;)
Krzysztof
ASKER
Will Do!
I have a few meetings coming up today. This might be one of those after hours, sit down in quiet and thoroughly fix this. I appreciate the support!
I have a few meetings coming up today. This might be one of those after hours, sit down in quiet and thoroughly fix this. I appreciate the support!
In addition i will also recommend to run diagnosis test dcdciag /q and repadmin /replsum and post the log if error is reported.
There are multiple reasons for event id 13508 to occur it could be due network latency issue.Ad sites and services are not set corectly,replication issue,dns misconfig,required port not open for AD replication,secure channel broken,tombstone DC,etc.
Troubleshooting File Replication Service
http://technet.microsoft.com/en-us/library/bb727056.aspx#EMAA
Best practices for DNS client settings on DC and domain members.
http://abhijitw.wordpress.com/2012/03/03/best-practices-for-dns-client-settings-on-domain-controller/
Hope this helps
There are multiple reasons for event id 13508 to occur it could be due network latency issue.Ad sites and services are not set corectly,replication issue,dns misconfig,required port not open for AD replication,secure channel broken,tombstone DC,etc.
Troubleshooting File Replication Service
http://technet.microsoft.com/en-us/library/bb727056.aspx#EMAA
Best practices for DNS client settings on DC and domain members.
http://abhijitw.wordpress.com/2012/03/03/best-practices-for-dns-client-settings-on-domain-controller/
Hope this helps
ASKER
Thanks Sandeshdubey I will look into this and post back any discrepancies,
I looked and noticed that I do not have Domain System Volume (Sysvol share) inside of Sysvol Seeding Registry folder. So it says that I need to make it, but I want to be sure that I know what I am making first. Does this seem right? The directions say:
Locate and then expand the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\
Note If this registry entry does not exist, you must create it.
So I'm guessing:
Create a folder inside of Sysvol Seeding called Domain System Volume (Sysvol share) <-do I even add the "(Sysvol share)" in the name?
The directions then say:
On the Edit menu, click New, click String Value, type Replica Set Parent, and then click OK.
In the right pane, right-click Replica Set Parent, click Modify, type the name of a domain controller that has the Sysvol data that you want to replicate in the Value data box, and then click OK.
I get adding the Replica Set Parent part but for the name of a domain controller, should I just add the name xxx-dc2 or should it be the FQDN?
Thanks for all the help guys
I looked and noticed that I do not have Domain System Volume (Sysvol share) inside of Sysvol Seeding Registry folder. So it says that I need to make it, but I want to be sure that I know what I am making first. Does this seem right? The directions say:
Locate and then expand the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\
Note If this registry entry does not exist, you must create it.
So I'm guessing:
Create a folder inside of Sysvol Seeding called Domain System Volume (Sysvol share) <-do I even add the "(Sysvol share)" in the name?
The directions then say:
On the Edit menu, click New, click String Value, type Replica Set Parent, and then click OK.
In the right pane, right-click Replica Set Parent, click Modify, type the name of a domain controller that has the Sysvol data that you want to replicate in the Value data box, and then click OK.
I get adding the Replica Set Parent part but for the name of a domain controller, should I just add the name xxx-dc2 or should it be the FQDN?
Thanks for all the help guys
No, you may simply skip steps 9-12 and this will work fine too :)
Krzysztof
Krzysztof
ASKER
I have also found that the DC that is fully up to date has this error:
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:\windows\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\
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.
I am looking into this right now
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:\windows\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\
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.
I am looking into this right now
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks Prash,
I notice that your directions say, "If One server in a domain......." I have two DCs. Would these directions still apply?
I notice that your directions say, "If One server in a domain......." I have two DCs. Would these directions still apply?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks Sandy,
I just did this an hour ago. I went to the healthy DC and ran d4 then went to the other DC and did d2.
Should I change the Burflags back to 0 now?
You guys are super human! Thanks for the help!!!
I just did this an hour ago. I went to the healthy DC and ran d4 then went to the other DC and did d2.
Should I change the Burflags back to 0 now?
You guys are super human! Thanks for the help!!!
ASKER
Thanks Again!!
Please check how this process looks like at
http://support.microsoft.com/kb/840674/pl
Regards,
Krzysztof