File Replication errors n Event log on Server

[Phil Walker]

I have been told by Microsoft to re-send this e-mail with the correct email
address as we have Technet Plus and a Microsoft engineer will reply with
help...........


I was checking the event logs in File replication and I have this error. I
have a C, F, H and X: Drives and this system and not sure why is mentions
d:\....?

Event ID 13539

The File Replication Service cannot replicate d:\ad\sysvol\domain because
the pathname of the replicated directory is not the fully qualified pathname
of an existing, accessible local directory.

and

Event ID 13552

he File Replication Service is unable to add this computer to the following
replica set:
"DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"

This could be caused by a number of problems such as:
-- an invalid root path,
-- a missing directory,
-- a missing disk volume,
-- a file system on the volume that does not support NTFS 5.0

The information below may help to resolve the problem:
Computer DNS name is "hddesign3.hd-design.local"
Replica set member name is "HDDESIGN3"
Replica set root path is "d:\ad\sysvol\domain"
Replica staging directory path is "d:\ad\sysvol\staging\domain"
Replica working directory path is "c:\windows\ntfrs\jet"
Windows error status code is
FRS error status code is FrsErrorStageDirOpenFail

Then when I check registry entries have noticed in the following registry
entries under

HKLM\system\CurrentControlSet\Services\Ntfrs\Parameters\Replica Sets\

2 folders

c4276d80-7893-4142-b8622fe475746e83
inside this folder:
(Default) REG_SZ (value not set)
Relica Set name REG_SZ DOMAIN SYSTEM VOLUME (SYSVOL
SHARE)
Replica Set Root REG_SZ d:\ad\sysvol\domain
Replica Set Stage REG_SZ d:\ad\sysvol\staging\domain
Replica Set Tombstoned REG_DWORD 0x0000000 (0)
Replica Set Type REG_SZ Domain

f8a48965-5f20-42dd-afa32b998fc2d3fd
inside this folder:
(Default) REG_SZ (value not set)
Relica Set name REG_SZ DOMAIN SYSTEM VOLUME (SYSVOL
SHARE)
Replica Set Root REG_SZ dc:\windows\sysvol\domain
Replica Set Stage REG_SZ c:\windows\sysvol\staging\domain
Replica Set Tombstoned REG_DWORD 0x0000000 (0)
Replica Set Type REG_SZ Domain


Can I just delete the 1st folder registry entry that mentions d:\ad? as this
does not
exist..............

 

[Meinolf Weber]

Re: File Replication errors n Event log on Server

Hello Phil,

Think you posted this uner "ZaZ" on 15.07.2008 16:51 under Subject "NTBackup
fails backing up System State"

This is a newsgroup which is NOT monitored from MS. Think you misunderstand
the MS people or they told you wrong, which i think is not. If you have a
Technet plus contact the TechNet plus contact number on your contract and
they are aible to help you with your problem.

Again, this is NOT MS support. This newsgroups are public and sometimes also
people form MS will help but they do it in there free time.


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

> I have been told by Microsoft to re-send this e-mail with the correct
> email address as we have Technet Plus and a Microsoft engineer will
> reply with help...........
>
> I was checking the event logs in File replication and I have this
> error. I have a C, F, H and X: Drives and this system and not sure why
> is mentions d:\....?
>
> Event ID 13539
>
> The File Replication Service cannot replicate d:\ad\sysvol\domain
> because the pathname of the replicated directory is not the fully
> qualified pathname of an existing, accessible local directory.
>
> and
>
> Event ID 13552
>
> he File Replication Service is unable to add this computer to the
> following
> replica set:
> "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
> This could be caused by a number of problems such as:
> -- an invalid root path,
> -- a missing directory,
> -- a missing disk volume,
> -- a file system on the volume that does not support NTFS 5.0
> The information below may help to resolve the problem:
> Computer DNS name is "hddesign3.hd-design.local"
> Replica set member name is "HDDESIGN3"
> Replica set root path is "d:\ad\sysvol\domain"
> Replica staging directory path is "d:\ad\sysvol\staging\domain"
> Replica working directory path is "c:\windows\ntfrs\jet"
> Windows error status code is
> FRS error status code is FrsErrorStageDirOpenFail
> Then when I check registry entries have noticed in the following
> registry entries under
>
> HKLM\system\CurrentControlSet\Services\Ntfrs\Parameters\Replica Sets\
>
> 2 folders
>
> c4276d80-7893-4142-b8622fe475746e83
> inside this folder:
> (Default) REG_SZ (value not set)
> Relica Set name REG_SZ DOMAIN SYSTEM VOLUME
> (SYSVOL
> SHARE)
> Replica Set Root REG_SZ d:\ad\sysvol\domain
> Replica Set Stage REG_SZ d:\ad\sysvol\staging\domain
> Replica Set Tombstoned REG_DWORD 0x0000000 (0)
> Replica Set Type REG_SZ Domain
> f8a48965-5f20-42dd-afa32b998fc2d3fd
> inside this folder:
> (Default) REG_SZ (value not set)
> Relica Set name REG_SZ DOMAIN SYSTEM VOLUME
> (SYSVOL
> SHARE)
> Replica Set Root REG_SZ
> dc:\windows\sysvol\domain
> Replica Set Stage REG_SZ
> c:\windows\sysvol\staging\domain
> Replica Set Tombstoned REG_DWORD 0x0000000 (0)
> Replica Set Type REG_SZ Domain
> Can I just delete the 1st folder registry entry that mentions d:\ad?
> as this
> does not
> exist..............

 

[Edwin vMierlo [MVP]]

Re: File Replication errors n Event log on Server

hi Phil,

these newsgroups are public and not from "Microsoft Technet" or any
Microsoft Support organisation.

Anyone here is answering posts on a voluntary basis. You might find people
from Microsoft here, but they do this on their own account and free time,
not official support from Microsoft.

Please see your Technet subscription details on how to obtain official
support

Rgds,
Edwin.


"Phil Walker" <bramblewood@noemail.noemail> wrote in message
news:OMV$gyx6IHA.3652@TK2MSFTNGP04.phx.gbl...
> I have been told by Microsoft to re-send this e-mail with the correct
email
> address as we have Technet Plus and a Microsoft engineer will reply with
> help...........
>
>
> I was checking the event logs in File replication and I have this error. I
> have a C, F, H and X: Drives and this system and not sure why is mentions
> d:\....?
>
> Event ID 13539
>
> The File Replication Service cannot replicate d:\ad\sysvol\domain because
> the pathname of the replicated directory is not the fully qualified
pathname
> of an existing, accessible local directory.
>
> and
>
> Event ID 13552
>
> he File Replication Service is unable to add this computer to the
following
> replica set:
> "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
>
> This could be caused by a number of problems such as:
> -- an invalid root path,
> -- a missing directory,
> -- a missing disk volume,
> -- a file system on the volume that does not support NTFS 5.0
>
> The information below may help to resolve the problem:
> Computer DNS name is "hddesign3.hd-design.local"
> Replica set member name is "HDDESIGN3"
> Replica set root path is "d:\ad\sysvol\domain"
> Replica staging directory path is "d:\ad\sysvol\staging\domain"
> Replica working directory path is "c:\windows\ntfrs\jet"
> Windows error status code is
> FRS error status code is FrsErrorStageDirOpenFail
>
> Then when I check registry entries have noticed in the following registry
> entries under
>
> HKLM\system\CurrentControlSet\Services\Ntfrs\Parameters\Replica Sets\
>
> 2 folders
>
> c4276d80-7893-4142-b8622fe475746e83
> inside this folder:
> (Default) REG_SZ (value not set)
> Relica Set name REG_SZ DOMAIN SYSTEM VOLUME (SYSVOL
> SHARE)
> Replica Set Root REG_SZ d:\ad\sysvol\domain
> Replica Set Stage REG_SZ d:\ad\sysvol\staging\domain
> Replica Set Tombstoned REG_DWORD 0x0000000 (0)
> Replica Set Type REG_SZ Domain
>
> f8a48965-5f20-42dd-afa32b998fc2d3fd
> inside this folder:
> (Default) REG_SZ (value not set)
> Relica Set name REG_SZ DOMAIN SYSTEM VOLUME (SYSVOL
> SHARE)
> Replica Set Root REG_SZ dc:\windows\sysvol\domain
> Replica Set Stage REG_SZ
c:\windows\sysvol\staging\domain
> Replica Set Tombstoned REG_DWORD 0x0000000 (0)
> Replica Set Type REG_SZ Domain
>
>
> Can I just delete the 1st folder registry entry that mentions d:\ad? as
this
> does not
> exist..............
>

 

[Andrew]

Re: File Replication errors n Event log on Server

Edwin,

Microsoft actually provide a guaranteed 1 business day response to certain
"managed newsgroups" under the Technet Plus program and this is one of them
.. So in fact Microsoft should respond to this request for help - and within
1 business day.

Part of the text of thier Technet Subscription Benefits reads ...
Managed Newsgroup Support. TechNet Plus provides unlimited access to over
100 Managed Newsgroups. Exchange ideas with other IT Professionals and get
expert answers to your technical questions within the next business
day-guaranteed.

Hope this help explain why Philip is trying to get MS attention - I see he
has a Technet Plus Subscription.

A.

"Edwin vMierlo [MVP]" <EdwinvMierlo@discussions.microsoft.com> wrote in
message news:eFMLafy6IHA.3816@TK2MSFTNGP03.phx.gbl...
> hi Phil,
>
> these newsgroups are public and not from "Microsoft Technet" or any
> Microsoft Support organisation.
>
> Anyone here is answering posts on a voluntary basis. You might find people
> from Microsoft here, but they do this on their own account and free time,
> not official support from Microsoft.
>
> Please see your Technet subscription details on how to obtain official
> support
>
> Rgds,
> Edwin.
>
>
> "Phil Walker" <bramblewood@noemail.noemail> wrote in message
> news:OMV$gyx6IHA.3652@TK2MSFTNGP04.phx.gbl...
>> I have been told by Microsoft to re-send this e-mail with the correct
> email
>> address as we have Technet Plus and a Microsoft engineer will reply with
>> help...........
>>
>>
>> I was checking the event logs in File replication and I have this error.
>> I
>> have a C, F, H and X: Drives and this system and not sure why is mentions
>> d:\....?
>>
>> Event ID 13539
>>
>> The File Replication Service cannot replicate d:\ad\sysvol\domain because
>> the pathname of the replicated directory is not the fully qualified
> pathname
>> of an existing, accessible local directory.
>>
>> and
>>
>> Event ID 13552
>>
>> he File Replication Service is unable to add this computer to the
> following
>> replica set:
>> "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
>>
>> This could be caused by a number of problems such as:
>> -- an invalid root path,
>> -- a missing directory,
>> -- a missing disk volume,
>> -- a file system on the volume that does not support NTFS 5.0
>>
>> The information below may help to resolve the problem:
>> Computer DNS name is "hddesign3.hd-design.local"
>> Replica set member name is "HDDESIGN3"
>> Replica set root path is "d:\ad\sysvol\domain"
>> Replica staging directory path is "d:\ad\sysvol\staging\domain"
>> Replica working directory path is "c:\windows\ntfrs\jet"
>> Windows error status code is
>> FRS error status code is FrsErrorStageDirOpenFail
>>
>> Then when I check registry entries have noticed in the following registry
>> entries under
>>
>> HKLM\system\CurrentControlSet\Services\Ntfrs\Parameters\Replica Sets\
>>
>> 2 folders
>>
>> c4276d80-7893-4142-b8622fe475746e83
>> inside this folder:
>> (Default) REG_SZ (value not set)
>> Relica Set name REG_SZ DOMAIN SYSTEM VOLUME
>> (SYSVOL
>> SHARE)
>> Replica Set Root REG_SZ d:\ad\sysvol\domain
>> Replica Set Stage REG_SZ d:\ad\sysvol\staging\domain
>> Replica Set Tombstoned REG_DWORD 0x0000000 (0)
>> Replica Set Type REG_SZ Domain
>>
>> f8a48965-5f20-42dd-afa32b998fc2d3fd
>> inside this folder:
>> (Default) REG_SZ (value not set)
>> Relica Set name REG_SZ DOMAIN SYSTEM VOLUME
>> (SYSVOL
>> SHARE)
>> Replica Set Root REG_SZ dc:\windows\sysvol\domain
>> Replica Set Stage REG_SZ
> c:\windows\sysvol\staging\domain
>> Replica Set Tombstoned REG_DWORD 0x0000000 (0)
>> Replica Set Type REG_SZ Domain
>>
>>
>> Can I just delete the 1st folder registry entry that mentions d:\ad? as
> this
>> does not
>> exist..............
>>
>
>

 

