Re: NTFRS taking Way too long to share sysvol

From: ptwilliams (ptw2001_at_hotmail.com)
Date: 07/14/04 

Date: Wed, 14 Jul 2004 20:35:26 +0100

SP3 made it 128MB.
SP4 made it 512MB...

Also, older antivirus or poor network conditions can cause this; not just
Frs being stopped. 

-- 
Paul Williams
_________________________________________
 http://www.msresource.net
Join us in our new forums!
  http://forums.msresource.net
_________________________________________
"Jim Singh" <jsingh07@hotmail.com> wrote in message
news:%231PD2kdaEHA.3716@TK2MSFTNGP11.phx.gbl...
Journal is a log file that keeps track of the changes made to the ntfs5.0
volumes and this log file is of fixed size by default but can be increased
to 128mb by configuring the following registry key:
HKLM\System\Ccs\Services\Ntfrs\Parameters\ntfs journal size
It depends how big is the volume that its trying to update. You should not
stop the FRS service for longer period of time as it can cause in the
journal wrap errors. I dont think there is a way to kick start it but you
can check it at MS site.
-Jim
"Jake" <anonymous@discussions.microsoft.com> wrote in message
news:2ce3901c469d2$c2ca1a10$a401280a@phx.gbl...
>I got this warning message this morning after my DC got a
> JRNL_WRAP_ERROR in the ntfrs.  I followed the recovery
> procedures listed in the event (changed the DWORD value
> in "Enable Journal Wrap Automatic Restore" parameter to 1
> and restarted NTFRS.
> My question is how much longer do I have to wait for the
> sysvol to become "shared".  Is there anything I can do to
> kick start this?
>
> Event Type: Warning
> Event Source: NtFrs
> Event Category: None
> Event ID: 13566
> Date: 7/14/2004
> Time: 10:47:51 AM
> User: N/A
> Computer: OZ
> Description:
> File Replication Service is scanning the data in the
> system volume. Computer OZ cannot become a domain
> controller until this process is complete. The system
> volume will then be shared as SYSVOL.
>
> To check for the SYSVOL share, at the command prompt,
> type:
> net share
>
> When File Replication Service completes the scanning
> process, the SYSVOL share will appear.
>
> The initialization of the system volume can take some
> time. The time is dependent on the amount of data in the
> system volume.
>

Relevant Pages

  • Re: FRS Journal wrap condition...
    ... as I once had fits trying to get sysvol back. ... I'm back to mentioning the use of the Burflags key to fix Journal Wrap Errors instead of "Enable Journal Wrap Automatic Restore". ... The File Replication Service has detected that the replica set "DOMAIN ... Replica set name is: ...
    (microsoft.public.windows.server.sbs)
  • Re: Unable to decommission a Windows 2008 DC via dcpromo
    ... server, so I manually created them, but apparently they didn't ... Can you open and compare sysvol and netlogon share on both DCs? ... The File Replication Service is having trouble enabling ... FRS can not correctly resolve the DNS name ...
    (microsoft.public.windows.server.active_directory)
  • Re: dcdiag er
    ... If the FRS already started and you have FRS related errors then something is ... The File Replication Service Event log test ... No record of File Replication System, SYSVOL started. ...
    (microsoft.public.win2000.active_directory)
  • Re: dcdiag er
    ... is booting the frs isn't started so shows up the 1st message, ... The File Replication Service Event log test ... No record of File Replication System, SYSVOL started. ...
    (microsoft.public.win2000.active_directory)
  • Re: FRS Journal wrap condition...
    ... I've lost my SYSVOL and can't get up ... I'm back to mentioning the use of the Burflags key to fix Journal Wrap ... The File Replication Service has detected that the replica set "DOMAIN ... Replica set name is: ...
    (microsoft.public.windows.server.sbs)
Loading