File Replication Service Error 13555
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) Home20132010Other VersionsLibraryForumsGallery Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: FRS errors 13552 frs error status code is frserrormismatchedjournalid & 13555. SYSVOL not replicating. Windows Server > Directory Services
Frs Error Status Code Is Frserrormismatchedjournalid 2012
Question 0 Sign in to vote Hi All, looking for a little help here... Here is
The File Replication Service Is In An Error State.
the scenario. My (new) client has ONLY1 domain controller(Windows Server 2003 which I will call SERVER1). I recently installed a new 2008 R2 serverand made it
Burflag
a replica domain controller. Everything went well until I realised that there was no SYSVOL share on the new server. I checked FRS event logs on SERVER1 and noticed that event ID errors 13552 & 13555 have been occuring since December 2010. I've been reading about changing burflags to do a nonauthorative frs error status code is frserrormismatchedjournalid server 2012 restore from a replica DC however in this case there is only 1 DC. Can someone advise how I go about fixing this? ------------------------------------------------------------------------------ Event Type:Error Event Source:NtFrs Event Category:None Event ID:13552 Date:21/06/2011 Time:2:15:57 PM User:N/A Computer:SERVER1 Description: The File Replication Service is unable to add this computer to the following replica set: "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" This could be caused by a number of problems such as: -- an invalid root path, -- a missing directory, -- a missing disk volume, -- a file system on the volume that does not support NTFS 5.0 The information below may help to resolve the problem: Computer DNS name is "server1.mydomain.local" Replica set member name is "SERVER1" Replica set root path is "c:\windows\sysvol\domain" Replica staging directory path is "c:\windows\sysvol\staging\domain" Replica working directory path is "c:\windows\ntfrs\jet" Windows error status code is FRS error status code is FrsErrorMismatchedJournalId -------------------------------
PPTP client through Cisco ASA 8.4 to external PPTPserver → NtFrs Event ID 13555 and 13552 The file replication Service is in an errorstate April 30, event id 13555 2013 1 Comment I discovered an issue at a client site ntfrs 13552 the other day where event IDs 13555 and 13552 with a source of NtFrs were present in burflags d2 vs d4 the event log of a Windows Server 2003 Domain Controller. The relevant error messages were as follows: ‘The File Replication Service is in an error state. Files will https://social.technet.microsoft.com/Forums/office/en-US/81f51ad2-875e-408f-8269-85269b337032/frs-errors-13552-13555-sysvol-not-replicating?forum=winserverDS not replicate to or from one or all of the replica sets on this computer until the following recovery steps are performed' The File Replication Service is unable to add this computer to the following replica set: "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" In this case the network had a single DC. It appeared from the errors that https://oasysadmin.com/2013/04/30/ntfrs-event-id-13555-and-13552-the-file-replication-service-is-in-an-error-state/ the SYSVOL share was in an inconsistent state. This error had obviously first occurred some time before and as a result there were no system state backups from when the SYSVOL share was in a consistent state. To fix the error I had to set the Burflags option to D4 under the following registry key to force the DC into thinking an authoritative restore had been performed: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Cumulative Replica Sets\GUID_OF_YOUR_REPLICA_SET\Burflags After Setting this, and restarting the server the errors disappeared. In a multi Domain Controller network much more care needs to be taken. On the plus side in this case you will normally have a good copy of SYSVOL on a different DC. Detailed information on how to recover from this error in a multi Domain Controller network can be found in the references below but the basic premise is this: Stop NtFrs on all servers Set Burflags to D4 in the registry of a Domain Controller with a known good copy of SYSVOL and start NtFrs Set Burf
(Microsoft) Technical Consultant/SI GROUP SPONSORED BY MICROSOFT See more RELATED PROJECTS Managing Vendor Performance The main objective of the project is to manage vendor performance and streamline the parts’ ordering process for equipment maintenance and parts' personnel. Datacenter Rebuild Complete redesign https://community.spiceworks.com/topic/555565-ntfrs-issues of the datacenter, network infrastructure, wireless implementation, and controls SpiceCorps of Southeast UK @ Microsoft With Windows 10 in public beta, and Azure being a Mystery to a lot of IT pros, Microsoft volunteered their facilities, and team to talk tech with the SpiceCorps of Southeast UK. TECHNOLOGY IN THIS DISCUSSION Data Domain Join the Community! Creating your account only takes a few minutes. Join Now Hello All, I have 2 DC's PDC emulator COEDC01 and BDC emulator LUNASRV. COEDC01 frs error is receiving event ID' 13552 and 13555. LUNASRV is receiving event ID 13508. Just to confirm, the way to fix this is to go in to reg of COEDC01 and set the key to D4. Any help would be great. Reply Subscribe View Best Answer RELATED TOPICS: event id 13568 source ntfrs   5 Replies Ghost Chili OP Kelly Armitage Aug 6, 2014 at 9:16 UTC I don't think there is enough info to say for certain.... frs error status when I Google that event ID I get this as a solution: http://support.microsoft.com/kb/819268 Any event ID can have multiple meanings... cut and paste the entire event and provide some OS info.. (blank out company specific info) 0 Poblano OP BZBOARDING101 Aug 6, 2014 at 9:20 UTC Event ID 1355: The File Replication Service is in an error state. Files will not replicate to or from one or all of the replica sets on this computer until the following recovery steps are performed: Recovery Steps: [1] The error state may clear itself if you stop and restart the FRS service. This can be done by performing the following in a command window: net stop ntfrs net start ntfrs If this fails to clear up the problem then proceed as follows. [2] For Active Directory Domain Services Domain Controllers that DO NOT host any DFS alternates or other replica sets with replication enabled: If there is at least one other Domain Controller in this domain then restore the "system state" of this DC from backup (using ntbackup or other backup-restore utility) and make it non-authoritative. If there are NO other Domain Controllers in this domain then restore the "system state" of this DC from backup (using ntbackup or other backup-restore utility) and choose the Advanced option which marks the sysvols as primary. If there are other Domain Controllers in this domain but ALL of them have this event l