Classification Stopped

Microsoft.Windows.FileServices.Service.FCI.ClassificationAborted (UnitMonitor)

This monitor checks to see if the classification operation stopped.

Knowledge Base article:

Summary

You can use the File Classification Infrastructure (FCI) to categorize files and to select files for scheduled file management tasks.

Classification operations usually stop in one of two ways:

The classification operation completes successfully
The time allotted to classify files runs out

When classification stops for other reasons, this usually indicates that there are issues that should be addressed by a member of the Administrators group. If the classification process stopped prematurely, it will likely happen again in future classification operations, and it may prevent complete classification of the server.

Causes

Classification operations that stop prematurely are often caused by the following:

Corrupted files that cause a classification or storage module to fail
Mount points that refer to volumes that no longer exist

Resolutions

Install updates

To fix this issue, you should begin by viewing the following articles and installing the associated updates. (To install updates, you must be a member of the Administrators group):

Microsoft Knowledge Base article 976096 (http://go.microsoft.com/fwlink/?LinkId=184960)
Microsoft Knowledge Base article 977375 (http://go.microsoft.com/fwlink/?LinkId=184961)
Microsoft Knowledge Base article 979539 (http://go.microsoft.com/fwlink/?LinkId=184962)

Review events

If the error persists, an administrator who is familiar with FCI should review the event logs for the cause of the stopped classification operation.

To access event logs to troubleshoot classification operations that have stopped prematurely:

1. Click Start, click Administrative Tools, and then click Event Viewer.

2. In the left pane, click Custom Views, click Server Roles, and then click File Server.

3. In the Source column, look for events with a source of SRMSVC or SRMREPORTS.

4. Click any events of interest and review the information on the General and Details tabs.

Verification

Verify that future classification operations will run successfully by running the operation that failed or waiting for the next scheduled classification.

To run a classification operation:

1. Click Start, click Administrative Tools, and then click File Server Resource Manager.

2. In the left pane, double-click Classification Management, right-click Classification Rules, and then click Run Classification With All Rules Now.

Element properties:

Target

Microsoft.Windows.FileServices.Service.FCI.10.0

Parent Monitor

System.Health.AvailabilityState

Category

AvailabilityHealth

Enabled

True

Alert Generate

True

Alert Severity

Error

Alert Priority

Normal

Alert Auto Resolve

True

Monitor Type

Microsoft.Windows.2SingleEventLog2StateMonitorType

Remotable

True

Accessibility

Public

Alert Message

File Classification Stopped

File classification on computer {0} has stopped

RunAs

Default

Source Code:

<UnitMonitor ID="Microsoft.Windows.FileServices.Service.FCI.ClassificationAborted" Accessibility="Public" Enabled="true" Target="Microsoft.Windows.FileServices.Service.FCI.10.0" ParentMonitorID="SystemHealth!System.Health.AvailabilityState" Remotable="true" Priority="Normal" TypeID="Windows!Microsoft.Windows.2SingleEventLog2StateMonitorType" ConfirmDelivery="true">

  <Category>AvailabilityHealth</Category>

  <AlertSettings AlertMessage="Microsoft.Windows.FileServices.Service.FCI.ClassificationAborted.AlertMessage">

    <AlertOnState>Error</AlertOnState>

    <AutoResolve>true</AutoResolve>

    <AlertPriority>Normal</AlertPriority>

    <AlertParameters>

      <AlertParameter1>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</AlertParameter1>

    </AlertParameters>

  </AlertSettings>

  <OperationalStates>

    <OperationalState ID="FirstEventRaised" MonitorTypeStateID="FirstEventRaised" HealthState="Error"/>

    <OperationalState ID="SecondEventRaised" MonitorTypeStateID="SecondEventRaised" HealthState="Success"/>

  </OperationalStates>

  <Configuration>

    <FirstComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</FirstComputerName>

    <FirstLogName>Application</FirstLogName>

    <FirstExpression>

      <And>

        <Expression>

          <RegExExpression>

            <ValueExpression>

              <XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery>

            </ValueExpression>

            <Operator>MatchesRegularExpression</Operator>

            <Pattern>^(8241|8242|8247)$</Pattern>

          </RegExExpression>

        </Expression>

        <Expression>

          <SimpleExpression>

            <ValueExpression>

              <XPathQuery Type="String">PublisherName</XPathQuery>

            </ValueExpression>

            <Operator>Equal</Operator>

            <ValueExpression>

              <Value Type="String">SrmSvc</Value>

            </ValueExpression>

          </SimpleExpression>

        </Expression>

      </And>

    </FirstExpression>

    <SecondComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</SecondComputerName>

    <SecondLogName>Application</SecondLogName>

    <SecondExpression>

      <And>

        <Expression>

          <RegExExpression>

            <ValueExpression>

              <XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery>

            </ValueExpression>

            <Operator>MatchesRegularExpression</Operator>

            <Pattern>^(906|908)$</Pattern>

          </RegExExpression>

        </Expression>

        <Expression>

          <SimpleExpression>

            <ValueExpression>

              <XPathQuery Type="String">PublisherName</XPathQuery>

            </ValueExpression>

            <Operator>Equal</Operator>

            <ValueExpression>

              <Value Type="String">SrmReports</Value>

            </ValueExpression>

          </SimpleExpression>

        </Expression>

      </And>

    </SecondExpression>

  </Configuration>

</UnitMonitor>