[Miles Li [MSFT]]

RE: File Replication errors n Event log on Server

Hello,

Thank you for your post.

Please allow me to confirm that my understandings are correct. As I
understand it, the issue is:

You receive the Event ID 13539 and 13552 that indicates the FRS cannot
replication the d:\ad\sysvol\ folder as the SYSVOL folder.

If I have misunderstood your concerns please feel free to let me know.

Suggestions:
==============

I'd like to ask some questions about the issue:

1. Where is the SYSVOL folder stored currently? Is it in the
c:\windows\sysvol? Does it keep consistent with other domain controller in
the domain?
2. Have you tried to relocate the SYSVOL folder to d:\ad\sysvol\? How do
you get the DOMAIN SYSTEM VOLUME replication set for d:\ad\sysvol\?

According to the symptom, it seems that the path to the FRS subscription is
set incorrectly. Please also check the following aspects to indentify the
effective SYSVOL folder:

1. Identify the fRSRootPath and fRSStagingPath in that domain controller
computer account.

a) Click Start, click Run, type adsiedit.msc, and then press Enter.
b) Expand the CN=NTFRS Subscriptions container, CN=computername,
OU=Domain Controllers, DC=domain, DC=local in the tree view.
c) In the details pane, right-click CN=Domain System Volume, and then
click Properties.
d) In Attributes, locate fRSRootPath and fRSStagingPath. Does it begin
with "D:\Windows\Sysvol"? If the path is set wrong, please edit the path to
point to the correct SYSVOL path. Generally speaking, SYSVOL folder is
stored in the c:\windows\sysvol folder.

2. Identify the SYSVOL parameter in the registry

a) In Registry Editor, navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters.
b) Sysvol appears in the details pane. Ensure the current value is
c:\windows\sysvol\sysvol
c) Navigate to the
[HKEY_LOCAL_MACHINE\System\CCS\Services\NTFRS\Parameters\Replica Sets]
registry key.
d) Locate the problematic replica set. All replica sets are displayed as
a GUID. If you click a GUID, one of the values on the right is Replica Set
Name and the value of "Replica Set Stage" stores the path to the staging
area. Is it correct? If not, please modify it to point to correct one.


As deleting the SYSVOL registry key and folder is dangerous, I'd like to
suggest that we temporarily hold this step before we are clearing about the
problem and the background.

For your reference:
==============
Relocating SYSVOL Manually
http://technet2.microsoft.com/windowsserver/en/library/300796c6-8148-49af-a3
27-b5dca853ac4f1033.mspx

Introduction to Administering SYSVOL
http://technet2.microsoft.com/windowsserver/en/library/551f0123-26a7-4ce5-be
71-173e7aa79bd31033.mspx

Best Practices for Sysvol Maintenance
http://support.microsoft.com/kb/324175



Please also collect DirSvc version of MPSReport which contains the FRS
objects. You can get this tool from the link:

Microsoft Product Support's Reporting Tools (MPSRPT_DirSvc.EXE)
http://www.microsoft.com/downloads/details.aspx?FamilyID=CEBF3C7C-7CA5-408F-
88B7-F9C79B7306C0&displaylang=en
----------------------------------------------------------------------------
-------------------

Please send the MPS report CAB file and screen shot file to
tfwst@microsoft.com with the following three lines for this issue in the
email body:


File Replication errors n Event log on Server
#42319311
Miles Li - MSFT


Hope this helps. Also, if you have any questions or concerns, please do not
hesitate to let me know.



Sincerely,
Miles Li

Microsoft Online Partner Support
Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Edwin vMierlo [MVP]]

Re: File Replication errors n Event log on Server



