FRS Error: "Two days in sharing violation install/staging"

Discussion in 'File Systems' started by dathrill, Nov 16, 2005.

  1. dathrill

    dathrill Guest

    We had been having some issues that when a user pushed a file onto the DFS
    and then tried to move it, it would not move. I decided to install
    Ultrasound to see if I could determine what was was wrong.

    Background:
    (1) Windows 2000 Server SP4
    (1) Windows 2003 Server no SP or NTFRS hotfix

    For the affected files, the DFS is setup to replicate a directory between
    these two servers. Only the Win2K3 server has its DFS Referral "enabled".

    Users login to our intranet and run a script that pulls down a file, which
    they then browse to the DFS hierarchy to the DFS folder and save the file
    there. When they go into Explorer, they sometimes have problems moving the
    file to a subfolder after removing the contents on the recently saved ZIP
    file.

    Ultrasound tells me that I have "Two days in sharing violation
    install/staging" for many, many ZIP files in the mentioned DFS folders, with
    problems all the way back to August. Sometimes the same file has multiple
    problems(as I assume that they are trying to move the file multiple times)

    The documentation states:
    "Sharing violations are logged as FRS event ID 13573. This event provides
    the file name and file GUID of the file held open and provides steps to
    resolve the sharing violation. "

    Yet I have no logged errors in my FRS Service Event Log. I have tried using
    FRSDiag, but I can't figure that tool out enough to help me determine the
    problem.

    Any ideas? I'm tempted to burn a MS Incident if I can't get this resolved
    quickly.
     
    dathrill, Nov 16, 2005
    #1
    1. Advertisements

  2. Here's the event text for 13573. See if this helps.



    File Replication Service has been repeatedly prevented from updating:

    File Name: "%1"

    File GUID: "%2"

    due to consistent sharing violations encountered on the file. Sharing
    violations occur when another user or application holds a file open,
    blocking FRS from updating it. Blockage caused by sharing violations can
    result in out-of-date replicated content. FRS will continue to retry this
    update, but will be blocked until the sharing violations are eliminated.

    Possible reasons for a sharing violation are other sources that may have
    opened the file to be replicated in on the target machine.

    To determine the full path of the file in sharing violation open the
    Computer Management, Shared Folders, Open Files from compmgmt.msc for the
    file in question and the user that has the filed opened. Search for the file
    listed above, Right click on the file, Select the close option to forcibly
    close the file. Note if multiple files with the same name are held open you
    may need to close all or perform more detailed steps listed in the KB
    article to determine file with full path that matches the GUID reported in
    the event. The install override feature in the Windows Server 2003 version
    of ntfrs.exe can be used to avoid this blockage by renaming the locked file
    to allow replication to occur. For more information on the install override
    feature in the Windows Server 2003 version of ntfrs.exe and its behavior,
    please refer to http://support.microsoft.com/?id=816493

    To disable logging of this event, edit the following registry keys as
    follows:

    Click Start, Run, and then type regedit.

    Expand HKEY_LOCAL_MACHINE, SYSTEM, CurrentControlSet, Services, NtFrs,
    Parameters, and update the value of "Enable Sharing Violation Logging" to
    FALSE.


    To change the frequency of reporting relative to the number of retries
    performed by FRS, edit the following registry key as follows:

    Click Start, Run, and then type regedit.

    Expand HKEY_LOCAL_MACHINE, SYSTEM, CurrentControlSet, Services, NtFrs,
    Parameters, and create (REG_DWORD, min =1, max=30, default=10) or update the
    value "Sharing Violation Events Counter" to a larger value to reduce the
    frequency of reporting.


    To change the number of events reported per hour, edit the following
    registry key as follows:

    Click Start, Run, and then type regedit.

    Expand HKEY_LOCAL_MACHINE, SYSTEM, CurrentControlSet, Services, NtFrs,
    Parameters, and create (REG_DWORD, min =1, max=60, default=10) or update the
    value "Max Sharing Violation Event".

    FRS will only report at most 60 sharing violation blockages every hour,
    beyond this limit, additional sharing violations may be unreported as
    events. If you suspect that FRS is hitting more sharing violations than
    those reported per hour causing replication to be backlogged, you may need
    to follow the detailed steps listed in the KB article.
     
    Jill Zoeller [MSFT], Nov 17, 2005
    #2
    1. Advertisements

  3. dathrill

    dathrill Guest

    As I stated in the original post, I am NOT receiving anything in the FRS
    Event Log.

    When I drill into the error in Ultrasound, the SharingViolation column has
    all zeroes. I'd be more than happy to provide a screen cap, just tell me
    where to email it.
     
    dathrill, Nov 17, 2005
    #3
  4. My thinking was that perhaps the sharing violation is occuring but for some
    reason no event is being logged. There are some initial tshooting steps in
    the event message that you can use to see if there are sharing violations.

    Can you send a screenshot to ?
     
    Jill Zoeller [MSFT], Nov 17, 2005
    #4
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.