Trying to migrate 2003 server std to 2012 r2 std
can transfer roles between servers
keep getting Error 1355 "a global catalog server cannot be located" SYSVOL not working on new server
Moved roles back to 2003 server
getting same error message on old server
2003 server was not the PDC of the domain I had to seize the roles from a non-existent server. After transferring roles I was able to perform a metadata clean up and remove the non-existent server. This all worked without errors.
Just getting errors trying to go the 2012
Any help or suggestions would be great.
Thanks Dave
Can you check NTfrs logs on all domain controllers?
2003 server is getting journal wrap errors
Event Type: Error Event Source: NtFrs Event Category: None Event ID: 13568 Date: 3/3/2020 Time: 12:06:36 AM User: N/A Computer: SERVER01 Description: The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR. Replica set name is : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" Replica root path is : "c:\windows\sysvol\domain" Replica root volume is : "\\.\C:" A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found. This can occur because of one of the following reasons. [1] Volume "\\.\C:" has been formatted. [2] The NTFS USN journal on volume "\\.\C:" has been deleted. [3] The NTFS USN journal on volume "\\.\C:" has been truncated. Chkdsk can truncate the journal if it finds corrupt entries at the end of the journal. [4] File Replication Service was not running on this computer for a long time. [5] File Replication Service could not keep up with the rate of Disk IO activity on "\\.\C:". Setting the "Enable Journal Wrap Automatic Restore" registry parameter to 1 will cause the following recovery steps to be taken to automatically recover from this error state. [1] At the first poll, which will occur in 5 minutes, this computer will be deleted from the replica set. If you do not want to wait 5 minutes, then run "net stop ntfrs" followed by "net start ntfrs" to restart the File Replication Service. [2] At the poll following the deletion this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set. WARNING: During the recovery process data in the replica tree may be unavailable. You should reset the registry parameter described above to 0 to prevent automatic recovery from making the data unexpectedly unavailable if this error condition occurs again. To change this registry parameter, run regedit. Click on Start, Run and type regedit. Expand HKEY_LOCAL_MACHINE. Click down the key path: "System\CurrentControlSet\Services\NtFrs\Parameters" Double click on the value name "Enable Journal Wrap Automatic Restore" and update the value. If the value name is not present you may add it with the New->DWORD Value function under the Edit Menu item. Type the value name exactly as shown above.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
2012 server is getting File replication warnings
Log Name: File Replication Service Source: NtFrs Date: 3/2/2020 10:00:17 PM Event ID: 13508 Task Category: None Level: Warning Keywords: Classic User: N/A Computer: FSEV-DC2.internal.foodstuffs.com Description: The File Replication Service is having trouble enabling replication from SERVER01 to FSEV-DC2 for c:\windows\sysvol\domain using the DNS name server01.internal.foodstuffs.com. FRS will keep retrying. Following are some of the reasons you would see this warning. [1] FRS can not correctly resolve the DNS name server01.internal.foodstuffs.com from this computer. [2] FRS is not running on server01.internal.foodstuffs.com. [3] The topology information in the Active Directory Domain Services 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. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="NtFrs" /> <EventID Qualifiers="32768">13508</EventID> <Level>3</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2020-03-03T04:00:17.000000000Z" /> <EventRecordID>21</EventRecordID> <Channel>File Replication Service</Channel> <Computer>FSEV-DC2.internal.foodstuffs.com</Computer> <Security /> </System> <EventData> <Data>SERVER01</Data> <Data>FSEV-DC2</Data> <Data>c:\windows\sysvol\domain</Data> <Data>server01.internal.foodstuffs.com</Data> <Binary>D9060000</Binary> </EventData> </Event>
Here is the answer Using the BurFlags registry key to reinitialize File Replication Service. If you don't want to do it yourself open a ticket.
Do I do an authoritative restore? Do I run this on the 2003 server or the 2012 server? If I wanted to open a ticket what should I do?
Thanks
Dave
An authoritative restore is mostly done on the PDC, the DC that owns the FSMO roles. If you want to open a ticket go here Premier Support. Choose 2 time slots as that will be enough for this job and if we have time left you can use that for something else. I am not available tomorrow early but after 2 PM CET should be OK
I am available at 2PM CET. I do have a meeting from 4PM CET to 5PM CET. Let me know if you think 2 hours is enough time.
Thanks. I will update our project sheet and send you a link as well as a Microsoft Teams invite for tomorrow.
Your browser doesn't have Flash, Silverlight or HTML5 support.