Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
The File Replication Service is having trouble enabling replication from <server> to <server> for <path> using the DNS name <name>. FRS will keep retrying.
Following are some of the reasons you would see this warning.
 FRS can not correctly resolve the DNS name <name> from this computer.
 FRS is not running on <name>.
 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.
|English: This information is only available to subscribers. An example of English, please!|
See also the link to "EventID 13508 from source NtFrs" for comments about an almost identical type of problem.
This problem can be caused by multiple reverse lookup addresses for the server name.
I had event 13508 and was having problems with replication between source and target. The orphaned folder started with the same name as the original but was auto-appended with a GUID like name to the end. The target had both the original folder and the one it came into conflict.
After beating my head against the wall and looking at the suspect files with Group Policy Management tool (GPMC – invaluable tool, a must download free tool from Microsoft) I went into the “Frs-Staging” folder on the failed target machine. Inside were the annoying conflicts. I deleted all the files and then restarted the File Replication Service on both machines. Replication started working again. I checked the original folder to see if there was any data that needed to be copied to the orphan folder that was now replicating and then deleted the original folder. Lastly, I renamed the orphan folder to its original name and the problem was solved.
As per Microsoft: "This message informs you that the File Replication service (FRS) cannot complete the Remote Procedure Call (RPC) connection to a specific replication partner because FRS cannot enable replication with that partner. FRS will continue trying to complete the connection". See MSW2KDB for more information on this event.
|Private comment: Subscribers only. See example of private comment|
|Links: Group Policy Management Console, EventID 13508 from source NtFrs|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
|Custom search for *****: Google - Bing - Microsoft - Yahoo|
Send comments or solutions
- Notify me when updated