Reset Password · PC & Mac Help and Assistance

Welcome Guest! To enable all features please Login or Register

Posted by: drdread - 29 January 2025 14:19:11
As far as I can tell all of the folders are intact but I cannot progress to DFRS without getting this error resolved: Log Name: File Replication Service Source: NtFrs Date: 29/01/2025 14:15:30 Event ID: 13552 Task Category: None Level: Error Keywords: Classic User: N/A Computer: ARGDC1.argofield.local 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 "DC1.domain.local" Replica set member name is "DC1" Replica set root path is "f:\windows\sysvol\domain" Replica staging directory path is "f:\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. Event Xml: [code=markup]<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="NtFrs" /> <EventID Qualifiers="49152">13552</EventID> <Level>2</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2025-01-29T14:15:30.000000000Z" /> <EventRecordID>1786</EventRecordID> <Channel>File Replication Service</Channel> <Computer>DC1.domain.local</Computer> <Security /> </System> <EventData> <Data>DOMAIN SYSTEM VOLUME (SYSVOL SHARE)</Data> <Data>DC1.domain.local</Data> <Data>DC1</Data> <Data>f:\windows\sysvol\domain</Data> <Data>f:\windows\sysvol\staging\domain</Data> <Data>c:\windows\ntfrs\jet</Data> <Data> </Data> <Data>FrsErrorMismatchedJournalId</Data> </EventData> </Event>[/code]

Posted by: drdread - 29 January 2025 14:19:11

As far as I can tell all of the folders are intact but I cannot progress to DFRS without getting this error resolved: Log Name: File Replication Service Source: NtFrs Date: 29/01/2025 14:15:30 Event ID: 13552 Task Category: None Level: Error Keywords: Classic User: N/A Computer: ARGDC1.argofield.local 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 "DC1.domain.local" Replica set member name is "DC1" Replica set root path is "f:\windows\sysvol\domain" Replica staging directory path is "f:\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. Event Xml: [code=markup]<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="NtFrs" /> <EventID Qualifiers="49152">13552</EventID> <Level>2</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2025-01-29T14:15:30.000000000Z" /> <EventRecordID>1786</EventRecordID> <Channel>File Replication Service</Channel> <Computer>DC1.domain.local</Computer> <Security /> </System> <EventData> <Data>DOMAIN SYSTEM VOLUME (SYSVOL SHARE)</Data> <Data>DC1.domain.local</Data> <Data>DC1</Data> <Data>f:\windows\sysvol\domain</Data> <Data>f:\windows\sysvol\staging\domain</Data> <Data>c:\windows\ntfrs\jet</Data> <Data> </Data> <Data>FrsErrorMismatchedJournalId</Data> </EventData> </Event>[/code]

Posted by: drdread - 29 January 2025 14:59:36
My mistake I promoted the new DC before completing the DFRS migration and although 2016 supposedly supported FRS I think this DC was too new with updates and would not replicate so I demoted it and progressed through the migration with only the old, single DC

Important Information: