This monitor checks whether the DFS Namespace service is running.
The namespace server is offline because the DFS Namespace service is not running.
The DFS Namespace service is set to start Automatically, but is not running. A service can stop for many reasons, including:
The service was stopped by an administrator.
The service could not allocate the required memory.
The service was prevented from starting because the user account could not be authenticated.
Restart the DFS Namespaces service
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
Note: To restart a service, you must be a member of the local Administrators group on the affected server.
If these actions do not resolve the problem, it is likely that there are other problems that will require in-depth troubleshooting.
Verification
This monitor resets to a Healthy state after the service starts. To confirm that the service is in the STARTED state, type the following command:
sc <servername> query dfs
| Target | Microsoft.Windows.FileServer.DFSN.6.2.Service | ||
| Parent Monitor | System.Health.AvailabilityState | ||
| Category | AvailabilityHealth | ||
| Enabled | True | ||
| Alert Generate | True | ||
| Alert Severity | Error | ||
| Alert Priority | High | ||
| Alert Auto Resolve | True | ||
| Monitor Type | Microsoft.Windows.CheckNTServiceStateMonitorType | ||
| Remotable | True | ||
| Accessibility | Public | ||
| Alert Message |
| ||
| RunAs | Default |
Home<UnitMonitor ID="Microsoft.Windows.FileServer.DFSN.6.2.Service.AvailabilityState" Accessibility="Public" Enabled="true" Target="Microsoft.Windows.FileServer.DFSN.6.2.Service" ParentMonitorID="Health!System.Health.AvailabilityState" Remotable="true" Priority="Normal" TypeID="Windows!Microsoft.Windows.CheckNTServiceStateMonitorType" ConfirmDelivery="false">
<Category>AvailabilityHealth</Category>
<AlertSettings AlertMessage="Microsoft.Windows.FileServer.DFSN.6.2.Service.AvailabilityState_AlertMessageResourceID">
<AlertOnState>Error</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>High</AlertPriority>
<AlertSeverity>Error</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/PrincipalName$</AlertParameter1>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState ID="Running" MonitorTypeStateID="Running" HealthState="Success"/>
<OperationalState ID="NotRunning" MonitorTypeStateID="NotRunning" HealthState="Error"/>
</OperationalStates>
<Configuration>
<ComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<ServiceName>Dfs</ServiceName>
<CheckStartupType>false</CheckStartupType>
</Configuration>
</UnitMonitor>