ultrasound FRS monitoring question

  • Thread starter Thread starter Andrew Story
  • Start date Start date
A

Andrew Story

Hi - long shot but if anyone has used ultrasound before...

I have just installed MS Ultrasound on a DC in my org's HUB site to
centrally monitor FRS.

I have one issue is that it won't deploy to one server on a remote site, the
error in Ultrasound console is:

Failed Ultrasound server updates - FRS Replica set in state journal wrap
ErrorID:24

If anyone has used Ultrasound before and knows what causes this, much
appreciated if you could post here.

TIA.
 
Andrew Story said:
Hi - long shot but if anyone has used ultrasound before...

I have just installed MS Ultrasound on a DC in my org's HUB site to
centrally monitor FRS.

I have one issue is that it won't deploy to one server on a remote site,
the error in Ultrasound console is:

Failed Ultrasound server updates - FRS Replica set in state journal wrap
ErrorID:24

If anyone has used Ultrasound before and knows what causes this, much
appreciated if you could post here.
Click to expand...
Yes I have seen the error.

You need to go into the event viewer of the domain controller in question
and go through the File Replication Service event log; this will have red
events regarding the journal wrap condition. The event text will tell you to
steps to take to recover from the journal wrap condition.

From memory you need to create a registry key (if it doesn't already exist)
and set its value to 1, then stop and start the FRS service. This will
initiate recovery from the Journal Wrap condition. I believe (from memory)
that the registry key is EnableJournalWrapAutomaticRestore.

Sorry for the general nature of my reply but I'm not at work at the moment
and I'm working from memory :) As I said the event text in the File
Replication Service log will explain all.

BTW a useful newsgroup for indepth Ultrasound and FRS issues is
microsoft.public.windows.server.dfs_frs

Hth
 
Thank you very much Peter, much appreciated.


Trust No One® said:
Yes I have seen the error.

You need to go into the event viewer of the domain controller in question
and go through the File Replication Service event log; this will have red
events regarding the journal wrap condition. The event text will tell you
to steps to take to recover from the journal wrap condition.

From memory you need to create a registry key (if it doesn't already
exist) and set its value to 1, then stop and start the FRS service. This
will initiate recovery from the Journal Wrap condition. I believe (from
memory) that the registry key is EnableJournalWrapAutomaticRestore.

Sorry for the general nature of my reply but I'm not at work at the moment
and I'm working from memory :) As I said the event text in the File
Replication Service log will explain all.

BTW a useful newsgroup for indepth Ultrasound and FRS issues is
microsoft.public.windows.server.dfs_frs

Hth
Click to expand...
 
Back
Top