> Edwin,
>
> Microsoft actually provide a guaranteed 1 business day response to
certain
> "managed newsgroups" under the Technet Plus program and this is one of
them
> . So in fact Microsoft should respond to this request for help - and
within
> 1 business day.
>
> Part of the text of thier Technet Subscription Benefits reads ...
> Managed Newsgroup Support. TechNet Plus provides unlimited access to over
> 100 Managed Newsgroups. Exchange ideas with other IT Professionals and get
> expert answers to your technical questions within the next business
> day-guaranteed.
>
> Hope this help explain why Philip is trying to get MS attention - I see he
> has a Technet Plus Subscription.
>
> A.
>

thanks for that info, I did not realise this is one of them, first time I
hear that.

You are the first to make that statement while many, many others have
claimed the opposite.

rgds,
Edwin.

 

[Meinolf Weber]

Re: File Replication errors n Event log on Server

Hello Andrew,

You never stop learning, me too. Logged in with our Technet Plus ID and see
it also. Think that during the first post he didn't login like described
here: http://technet.microsoft.com/en-us/subscriptions/ms772427.aspx "Accessing
Your Subscriber Benefits" where you find the way how to do it.

Thank's for clarifying this part.

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

> Edwin,
>
> Microsoft actually provide a guaranteed 1 business day response to
> certain "managed newsgroups" under the Technet Plus program and this
> is one of them . So in fact Microsoft should respond to this request
> for help - and within 1 business day.
>
> Part of the text of thier Technet Subscription Benefits reads ...
> Managed Newsgroup Support. TechNet Plus provides unlimited access to
> over
> 100 Managed Newsgroups. Exchange ideas with other IT Professionals and
> get
> expert answers to your technical questions within the next business
> day-guaranteed.
> Hope this help explain why Philip is trying to get MS attention - I
> see he has a Technet Plus Subscription.
>
> A.
>
> "Edwin vMierlo [MVP]" <EdwinvMierlo@discussions.microsoft.com> wrote
> in message news:eFMLafy6IHA.3816@TK2MSFTNGP03.phx.gbl...
>
>> hi Phil,
>>
>> these newsgroups are public and not from "Microsoft Technet" or any
>> Microsoft Support organisation.
>>
>> Anyone here is answering posts on a voluntary basis. You might find
>> people from Microsoft here, but they do this on their own account and
>> free time, not official support from Microsoft.
>>
>> Please see your Technet subscription details on how to obtain
>> official support
>>
>> Rgds,
>> Edwin.
>> "Phil Walker" <bramblewood@noemail.noemail> wrote in message
>> news:OMV$gyx6IHA.3652@TK2MSFTNGP04.phx.gbl...
>>
>>> I have been told by Microsoft to re-send this e-mail with the
>>> correct
>>>
>> email
>>
>>> address as we have Technet Plus and a Microsoft engineer will reply
>>> with help...........
>>>
>>> I was checking the event logs in File replication and I have this
>>> error.
>>> I
>>> have a C, F, H and X: Drives and this system and not sure why is
>>> mentions
>>> d:\....?
>>> Event ID 13539
>>>
>>> The File Replication Service cannot replicate d:\ad\sysvol\domain
>>> because the pathname of the replicated directory is not the fully
>>> qualified
>>>
>> pathname
>>
>>> of an existing, accessible local directory.
>>>
>>> and
>>>
>>> Event ID 13552
>>>
>>> he File Replication Service is unable to add this computer to the
>>>
>> following
>>
>>> replica set:
>>> "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
>>> This could be caused by a number of problems such as:
>>> -- an invalid root path,
>>> -- a missing directory,
>>> -- a missing disk volume,
>>> -- a file system on the volume that does not support NTFS 5.0
>>> The information below may help to resolve the problem:
>>> Computer DNS name is "hddesign3.hd-design.local"
>>> Replica set member name is "HDDESIGN3"
>>> Replica set root path is "d:\ad\sysvol\domain"
>>> Replica staging directory path is "d:\ad\sysvol\staging\domain"
>>> Replica working directory path is "c:\windows\ntfrs\jet"
>>> Windows error status code is
>>> FRS error status code is FrsErrorStageDirOpenFail
>>> Then when I check registry entries have noticed in the following
>>> registry entries under
>>>
>>> HKLM\system\CurrentControlSet\Services\Ntfrs\Parameters\Replica
>>> Sets\
>>>
>>> 2 folders
>>>
>>> c4276d80-7893-4142-b8622fe475746e83
>>> inside this folder:
>>> (Default) REG_SZ (value not set)
>>> Relica Set name REG_SZ DOMAIN SYSTEM VOLUME
>>> (SYSVOL
>>> SHARE)
>>> Replica Set Root REG_SZ d:\ad\sysvol\domain
>>> Replica Set Stage REG_SZ
>>> d:\ad\sysvol\staging\domain
>>> Replica Set Tombstoned REG_DWORD 0x0000000 (0)
>>> Replica Set Type REG_SZ Domain
>>> f8a48965-5f20-42dd-afa32b998fc2d3fd
>>> inside this folder:
>>> (Default) REG_SZ (value not set)
>>> Relica Set name REG_SZ DOMAIN SYSTEM VOLUME
>>> (SYSVOL
>>> SHARE)
>>> Replica Set Root REG_SZ
>>> dc:\windows\sysvol\domain
>>> Replica Set Stage REG_SZ
>> c:\windows\sysvol\staging\domain
>>
>>> Replica Set Tombstoned REG_DWORD 0x0000000 (0) Replica Set
>>> Type REG_SZ Domain
>>>
>>> Can I just delete the 1st folder registry entry that mentions d:\ad?
>>> as
>>>
>> this
>>
>>> does not
>>> exist..............

 

[Zaz]

Re: File Replication errors n Event log on Server

Hello Miles,

