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 & 13555. SYSVOL not the file replication service is in an error state replicating. Windows Server > Directory Services Question 0 Sign in to
Event 13555
vote Hi All, looking for a little help here... Here is the scenario. My (new) client has frs error status code is frserrormismatchedjournalid ONLY1 domain controller(Windows Server 2003 which I will call SERVER1). I recently installed a new 2008 R2 serverand made it a replica domain controller. Everything went well until
Frserrormismatchedjournalid 2012
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 restore from a replica DC however in this case there is only 1 frs error status code is frserrormismatchedjournalid server 2012 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 ------------------------------------------------------------------------------ Event Type:Error Event Source:NtFrs Event Category:None Event ID:13555 Date:21/06/2011 Time:2:15:57 PM User:N/A Computer:SERVER1 Description: The File Replication Service is in an error state. Files will
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, 2013 1 Comment I discovered an issue
Burflag
at a client site the other day where event IDs 13555 and
Frs Error Status Code Is Frserrormismatchedjournalid 2012
13552 with a source of NtFrs were present in the event log of a Windows Server 2003 Domain Controller. The event id 13555 relevant error messages were as follows: ‘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 https://social.technet.microsoft.com/Forums/office/en-US/81f51ad2-875e-408f-8269-85269b337032/frs-errors-13552-13555-sysvol-not-replicating?forum=winserverDS 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 the SYSVOL share was in an inconsistent state. This error had obviously first occurred some time before and as a result https://oasysadmin.com/2013/04/30/ntfrs-event-id-13555-and-13552-the-file-replication-service-is-in-an-error-state/ 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 Burflags to D2 on the remaining Domain Controllers and start NtFrs Exercise extreme caution if using the advice above. It is not a substitute for restoring from a good system state backup if you have one, and more of a last resort. In
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 https://www.experts-exchange.com/questions/26629478/No-Backup-ntfrs-failure-How-to-fix-13552-13555.html Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > No Backup. ntfrs failure. How to fix 13552/13555? Want to Advertise Here? Solved No Backup. ntfrs failure. How to fix 13552/13555? Posted on 2010-11-20 Storage Software Windows Server 2003 Active Directory 2 Verified Solutions 3 Comments 1,642 Views Last Modified: 2012-05-10 I have 2 dcs both running w2k3, one of them started to show these event ids: Event Type: Error Event Source: frs error NtFrs Event Category: None Event ID: 13552 Date: 11/21/2010 Time: 7:38:19 AM User: N/A Computer: * 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 frs error status support NTFS 5.0 The information below may help to resolve the problem: Computer DNS name is "*" Replica set member name is "*" 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 Other event log messages may also help determine the problem. Correct the problem and the service will attempt to restart replication automatically at a later time. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Event Type: Error Event Source: NtFrs Event Category: None Event ID: 13555 Date: 11/21/2010 Time: 7:38:19 AM User: N/A Computer: * Description: 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 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 r