This object monitors the initialization of namespace roots by looking for the presence of DfsSvc event 14534 in the System event log. If this object detects the event, it sets the health state of the monitor to Critical, indicating that the namespace is offline and triggers an alert.
If the namespace is a domain-based namespace, it could fail to initialize for the following reasons:
Network connectivity problems are preventing the namespace server from reaching a domain controller.
Changes were made to the DFS namespace directly in Active Directory Domain Services (AD DS) instead of using DFS Management or command-line tools.
If the namespace is a stand-alone namespace, it could fail to initialize if the DFS Namespace service cannot locate the metadata for the namespace in the registry of the server. This can occur because of registry corruption.
Restart the DFS Namespace service. To do so, open a command prompt window on the affected server and then type the following commands:
net stop dfs
net start dfs
If restarting the service does not resolve the issue, the namespace server might not be able to contact a domain controller.
To test communication with AD DS, use the dfsdiag /testdcs command. Confirm that all domain controllers report healthy results.
To verify that this issue is no longer present, use the following procedure:
1. Open a command prompt window and then use the dfsutil root\\<namespace> command (on Windows Server 2003, use the dfsutil root\\<namespace>/view command) to check the state of the namespace.
2. Confirm that the state of the root is OK and that the states of all namespace servers are Online.
3. After you resolve the problem, in the Operations console, reset the health state of this monitor to Healthy.