FRS event id 13565 - Sysvol not shared
Stephen3rd
I now have event id 13565 within the FRS log and it reads:
Log Name: File Replication Service
Source: NtFrs
Date: 30/03/2009 11:28:07
Event ID: 13565
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: server.domain.com
Description:
File Replication Service is initializing the system volume with data from
another domain controller. Computer server 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 initialization 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, the availability of
other domain controllers, and the replication interval between domain
controllers.
Anybody have any thoughts in how to speed the process along?
--
Many Thanks
Meinolf Weber [MVP-DS]
On the 2008 Dc's check that the "File replication" service is started and
set to automatic. Then run dcdiag and if it states an error about missing
object relating to article Q312862 follow the article to add the missing
value.
http://support.microsoft.com/kb/312862
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
Stephen3rd
DCdiag does come up with a missing object reference but is for a dc that was
removed almost 2 years ago. We have no need to add any reference to this
server as it has been out of our environment for a long time.
Or will i be forced to sort this issue out to enable the FRS service to
share out the Sysvol foder?
--
Many Thanks
Meinolf Weber [MVP-DS]
File replication service has to run for sysvol sharing.
If you have references to removed DC's run metabase cleanup according to
this article:
http://support.microsoft.com/kb/216498
Also make sure that the removed server is not existing in AD sites and services
under the servers list. Will not be removed there during demoting of a server,
you have to do it manual.
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
> Thanks Meinolf for the reply.
>
> DCdiag does come up with a missing object reference but is for a dc
> that was removed almost 2 years ago. We have no need to add any
> reference to this server as it has been out of our environment for a
> long time.
>
> Or will i be forced to sort this issue out to enable the FRS service
> to share out the Sysvol foder?
>
Florian Frommherz [MVP]
"Stephen3rd" wrote:
> DCdiag does come up with a missing object reference but is for a dc that
> was
> removed almost 2 years ago. We have no need to add any reference to this
> server as it has been out of our environment for a long time.
What does frsdiag come up with?
> Or will i be forced to sort this issue out to enable the FRS service to
> share out the Sysvol foder?
Is there anything else in the event viewer?
Check http://support.microsoft.com/default.aspx?scid=kb;en-us;257338 and
http://support.microsoft.com/default.aspx?scid=kb;en-us;315457
Cheers,
Florian
--
Microsoft MVP - Group Policy
eMail: prename [at] frickelsoft [dot] net.
blog: http://www.frickelsoft.net/blog.
Maillist (german): http://frickelsoft.net/cms/index.php?page=mailingliste