Home
  •  

DFS-N: AD DS Site Support Table Initialization

Microsoft.Windows.FileServer.DFSN.10.0.Service.ADSiteSupportTableInitialization (UnitMonitor)

This object monitors whether DFS Namespaces can initialize the site support table.

Knowledge Base article:

Summary

This object monitors whether DFS Namespaces can initialize the site support table by looking for the presence of DfsSvc event 14524 and creates a Warning alert if initialization fails.

Causes

The DFS Namespace service failed to contact a domain controller. This can occur for many reasons including:

Resolutions

Test network connectivity

To test network connectivity with the affected server, use the following procedure:

1. Open a command prompt window and then use the ping command to check basic network connectivity. If the ping command fails, it is likely that the server is not running, or has network problems that require local access to resolve. If ping is blocked in your network environment, skip this step.

2. If the ping command is successful, test the servers registration in DNS by using the nslookup command. If the nslookup command fails, there is a problem with DNS. Check the DNS server health or contact the DNS server administrator.

3. If the nslookup command succeeds, it is likely that the shared folder is offline (possibly for maintenance) or there are problems with the permissions on the shared folder.

Restart the DFS Namespace service

If communication with a domain controller fails, or DFS metadata is inconsistent, restart the DFS Namespace service.

Note To restart a service, you must be a member of the local Administrators group on the affected server.

To restart the service, use the Services snap-in, the Windows PowerShell Start-Service and Stop-Service cmdlets, or command-line tools such as net stop and net start. To restart the service remotely by using the sc command, open a command prompt window and then do the following:

1.To stop the service, type the following command, where [ServerName] is the Universal Naming Convention (UNC) path to the remote server:

sc [ServerName] stop dfs

2.To confirm that the service is in the STOPPED state, type the following command:

sc [ServerName] query dfs

3.To restart the service, type the following command:

sc [ServerName] start dfs

Verification

To test communication with ADDS, use the dfsdiag /testdcs command. Confirm that all domain controllers report healthy results.

Additional

DFS Namespaces Event 14524 (http://go.microsoft.com/fwlink/?LinkId=186537)

Element properties:

TargetMicrosoft.Windows.FileServer.DFSN.10.0.Service
Parent MonitorSystem.Health.AvailabilityState
CategoryAvailabilityHealth
EnabledTrue
Alert GenerateTrue
Alert SeverityWarning
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeMicrosoft.Windows.2SingleEventLog2StateMonitorType
RemotableTrue
AccessibilityPublic
Alert Message
DFS-N: Could not initialize the site support table
{0}
RunAsDefault

Source Code:

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

  <Category>AvailabilityHealth</Category>

  <AlertSettings AlertMessage="Microsoft.Windows.FileServer.DFSN.10.0.Service.ADSiteSupportTableInitialization_AlertMessageResourceID">

    <AlertOnState>Warning</AlertOnState>

    <AutoResolve>true</AutoResolve>

    <AlertPriority>Normal</AlertPriority>

    <AlertSeverity>Warning</AlertSeverity>

    <AlertParameters>

      <AlertParameter1>$Data/Context/EventDescription$</AlertParameter1>

    </AlertParameters>

  </AlertSettings>

  <OperationalStates>

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

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

  </OperationalStates>

  <Configuration>

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

    <FirstLogName>System</FirstLogName>

    <FirstExpression>

      <And>

        <Expression>

          <SimpleExpression>

            <ValueExpression>

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

            </ValueExpression>

            <Operator>Equal</Operator>

            <ValueExpression>

              <Value Type="UnsignedInteger">14524</Value>

            </ValueExpression>

          </SimpleExpression>

        </Expression>

        <Expression>

          <RegExExpression>

            <ValueExpression>

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

            </ValueExpression>

            <Operator>ContainsSubstring</Operator>

            <Pattern>DfsSvc</Pattern>

          </RegExExpression>

        </Expression>

      </And>

    </FirstExpression>

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

    <SecondLogName>System</SecondLogName>

    <SecondExpression>

      <And>

        <Expression>

          <SimpleExpression>

            <ValueExpression>

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

            </ValueExpression>

            <Operator>Equal</Operator>

            <ValueExpression>

              <Value Type="UnsignedInteger">14531</Value>

            </ValueExpression>

          </SimpleExpression>

        </Expression>

        <Expression>

          <RegExExpression>

            <ValueExpression>

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

            </ValueExpression>

            <Operator>ContainsSubstring</Operator>

            <Pattern>DfsSvc</Pattern>

          </RegExExpression>

        </Expression>

      </And>

    </SecondExpression>

  </Configuration>

</UnitMonitor>