This rule monitors the initialization of the DFS Namespace service and creates an alert if the service fails to initialize.
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.
To resolve this issue, use the procedure below that is appropriate to the level of permissions and authority that you have.
If you are 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 logon to the affected server (first or second tier technician), logon 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.