RE: File Replication errors n Event log on Server

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

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@xxxxxxxxxxxxx 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.

.

Relevant Pages

  • Re: File Replication errors n Event log on Server
    ... Where is the SYSVOL folder stored currently? ... one of the values on the right is Replica Set ... Miles Li - MSFT ...
    (microsoft.public.windows.server.general)
  • Re: "Not enough storage is available to complete this operation" ?
    ... > The File Replication Service has detected that the replica set "DOMAIN ... > SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR. ... > A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to ...
    (microsoft.public.win2000.group_policy)
  • Re: Active Directory Errrors
    ... non-authoritative restore of sysvol ON my Main DC of site two which has ... INPUNDC2.What will be the impact on the end user if i do the restore using D2 ... The File Replication Service has detected that the replica set "DOMAIN ... Replica set name is: ...
    (microsoft.public.windows.server.active_directory)
  • RE: NTFRS/USERENV SBS2003 Std Issues
    ... "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" ... Replica set member name is "SERVER" ... The File Replication Service has detected that the replica set "DOMAIN ...
    (microsoft.public.windows.server.sbs)
  • Re: File Replication Service problem
    ... Make sure the SYSVOL sharing is present. ... partner or from the computer that is specified in the Replica Set Parent ... <the FRS (File Replication Service) on the SBS must copy the SYSVOL ...
    (microsoft.public.windows.server.sbs)