1. Where is the SYSVOL folder stored currently? Is it in the
c:\windows\sysvol? Does it keep consistent with other domain controller in
the domain?
Yes it is in the folder c:\windows\sysvol. There is no other Domain
controller in the domain (only one). Orginally this server was part of a
bigger domain and part of the company split away. The FSMO roles fro the
domain where passed to this server.

2. Have you tried to relocate the SYSVOL folder to d:\ad\sysvol\? How do
you get the DOMAIN SYSTEM VOLUME replication set for d:\ad\sysvol\?

This maybe due to the domain setup when it had others servers in the domain
and a relocate was setup?. When the company was split, this server was
relocated to new offices and is the only DC in the domain now.

d) In Attributes, locate fRSRootPath and fRSStagingPath. Does it begin
with "D:\Windows\Sysvol"?

These already have:

fRSRootPath = C:\WINDOWS\SYSVOL\domain
fRSStagingPath = C:\WINDOWS\SYSVOL\staging\domain

a) In Registry Editor, navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters.
b) Sysvol appears in the details pane. Ensure the current value is
c:\windows\sysvol\sysvol - it already this..........

c) Navigate to the
[HKEY_LOCAL_MACHINE\System\CCS\Services\NTFRS\Parameters\Replica Sets]
registry key.
d) Locate the problematic replica set. All replica sets are displayed as
a GUID. If you click a GUID, one of the values on the right is Replica Set
Name and the value of "Replica Set Stage" stores the path to the staging
area. Is it correct? If not, please modify it to point to correct one.

As mentioned in my previuos email i have 2 GUID entries

HKLM\system\CurrentControlSet\Services\Ntfrs\Parameters\Replica Sets\

2 GUID folders

c4276d80-7893-4142-b8622fe475746e83
inside this folder:
(Default) REG_SZ (value not set)
Relica Set name REG_SZ DOMAIN SYSTEM VOLUME (SYSVOL
SHARE)
Replica Set Root REG_SZ d:\ad\sysvol\domain
Replica Set Stage REG_SZ d:\ad\sysvol\staging\domain
Replica Set Tombstoned REG_DWORD 0x0000000 (0)
Replica Set Type REG_SZ Domain

f8a48965-5f20-42dd-afa32b998fc2d3fd
inside this folder:
(Default) REG_SZ (value not set)
Relica Set name REG_SZ DOMAIN SYSTEM VOLUME (SYSVOL
SHARE)
Replica Set Root REG_SZ dc:\windows\sysvol\domain
Replica Set Stage REG_SZ c:\windows\sysvol\staging\domain
Replica Set Tombstoned REG_DWORD 0x0000000 (0)
Replica Set Type REG_SZ Domain

 

[Edwin vMierlo [MVP]]

Re: File Replication errors n Event log on Server

amazing, just did the same here.... never knew !


"Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
news:ff16fb66a45198caba12494646e6@msnews.microsoft.com...
> Hello Andrew,
>
> You never stop learning, me too. Logged in with our Technet Plus ID and
see
> it also. Think that during the first post he didn't login like described
> here: http://technet.microsoft.com/en-us/subscriptions/ms772427.aspx
"Accessing
> Your Subscriber Benefits" where you find the way how to do it.
>
> Thank's for clarifying this part.
>
> 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
>
> > Edwin,
> >
> > Microsoft actually provide a guaranteed 1 business day response to
> > certain "managed newsgroups" under the Technet Plus program and this
> > is one of them . So in fact Microsoft should respond to this request
> > for help - and within 1 business day.
> >
> > Part of the text of thier Technet Subscription Benefits reads ...
> > Managed Newsgroup Support. TechNet Plus provides unlimited access to
> > over
> > 100 Managed Newsgroups. Exchange ideas with other IT Professionals and
> > get
> > expert answers to your technical questions within the next business
> > day-guaranteed.
> > Hope this help explain why Philip is trying to get MS attention - I
> > see he has a Technet Plus Subscription.
> >
> > A.
> >
> > "Edwin vMierlo [MVP]" <EdwinvMierlo@discussions.microsoft.com> wrote
> > in message news:eFMLafy6IHA.3816@TK2MSFTNGP03.phx.gbl...
> >
> >> hi Phil,
> >>
> >> these newsgroups are public and not from "Microsoft Technet" or any
> >> Microsoft Support organisation.
> >>
> >> Anyone here is answering posts on a voluntary basis. You might find
> >> people from Microsoft here, but they do this on their own account and
> >> free time, not official support from Microsoft.
> >>
> >> Please see your Technet subscription details on how to obtain
> >> official support
> >>
> >> Rgds,
> >> Edwin.
> >> "Phil Walker" <bramblewood@noemail.noemail> wrote in message
> >> news:OMV$gyx6IHA.3652@TK2MSFTNGP04.phx.gbl...
> >>
> >>> I have been told by Microsoft to re-send this e-mail with the
> >>> correct
> >>>
> >> email
> >>
> >>> address as we have Technet Plus and a Microsoft engineer will reply
> >>> with help...........
> >>>
> >>> I was checking the event logs in File replication and I have this
> >>> error.
> >>> I
> >>> have a C, F, H and X: Drives and this system and not sure why is
> >>> mentions
> >>> d:\....?
> >>> Event ID 13539
> >>>
> >>> The File Replication Service cannot replicate d:\ad\sysvol\domain
> >>> because the pathname of the replicated directory is not the fully
> >>> qualified
> >>>
> >> pathname
> >>
> >>> of an existing, accessible local directory.
> >>>
> >>> and
> >>>
> >>> Event ID 13552
> >>>
> >>> he File Replication Service is unable to add this computer to the
> >>>
> >> following
> >>
> >>> replica set:
> >>> "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
> >>> This could be caused by a number of problems such as:
> >>> -- an invalid root path,
> >>> -- a missing directory,
> >>> -- a missing disk volume,
> >>> -- a file system on the volume that does not support NTFS 5.0
> >>> The information below may help to resolve the problem:
> >>> Computer DNS name is "hddesign3.hd-design.local"
> >>> Replica set member name is "HDDESIGN3"
> >>> Replica set root path is "d:\ad\sysvol\domain"
> >>> Replica staging directory path is "d:\ad\sysvol\staging\domain"
> >>> Replica working directory path is "c:\windows\ntfrs\jet"
> >>> Windows error status code is
> >>> FRS error status code is FrsErrorStageDirOpenFail
> >>> Then when I check registry entries have noticed in the following
> >>> registry entries under
> >>>
> >>> HKLM\system\CurrentControlSet\Services\Ntfrs\Parameters\Replica
> >>> Sets\
> >>>
> >>> 2 folders
> >>>
> >>> c4276d80-7893-4142-b8622fe475746e83
> >>> inside this folder:
> >>> (Default) REG_SZ (value not set)
> >>> Relica Set name REG_SZ DOMAIN SYSTEM VOLUME
> >>> (SYSVOL
> >>> SHARE)
> >>> Replica Set Root REG_SZ d:\ad\sysvol\domain
> >>> Replica Set Stage REG_SZ
> >>> d:\ad\sysvol\staging\domain
> >>> Replica Set Tombstoned REG_DWORD 0x0000000 (0)
> >>> Replica Set Type REG_SZ Domain
> >>> f8a48965-5f20-42dd-afa32b998fc2d3fd
> >>> inside this folder:
> >>> (Default) REG_SZ (value not set)
> >>> Relica Set name REG_SZ DOMAIN SYSTEM VOLUME
> >>> (SYSVOL
> >>> SHARE)
> >>> Replica Set Root REG_SZ
> >>> dc:\windows\sysvol\domain
> >>> Replica Set Stage REG_SZ
> >> c:\windows\sysvol\staging\domain
> >>
> >>> Replica Set Tombstoned REG_DWORD 0x0000000 (0) Replica Set
> >>> Type REG_SZ Domain
> >>>
> >>> Can I just delete the 1st folder registry entry that mentions d:\ad?
> >>> as
> >>>
> >> this
> >>
> >>> does not
> >>> exist..............
>
>

 

