Ask a question


How can we help you today?

Ask Question
Manage notifications
Subscribe to this question
Clive Flint

FRS has been migrated to DFSr but logs show journal wrap error a year ago

Hi,

I have an SBS2011 server and one of the checks was for FRS errors.

I got this reported

Category: Configuration

Source: 229

Issue: The server is in a journal wrap condition.

Impact: In a journal wrap condition, the system volume is not shared. As a result, the domain controller cannot replicate with other domain controllers. Additionally, the server cannot authenticate network users until the journal wrap condition is resolved.

 

The FRS was migrated last year to DFS so FRS isn't running and refuses to run (DFS is the one it's using) but this error still shows.

Is it something that's going to cause an issue during the migration, and if so, how do I deal with it seeing as FRS won't run, so setting it to be authoritative  (B4 iirc) doesn't appear to help as it's not using FRS anymore.

DFS says it's fine and happy with no errors reported and the migration to DFS went without any issues.

Cheers

 

asked05/21/2020 15:07
183 views
Add Comment
Last Activity 05/21/2020 15:17

1 Answer(s)

  • Mariette Knap

    Hello Clive,

    Yes, even if you have Journal Wrap issues with FRS and you migrate FRS to DFS it can go without issues but later in the migration of your Active Directory we could run into other problems.

    If you check the logs and you do not find DFS related issues and you check if Sysvol and Netlogon are shared you should be able to continue. If later, during the migration you encounter issues with Sysvol and Netlogon not being shared on the new DC or you see DFS replication issues we can always fix those issues when they occur.

    You can continue for now.

    answered 05/21/2020 15:17
    Add Comment
Add an Answer