Event ID: 13508 - The File Replication Service is having trouble enabling replicatiing
I am getting the following event warning on our Primary DC.
Computer: SERVER1
Monitor Title: "Event Log Errors" (Type=Event Log Monitor)
Description:
* Event Time: 2012/01/05 12:22:53 PM
* Source: NtFrs
* Type: Warning Event
* Event ID: 13508
* The File Replication Service is having trouble enabling replication from SERVER2 to SERVER1 for c:\windows\sysvol\domain using the DNS name Server2.domain.local. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name Server2.domain.local from this computer.
[2] FRS is not running on Server2.domain.local.
[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.
--------------------------
Details:
Server1 - Windows 2008 STD (64Bit) - DC with all FSMO role running from here.
Server2 - Windows Server 2003 STD (32Bit) - DC - Exchange 2003
- I have checked and do not get any Event logs for EventID 13509 to say it has been resolved.
- FRS is running on both servers
- I can ping both servers from each other.
- ntfrsutl server2.domain.local runs successfully from Server1
- I have checked DNS and that seens to be running fine too.
Are there any other suggestions?
Computer: SERVER1
Monitor Title: "Event Log Errors" (Type=Event Log Monitor)
Description:
* Event Time: 2012/01/05 12:22:53 PM
* Source: NtFrs
* Type: Warning Event
* Event ID: 13508
* The File Replication Service is having trouble enabling replication from SERVER2 to SERVER1 for c:\windows\sysvol\domain using the DNS name Server2.domain.local. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name Server2.domain.local from this computer.
[2] FRS is not running on Server2.domain.local.
[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.
--------------------------
Details:
Server1 - Windows 2008 STD (64Bit) - DC with all FSMO role running from here.
Server2 - Windows Server 2003 STD (32Bit) - DC - Exchange 2003
- I have checked and do not get any Event logs for EventID 13509 to say it has been resolved.
- FRS is running on both servers
- I can ping both servers from each other.
- ntfrsutl server2.domain.local runs successfully from Server1
- I have checked DNS and that seens to be running fine too.
Are there any other suggestions?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You don't need to take any action EventID 13509 indicates problem is resolved. Ignore it.
Helllo?? "- I have checked and do not get any Event logs for EventID 13509 to say it has been resolved."
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
@Neilsr Thanks for pointing. I missed that :)
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hi Box,
@Neilsr kindly read the following :-
By doing D2 you will do non-authoratative restore
.Kindly go through the following article -- http://support.microsoft.com/kb/315457
When,you are modifying the following key :-
"HKEY_LOCAL_MACHINE\System
Insted make changes to HKEY_LOCAL_MACHINE\System\
D4 on FSMO role holder and D2 on the ADC.As Microsoft says that FSMO role holder specially the one which has PDC role is the GOOD DC...!!
Note:--Take a back up of SYSVOL
Hopw this helps !!!
@Neilsr kindly read the following :-
By doing D2 you will do non-authoratative restore
.Kindly go through the following article -- http://support.microsoft.com/kb/315457
When,you are modifying the following key :-
"HKEY_LOCAL_MACHINE\System
Insted make changes to HKEY_LOCAL_MACHINE\System\
D4 on FSMO role holder and D2 on the ADC.As Microsoft says that FSMO role holder specially the one which has PDC role is the GOOD DC...!!
Note:--Take a back up of SYSVOL
Hopw this helps !!!
You should get the DC logging the 13568 event out of the Journal Wrap state by setting the Burflags regisry key to "d2" (hex) and restart the ntfrs service.
Setting the Burflags to "d4" is not necessary and should only be set when you'll have to rebuild the replica set. You don't want that.
Setting the Burflags to "d4" is not necessary and should only be set when you'll have to rebuild the replica set. You don't want that.
ASKER
All help appreciated.
Server1 is your PDC?
Server2 is your ADC?
DNS is AD integrated?
Also, can you post nslookup results of machine?