[Zaz]

Re: File Replication errors n Event log on Server

OK Miles data sent to email as requested

"Miles Li [MSFT]" <v-mileli@online.microsoft.com> wrote in message
newsjpX0W%236IHA.3588@TK2MSFTNGHUB02.phx.gbl...
> Hello,
>
> Thank you for your post.
>
> Please allow me to confirm that my understandings are correct. As I
> understand it, the issue is:
>
> You receive the Event ID 13539 and 13552 that indicates the FRS cannot
> replication the d:\ad\sysvol\ folder as the SYSVOL folder.
>
> If I have misunderstood your concerns please feel free to let me know.
>
> Suggestions:
> ==============
>
> I'd like to ask some questions about the issue:
>
> 1. Where is the SYSVOL folder stored currently? Is it in the
> c:\windows\sysvol? Does it keep consistent with other domain controller in
> the domain?
> 2. Have you tried to relocate the SYSVOL folder to d:\ad\sysvol\? How do
> you get the DOMAIN SYSTEM VOLUME replication set for d:\ad\sysvol\?
>
> According to the symptom, it seems that the path to the FRS subscription
> is
> set incorrectly. Please also check the following aspects to indentify the
> effective SYSVOL folder:
>
> 1. Identify the fRSRootPath and fRSStagingPath in that domain controller
> computer account.
>
> a) Click Start, click Run, type adsiedit.msc, and then press Enter.
> b) Expand the CN=NTFRS Subscriptions container, CN=computername,
> OU=Domain Controllers, DC=domain, DC=local in the tree view.
> c) In the details pane, right-click CN=Domain System Volume, and then
> click Properties.
> d) In Attributes, locate fRSRootPath and fRSStagingPath. Does it begin
> with "D:\Windows\Sysvol"? If the path is set wrong, please edit the path
> to
> point to the correct SYSVOL path. Generally speaking, SYSVOL folder is
> stored in the c:\windows\sysvol folder.
>
> 2. Identify the SYSVOL parameter in the registry
>
> a) In Registry Editor, navigate to
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters.
> b) Sysvol appears in the details pane. Ensure the current value is
> c:\windows\sysvol\sysvol
> c) Navigate to the
> [HKEY_LOCAL_MACHINE\System\CCS\Services\NTFRS\Parameters\Replica Sets]
> registry key.
> d) Locate the problematic replica set. All replica sets are displayed as
> a GUID. If you click a GUID, one of the values on the right is Replica Set
> Name and the value of "Replica Set Stage" stores the path to the staging
> area. Is it correct? If not, please modify it to point to correct one.
>
>
> As deleting the SYSVOL registry key and folder is dangerous, I'd like to
> suggest that we temporarily hold this step before we are clearing about
> the
> problem and the background.
>
> For your reference:
> ==============
> Relocating SYSVOL Manually
> http://technet2.microsoft.com/windowsserver/en/library/300796c6-8148-49af-a3
> 27-b5dca853ac4f1033.mspx
>
> Introduction to Administering SYSVOL
> http://technet2.microsoft.com/windowsserver/en/library/551f0123-26a7-4ce5-be
> 71-173e7aa79bd31033.mspx
>
> Best Practices for Sysvol Maintenance
> http://support.microsoft.com/kb/324175
>
>
>
> Please also collect DirSvc version of MPSReport which contains the FRS
> objects. You can get this tool from the link:
>
> Microsoft Product Support's Reporting Tools (MPSRPT_DirSvc.EXE)
> http://www.microsoft.com/downloads/details.aspx?FamilyID=CEBF3C7C-7CA5-408F-
> 88B7-F9C79B7306C0&displaylang=en
> ----------------------------------------------------------------------------
> -------------------
>
> Please send the MPS report CAB file and screen shot file to
> tfwst@microsoft.com with the following three lines for this issue in the
> email body:
>
>
> File Replication errors n Event log on Server
> #42319311
> Miles Li - MSFT
>
>
> Hope this helps. Also, if you have any questions or concerns, please do
> not
> hesitate to let me know.
>
>
>
> Sincerely,
> Miles Li
>
> Microsoft Online Partner Support
> Microsoft Global Technical Support Center
>
> Get Secure! - www.microsoft.com/security
> =====================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>

 

