DFS-N: Service Initialization Monitor

  • ID:  Microsoft.Windows.DfsService.InitializationState
  • Description:  This object monitors the initialization of the DFS Namespace service (Distributed File System on Windows Server 2003) and creates an alert if the service fails to initialize.
  • Target:  DFS Service
  • Enabled:  Yes

Operational States

Name State Description
First Event Raised Error  
Second Event Raised Success  

Alert Details

Monitor State Message Priority Severity Auto Resolution
First Event Raised (Error) DFS-N: DFS Namespace Service Failed to Initialize and Is Not Running Medium Critical Yes

Run As Profiles

Name
Default

Monitor Knowledgebase

Summary

This object monitors the initialization of the DFS Namespace service (Distributed File System on Windows Server 2003) and creates an alert if the service fails to initialize.

Causes

The DFS Namespace service failed to initialize. A service can fail to start for many reasons, including:

  • The service could not allocate the required memory.

  • The DFS filter driver is not loaded.

Resolutions

To resolve this issue, use the procedure below that is appropriate to the level of permissions and authority that you have.

  • If you are an Operator (first tier technician) in Operations Manager, start the DFS Namespace service (Distributed File System on Windows Server 2003). To do so, in the Operations console, click the Start DFS Namespace Service task.

  • If you have permission to log on to the affected server (first or second tier technician), log on to the server, close applications to free up memory, and then try restarting the DFS Namespace service. If this does not resolve the problem and there are no critical services or applications that are running successfully on the server, consider restarting the server.

To confirm that the DFS Namespace service is running, in the Operations console, click the Query DFS Namespace Service Status task. This monitor resets to a Healthy state after the service starts.

If these actions do not resolve the problem, it is likely that there are other problems that will require in-depth troubleshooting.

External References
This monitor does not contain any external references.

See Also for DFS Namespaces Monitoring Management Pack


Downloads for DFS Namespaces Monitoring Management Pack

AZURE OPTIMIZATION ASSESSMENT GET STARTED
MIGRATION TO AZURE GET STARTED
SYSTEM CENTER MIGRATION TO AZURE GET STARTED
MIGRATION TO AZURE FOR SQL AND WINDOWS 2008 GET STARTED