13508 Error Frs
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) 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: FRS 13508 Error - HELP!? frs error 13568 Windows Server > Directory Services Question 0 Sign in to vote Hi. I frs 13508 without 13509 have 2 DCs, PDC (2k8) and PDC1 (2k8R2). I recently promoted PDC1 to become a DC and replication occured
Frs Event 13508
without error. However now I get the FRS 13508 error and replication will not happen. Can some have a look at my dcdiags below and tell me what is wrong. I
File Replication Service Error 13508
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 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 the file replication service is having trouble enabling replication 13508 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 SysVolCheck Starting test: KccEvent ......................... PDC passed test KccEvent Starting test: KnowsOfRoleHolders [PDC1] DsBindWithSpnEx() failed with error -2146893022, The target principal name is incorrect.. Warning: PDC1 is the Schema Owner, but is not responding to DS RPC Bind. [PDC1] LDAP bind failed with error 8341, A directory service error has occurred.. Warning
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
Event Id 13508 Ntfrs Windows 2008 R2
Overflow the company Business Learn more about hiring developers or posting ads with us event id 13508 ntfrs windows 2012 r2 Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network frs event id 13508 without frs event id 13509 administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Active Directory FRS https://social.technet.microsoft.com/Forums/windowsserver/en-US/88f45cb5-6057-4b35-815e-791cc0575263/frs-13508-error-help?forum=winserverDS problems. 13508 error and other problems up vote 2 down vote favorite 1 I have 3 Domain Controllers. We will call them DC1, DC2 and DC3. DC3 and DC2 show Event ID 13508 in their FRS logs with no follow-up event(13509 I think) to say the error had been fixed. DC1's FRS log no matter what you do never shows any events besides FRS service stopped and started. DC1 holds the SYSVOL http://serverfault.com/questions/198351/active-directory-frs-problems-13508-error-and-other-problems that needs to be replicated to the other DC's. The other DC's sysvol folders are empty. I have tried the burflag method of fixing this but I haven't had any luck. My procedure for that was to stop all FRS services on all DC's. Then set the burflag on DC1 to D4 and the other two DCs burflag to D2. Started FRS on DC1 and the only event's I see in DC1's FRS event logs are service stopped and service started messages. This fact is leading me to believe that something is wrong on FRS for DC1. I believe there should be events 13553 and 13516 in the FRS event logs after an authoritative sysvol restore. The other two DC's do not have anything in their SYSVOL, otherwise I would have made one of them the authoritative sysvol. DC1 is MS Server 2003 Enterprise Edition SP2 DC2 is MS Server 2003 Standard Edition SP1 DC3 is MS Server 2003 R2 Standard Edition SP2 I did not setup this domain originally but I am now the administrator of it, so I don't have a lot of background on why certain things may have been done in the past. My main goal is to try and fix these issues to get myself better prepared to decommisio
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and http://serverfault.com/questions/417159/new-domain-controller-is-having-trouble-replicating-from-an-existing-dc-13508-e policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges http://www.eventid.net/display-eventid-13508-source-NtFrs-eventno-349-phase-1.htm Unanswered Ask Question _ 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 it works: Anybody event id 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 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 event id 13508 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 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-r
Add-on 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. TheEventId.Net for Splunk Add-onassumes thatSplunkis collecting information from Windows servers and workstation via the Splunk Universal Forwarder. read more... Event ID: 13508 Source: NtFrs Source: NtFrs Type: Warning Description:The File Replication Service is having trouble enabling replication from