[Miles Li [MSFT]]

Re: File Replication errors n Event log on Server

Hello,


I'd like to know whether fRSRootPath and fRSStagingPath in that domain
controller computer account is correct and if the system will pass the
DCDIAG frs test successfully. If all related attribute indicates the SYSVOL
folder resides in the default place c:\windows\sysvol and the SYSVOL
replication set d:\ad\sysvol\ is unnecessary, you can safely delete the
Replica Sets with d:\ad\sysvol\.

HKLM\system\CurrentControlSet\Services\Ntfrs\Parameters\Replica Sets\
c4276d80-7893-4142-b8622fe475746e83

Please make sure that you have backup the system before performing the
change in the registry.

Then restart the server to check how it works.


Sincerely,
Miles Li

Microsoft Online Partner Support
Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Zaz]

Re: File Replication errors n Event log on Server

I have attached DCDIAG on this system. Can you confirm if ok to delete
registry entry? I have also sent MSreports to you via other
email.......Await you response

Thanks

"Miles Li [MSFT]" <v-mileli@online.microsoft.com> wrote in message
news:JINMnUL7IHA.1620@TK2MSFTNGHUB02.phx.gbl...
> Hello,
>
>
> I'd like to know whether fRSRootPath and fRSStagingPath in that domain
> controller computer account is correct and if the system will pass the
> DCDIAG frs test successfully. If all related attribute indicates the
> SYSVOL
> folder resides in the default place c:\windows\sysvol and the SYSVOL
> replication set d:\ad\sysvol\ is unnecessary, you can safely delete the
> Replica Sets with d:\ad\sysvol\.
>
> HKLM\system\CurrentControlSet\Services\Ntfrs\Parameters\Replica Sets\
> c4276d80-7893-4142-b8622fe475746e83
>
> Please make sure that you have backup the system before performing the
> change in the registry.
>
> Then restart the server to check how it works.
>
>
> Sincerely,
> Miles Li
>
> Microsoft Online Partner Support
> Microsoft Global Technical Support Center
>
> Get Secure! - www.microsoft.com/security
> =====================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>

 

[Miles Li [MSFT]]

Re: File Replication errors n Event log on Server

Hello,

I have received the MPS report and the result is that:

1. DCDIAG: everything related to FRS (SYSVOL) is clean
2. GPOTOOL: all group policy pass the check successfully
3. FRSDS: the subscriber of SYSVOL SHARE (for c:\windows\sysvol\) under
the computer account is clean. The entry for d:\ad\sysvol\ is not
registered.
4. GPresult: the domain controller gets the group policies applied
successfully.
5. Eventlog: NTFrs Event ID 13555, 13552, 13539 is received.

From the report, the incorrect SYSVOL SHARE replication set (d:\ad\sysvol\)
is only registered on the computer local registry. You can delete it as we
discussed in the last post. However, please make sure that a registry
backup is available before any modifications of the registry.

If you have any questions or concerns, please do not hesitate to let me
know.



Best regards,
Miles Li

Microsoft Online Partner Support
Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Zaz]

Re: File Replication errors n Event log on Server

OK I have done that and restarted the file replication service and now
getting Event ID 13516 which is good!

Do I need to reboot server? I think we are there!


"Miles Li [MSFT]" <v-mileli@online.microsoft.com> wrote in message
news:BVohMPY7IHA.1624@TK2MSFTNGHUB02.phx.gbl...
> Hello,
>
> I have received the MPS report and the result is that:
>
> 1. DCDIAG: everything related to FRS (SYSVOL) is clean
> 2. GPOTOOL: all group policy pass the check successfully
> 3. FRSDS: the subscriber of SYSVOL SHARE (for c:\windows\sysvol\) under
> the computer account is clean. The entry for d:\ad\sysvol\ is not
> registered.
> 4. GPresult: the domain controller gets the group policies applied
> successfully.
> 5. Eventlog: NTFrs Event ID 13555, 13552, 13539 is received.
>
> From the report, the incorrect SYSVOL SHARE replication set
> (d:\ad\sysvol\)
> is only registered on the computer local registry. You can delete it as we
> discussed in the last post. However, please make sure that a registry
> backup is available before any modifications of the registry.
>
> If you have any questions or concerns, please do not hesitate to let me
> know.
>
>
>
> Best regards,
> Miles Li
>
> Microsoft Online Partner Support
> Microsoft Global Technical Support Center
>
> Get Secure! - www.microsoft.com/security
> =====================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>

 

[Miles Li [MSFT]]

