none
File Server Resource Manager Error 8197

    Question

  • Event Type: Error
    Event Source: SRMSVC
    Event Category: None
    Event ID: 8197
    Date:  24/05/2010
    Time:  11:50:36
    User:  N/A
    Computer: DATA
    Description:
    File Server Resource Manager Service error: Unexpected error.

    Error-specific details:
       Error: GetVolumeNameForVolumeMountPoint, 0x80071126, The file or directory is not a reparse point.


    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 53 52 4d 56 4f 4c 4d 43   SRMVOLMC
    0008: 38 31 00 00 00 00 00 00   81......
    0010: 53 52 4d 56 4f 4c 4d 43   SRMVOLMC
    0018: 35 37 00 00 00 00 00 00   57......

     

    I am getting this on three servers all running Windows 2003 R2 with the latest service pack and patches. It happens on all three servers every few hours.

    Chris

    Monday, May 24, 2010 11:14 AM

Answers

  • Hello Chris,

     

    Based on the research, the Error-specific details indicates that FSRM is failing to get a volume name for a mount point.

     

    1. Install the hotfixes and reboot the server

     

    The computer may stop responding when you run the disk quota-related functions that are provided by the File Server Resource Manager (FSRM) component on a Windows Server 2003 R2-based computer

    http://support.microsoft.com/kb/939446

     

    On a Windows Server 2003 R2-based computer, the Quota function of the File Server Resource Manager (FSRM) may report incorrect disk usage when both the Quota function and the shadow copies are configured on the same volume

    http://support.microsoft.com/kb/944830

     

    2. Meanwhile, please make sure "System" has full access to quota.xml on all the volumes (Quota.xml is located inside the hidden folder System Volume Information\SRM).

     

    Please also check whether the volume of multiple GUIDs in the following scenarios:

     

    a. Dual booting two or more copies of Windows which access the drive. 

    b. Using a volume on a shared disk in a cluster where multiple nodes have accessed the volume. 

    c. Moving the disk which hosts the volume from one computer to another. 

    d. In a SAN environment where the volume was assigned to multiple instances of Windows. 

     

    I suspect that FSRM may hit the same issue as described in the following KB:

     

    959573  PRB:  GetVolumeNameForVolumeMountPoint API may return Incorrect Name for Volumes with Multiple Names

    http://support.microsoft.com/kb/959573

     

    Hope this can be helpful.


    MCTS: Windows Vista | Exchange Server 2007 MCITP: Enterprise Support Technician | Server & Enterprise Admin
    Tuesday, May 25, 2010 2:05 AM