13508 Frs Error
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove frs error 13568 From My Forums Answered by: FRS 13508 Error - HELP!? Windows
Frs 13508 Without 13509
Server > Directory Services Question 0 Sign in to vote Hi. I have 2 DCs,
Frs Event 13508
PDC (2k8) and PDC1 (2k8R2). I recently promoted PDC1 to become a DC and replication occured without error. However now I get the FRS 13508 error
File Replication Service Error 13508
and replication will not happen. Can some have a look at my dcdiags below and tell me what is wrong. I can ping both servers from each other and they resolve correctly. I have removed our domain name and some AV errors. DCDIAG from PDC: Directory Server Diagnosis Performing initial setup: Trying ntfrs error 13508 to find home server... Home Server = PDC * Identified AD Forest. Done gathering initial info. Doing initial required tests Testing server: Default-First-Site-Name\PDC Starting test: Connectivity ......................... PDC passed test Connectivity Doing primary tests Testing server: Default-First-Site-Name\PDC Starting test: Advertising Warning: PDC is not advertising as a time server. ......................... PDC failed test Advertising Starting test: FrsEvent There are warning or error events within the last 24 hours after the SYSVOL has been shared. Failing SYSVOL replication problems may cause Group Policy problems. ......................... PDC passed test FrsEvent Starting test: DFSREvent There are warning or error events within the last 24 hours after the SYSVOL has been shared. Failing SYSVOL replication problems may cause Group Policy problems. ......................... PDC failed test DFSREvent Starting test: SysVolCheck ......................... PDC passed test SysV
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring the file replication service is having trouble enabling replication 13508 developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ event id 13508 ntfrs windows 2008 r2 Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how event id 13508 ntfrs windows 2012 r2 it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top New Domain controller is having trouble replicating from an existing DC, 13508 Event ID for FRS up vote 4 https://social.technet.microsoft.com/Forums/windowsserver/en-US/88f45cb5-6057-4b35-815e-791cc0575263/frs-13508-error-help?forum=winserverDS down vote favorite This question is related to a previous one I asked regarding backing up Domain Controllers and RODC's. Basically I am making some changes in regards to the DC's in my network. I am looking to add a writable 2008R2 DC as well as a 2008R2 RODC to my domain. I have created a writable 2008R2 DC called "DC-04", it is set up and appears to be working fine with one exception. When I run dcdiag /v on http://serverfault.com/questions/417159/new-domain-controller-is-having-trouble-replicating-from-an-existing-dc-13508-e this new domain controller, I get an error during the FRS event test. This error corresponds to Event 13508 that I am getting and it states: "The File Replication Service is having trouble enabling Replication from DC-02 to DC-04 for c:\windows\sysvol\domain using the DNS name dc-02.domain.com. FRS will keep retrying." Some information that may be helpful: DC-02 is running 2003R2 x86, it also holds all 5 FSMO roles There is another DC called DC-03 also running 2003R2 x86, no errors come up on DC-04 regarding replication from this DC All DC's are Global Catalogs and have DNS I can ping dc-02.domain.com from dc-04, so DNS seems ok FRS service is running on DC-02 Any ideas or things to check would be greatly appreciated. Thanks! active-directory replication domain-controller file-replication-services share|improve this question edited Aug 13 '12 at 21:45 asked Aug 13 '12 at 20:50 Mike 501315 Ugh, FRS sucks. I mean, really sucks. Is it possible to upgrade to DFS or DFS-R? (2k8 FL required, IIRC.) That's the first thing I'd try, because FRS just doesn't work and is such a massive pain to fix that it's best to not use it if at all possible. –HopelessN00b Aug 15 '12 at 2:26 add a comment| 3 Answers 3 active oldest votes up vote 1 down vote accepted +50 Usually these sorts of issues are related to DNS in some way. I would start by verifying the Client DN
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 https://www.experts-exchange.com/questions/26426708/Active-Directory-FRS-error-13508-in-FRS-Event-Log.html Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Active Directory https://www.experts-exchange.com/questions/28197729/FRS-Replication-Issue-and-a-13508-Event-Error.html FRS error 13508 in FRS Event Log Want to Advertise Here? Solved Active Directory FRS error 13508 in FRS Event Log Posted on 2010-08-24 Active Directory Windows Server 2003 Networking 1 Verified Solution 96 Comments 7,737 Views 1 Ratings Last Modified: 2012-05-10 Well I have been working on this problem for awhile now and I just can't seem to figure it out. Here is what frs error is going on: A couple of weeks ago as I was doing some research into replacing some of my aging DCs I came across an error that I can't seem to remedy. I was running DCDIAG just to check and make sure there wasn't any errors and I found one. All tests would pass except the Netlogons test and the FRSEvent test when running DCDIAG. I get the following output for this test: Starting test: NetLogons * file replication service Network Logons Privileges Check Unable to connect to the NETLOGON share! (\\SERVER\netlogon) [SERVER] An net use or LsaPolicy operation failed with error 1203, No network provider accepted the given network path.. ......................... SERVER failed test NetLogons I also fail the FRSEVENT test with the error: Starting test: frsevent * The File Replication Service Event log test There are warning or error events within the last 24 hours after the SYSVOL has been shared. Failing SYSVOL replication problems may cause Group Policy problems. An Warning Event occured. EventID: 0x800034C4 Time Generated: 08/23/2010 22:49:31 (Event String could not be retrieved) ......................... SERVER failed test frsevent So I did some research and was directed towards the FRS Event Logs. Once I looked in there I saw the following error: The File Replication Service is having trouble enabling replication from
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 > FRS Replication Issue and a 13508 Event Error Want to Advertise Here? Solved FRS Replication Issue and a 13508 Event Error Posted on 2013-07-29 Active Directory Windows Server 2003 3 Verified Solutions 14 Comments 3,584 Views 1 Ratings Last Modified: 2013-08-05 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 losin