Error 13509 Ntfrs
Contents |
additional information might be available elsewhere. Thank you for searching on this message; your search helps us identify those
The File Replication Service Is Having Trouble Enabling Replication From 13508
areas for which we need to provide more information. If the product or version you are looking for is not listed, you can use this search box to search TechNet, the Microsoft Knowledge Base, and TechNet Blogs for more information. Enter the product name, event source, and event ID. For example: Vista Application Error 1001.
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by:
Ntfrs 13568
FRS problem - event ID 13508 (without 13509) Windows Server > ntfrs 13508 server 2012 r2 Directory Services Question 0 Sign in to vote Hi everyone, Thank you for your help in advanced. ntfrs force replication I have been searching for couple hours before coming for help~~ I read so many articles but could not find any clue yet. I have 7 sites, and the https://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Windows+Operating+System&ProdVer=5.2&EvtID=13508&EvtSrc=NtFrs Windows 2003 DC servers have been running for 4 years.Now, all in a sudden, one single DC for a site is having an event ID 13508 (since Feb). It said the "File Replcation Service is having trouble enable replication from server A to Server B for d:\windows\sysvol\domain using the DNS domain name.... the FRS will keep retries...etc". https://social.technet.microsoft.com/Forums/windowsserver/en-US/0bb3d213-f266-422e-9ff2-64a23e552af0/frs-problem-event-id-13508-without-13509?forum=winserverDS I followed one of the technets and verify each mentioned, including running repadmin /showreps and /showconn, netdiag, NTFRSUtl version
Analyzer Sample report Advanced filtering Direct links to www.eventid.net Email notifications Scheduled reporting Free for subscribers EventReader Event Viewer Sample report Custom views/filters Servers list, organized in groups Integration with EventID.Net http://www.eventid.net/display-eventid-13508-source-NtFrs-eventno-349-phase-1.htm Consolidated view for all logs Free for subscribers Event ID: 13508 Source: NtFrs Source: NtFrs Type: Warning Description:The File Replication Service is having trouble enabling replication from
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > FILE REPLICATION SERVICE is having trouble. Event ID 13508 Want to Advertise Here? Solved FILE REPLICATION SERVICE is having trouble. Event ID 13508 Posted on 2006-02-16 Windows Server 2003 1 Verified Solution 13 Comments 39,588 Views 1 Ratings Last Modified: 2011-09-04 can't get this error to stop coming up in event viewer. just built a new DC to be a backup netlogon for my primary DC. DNS looks OK, but am I missing anytning? the netlogon share is not being created and i think its due to this error. HELP! I can Ping it, resolve the names etc. is this problem on my Primary DC? THe steps below seem not to help at all. ----------------------- Event Type: Warning Event Source: NtFrs Event Category: None Event ID: 13508 Date: 2/16/2006 Time: 7:13:51 PM User: N/A Computer: YODA Description: The File Replication Service is having trouble enabling replication from \\SERVER0.DOMAIN.local to YODA for c:\windows\sysvol\domain using the DNS name \\SERVER0.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 \\SERVER0.DOMAIN.local from this computer. [2] FRS is not running on \\SERVER0.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. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 00 00 00 00 .... 1 Question by:CBIA Facebook Twitter LinkedIn Google LVL 22 Best Solution byjvuz http://www.microsoft.com/technet/prodtechnol/windows2000serv/technologies/activedirectory/maintain/opsguide/part1/adogd11.mspx#ENAA Go to Solution 13 Comments LVL 22 Overall: Level 22 Windows Server 2003 3 Message Accepted Solution