Re: File Replication errors n Event log on Server


Hello,

I am glad to know that the issue is solved. The Event ID 13516 after the
start the FRS indicates that the domain controller is running and ready for
service. There is no need to restart the server. Please keep on monitoring
the FRS event log for some time.

If you have further questions, please do not hesitate to let me know.


Best regards,
Miles Li

Microsoft Online Partner Support
Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Zaz]

Re: File Replication errors n Event log on Server

I am not sure if this is related to the sysvol issue but for awhile now
(before) changes I have not been able to back up the system state on this
server. When I run NTbackup I get the following error in the log:

Folder System State\SYSVOL
Could not access portions of directory System State\SYSVOL.
You may not have permission to open the file, or the directory may be
missing or damaged.
Please contact the owner or administrator.

Also in my Application event log I am getting Event ID 1091 Source userenv.
If I check the gptext.log file is has:

GPTEXT(e8.175c) 13:04:55:830 CPolicyComponentData::AddTemplates: Failed to
copy <C:\WINDOWS\inf\wuau.adm> to
<\\mydomain.local\SysVol\hd-design.local\Policies\{0B47BD76-DCF0-420A-97D4-F75EE5BF2EEE}\Adm>
with 7.
GPTEXT(cc0.1060) 15:31:11:671 CPolicyComponentData::EnumerateScopePane: ADM
event has been signaled.

'mydomain.local' is really my domain name. Changed it for this post.

 

[Miles Li [MSFT]]

Re: File Replication errors n Event log on Server


Hello,

About the NTbackup error "Could not access portions of directory System
State\SYSVOL", please check the following two aspects:

1. The permission on the SYSVOL folder.
a. Which user account is logged on when you perform the backup.
b. Please verify the NTFS permission on the SYSVOL folder.

2. Please make sure that the junction points is correct on the 2 folders:

\SYSVOL\SYSVOL\Domain Name
There is a junction point must be linked to the \SYSVOL\domain
folder.

\SYSVOL\staging areas\Domain Name
There is a junction point must be linked to the \SYSVOL\staging\domain
folder

205524 How to create and manipulate NTFS junction points
http://support.microsoft.com/kb/205524


For the Event ID 1091, you may refer to the following Microsoft KB article.
This error is not related to the SYSVOL FRS replication that we discussed.

931352 Event ID 1091 is frequently logged in the Application log
on a Windows Server 2003-based computer
http://support.microsoft.com/kb/931352


Best regards,
Miles Li

Microsoft Online Partner Support
Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Zaz]

Re: File Replication errors n Event log on Server

> About the NTbackup error "Could not access portions of directory System
> State\SYSVOL", please check the following two aspects:
>
> 1. The permission on the SYSVOL folder.
Permission are:
Administrators Full Control
Authenicated users Read & Execute, List Folder Contents, read &
special permissions (read) special
permssion deny greyed out but nothing set.
Creator Owner - special permissions
Server Operator - Read & Execute, List Folder Contents, read &
special permissionsspecial permissions
(read) special
permssion deny greyed out but nothing set.
System - Full Control


> a. Which user account is logged on when you perform the backup.
Administrator

> b. Please verify the NTFS permission on the SYSVOL folder.
Permission are:
Administrators Full Control
Authenicated users Read & Execute, List Folder Contents, read &
special permissions (read) special
permssion deny greyed out but nothing set.
Creator Owner - special permissions
Server Operator - Read & Execute, List Folder Contents, read &
special permissionsspecial permissions
(read) special
permssion deny greyed out but nothing set.
System - Full Control

> 2. Please make sure that the junction points is correct on the 2 folders:

Details of running linkd

F:\Program Files\Windows Resource Kits\Tools>linkd
C:\WINDOWS\sysvol\sysvol\hd-design.local C:\WINDOWS\sysvol\domain"
Link created at: C:\WINDOWS\sysvol\sysvol\hd-design.local

F:\Program Files\Windows Resource Kits\Tools>Linkd
"C:\WINDOWS\sysvol\staging areas\hd-design.local"
"C:\WINDOWS\SYSVOL\staging\domain"
Link created at: C:\WINDOWS\sysvol\staging areas\hd-design.local

 

[Miles Li [MSFT]]

Re: File Replication errors n Event log on Server

Hello,

To further troubleshooting the issue, please follow the steps below:

1. Reboot the server into a Clean Boot environment then try to backup the
system.

a) Type msconfig in the command prompt and press Enter
b) Click Services tab and select Hide All Microsoft Services and Disable
All third party Services.
c) Click Startup tab and Disable All startup items
d) Click OK and choose Restart
e) After reboot, check whether NTbackup can works.

2. Disable or uninstall Antivirus software.

Antivirus software that scan the files in SYSVOL folder may prevent the
NTbackup from backup files and folders successfully. Please try to disable
or uninstall any Antivirus software on the computer to have a try.


3. If the problem continues, please help to collect NTBackup log file. You
can find NTBackup log file from "%userprofile%\Local Settings\Application
Data\Microsoft\Windows NT\NTBackup\data".

Please send the backup log file to tfwst@microsoft.com including the
following three lines for this issue in the email body:

File Replication errors n Event log on Server
#42319311
Miles Li - MSFT

Thanks.




Best regards,
Miles Li

Microsoft Online Partner Support
Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Miles Li [MSFT]]

Re: File Replication errors n Event log on Server

Hello,

I am just checking on your progress regarding the information that was sent
to you. If anything is unclear with the previous information I've provided
to you, please don't hesitate to let me know.

Best regards,
Miles Li

Microsoft Online Partner Support
Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.