Condividi tramite

Event ID 8197 — FSRM Basic Functionality

  • Articolo

Applies To: Windows Server 2008 R2

File Server Resource Manager (FSRM) uses minifilter drivers to intercept the I/O requests that are sent to the volumes it manages. These minifilter drivers require configuration information from metadata files that are stored in each of the volumes that the minifilter drivers are attached to.

Event Details

Product: Windows Operating System
ID: 8197
Source: srmsvc
Version: 6.1
Symbolic Name: SRM_ERROR_UNEXPECTED_ERRORCODE
Message: File Server Resource Manager Service error: Unexpected error. %1

Resolve

Monitor system resources

Determine if the computer is low on system resources like CPU resources, disk I/O performance, or memory. To identify what is causing the system to be low on resources, you can generate a System Diagnostics Report using Reliability and Performance Monitor, or you can use Resource Monitor to determine, in real-time, which applications or services are utilizing too many system resources.

To generate a System Diagnostics Report, which will present system information collected for 60 seconds, follow the steps in the "Generate a System Diagnostics Report" section. To use Resource Monitor to monitor system resources in real-time, follow the steps in the "Start Resource Monitor" section.

To perform these procedures, you must have membership in Administrators, or you must have been delegated the appropriate authority.

Generate a System Diagnostics Report

To collect system information for 60 seconds and generate a System Diagnostics Report:

  1. Open an elevated command prompt. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
  2. Type perfmon /report and press ENTER. Reliability and Performance Monitor will start collecting data to create the System Diagnostics Report.
  3. When the report is ready for viewing, locate the Diagnostic Results section of the report and check for any Warnings. You can follow links to additional help on resolving warnings from this section. In addition, you can expand each category in the Basic System Checks section to see more details about why warnings appear. Also, the Performance section provides process-level detail about the top consumers of resources.

Start Resource Monitor

To start Resource Monitor:

Important: Resource Monitor stops collecting information while a System Diagnostics Report is being generated. To start collecting information after a System Diagnostics Report has completed, in Monitor, click Start.

  1. Open an elevated command prompt. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
  2. Type perfmon /res and press ENTER. Resource Monitor will start running.
  3. Four scrolling graphs in the Resource Overview pane display the real-time usage of CPU, Disk, Network, and Memory. Four expandable sections below the graphs contain process-level detail about each resource. Click the resource labels to see more information, or click a graph to expand its corresponding details. You can use the real-time usage information to identify the top resource consumers. Click a column heading to sort the data in the table by that column; click the column heading again to reverse the sort order.

Verify

To verify that basic File Server Resource Manager (FSRM) functionality is available, you must verify that the quota and file screening minifilter drivers are attached to the volumes that are managed by File Server Resource Manager.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To verify that the quota and file screening minifilter drivers are attached to the volumes managed by File Server Resource Manager:

  1. Open an elevated command prompt. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.

  2. Type fltmc instances, and press ENTER. A quota minifilter driver is attached to a volume if there is a Quota instance listed for that volume. A file screening minifilter driver is attached to a volume if there is a Datascrn instance listed for that volume. For example, on a computer where file screens are configured for drive C and D, and quotas are configured for drive C, the output of this command would look something like this:

    Filter          Volume Name    Altitude    Instance Name

    ---------    ---------------    --------    ---------------

    Datascrn    C:                       261000    Datascrn   

    Datascrn    D:                       261000    Datascrn   

    Quota        C:                       125000    quota       

FSRM Basic Functionality

File Services