NFS: Server for NFS Driver Startup State Monitor

  • ID:  Microsoft.Windows.FileServices.Service.NFS.6.2.Server.StartupState.Service
  • Description:  This object monitors the Server for NFS driver and generates an alert if the driver does not start, if the alert is enabled for this monitor.
  • Target:  NFS (Windows Server 2012)
  • Enabled:  Yes

Operational States

Name State Description
FirstEventRaised Error  
SecondEventRaised Success  

Alert Details

Monitor State Message Priority Severity Auto Resolution
FirstEventRaised (Error) NFS: Server for NFS Driver Startup State Medium Match Monitor Health Yes

Run As Profiles

Name
Default

Monitor Knowledgebase

Summary

This object monitors the Server for NFS driver and generates an alert if the driver does not start, if the alert is enabled for this monitor.

NFS clients discover NFS servers by querying the RPC Port Mapper service for a remote server. NFS clients can only discover and communicate with a computer running Server for NFS.

Causes

This monitor can enter a Critical health state for one of the following reasons:

  • Windows may be low on system resources and is unable to load the Services for Network File System (NFS) service (>Microsoft-Windows-ServicesForNFS-Server), driver (>Microsoft-Windows-ServicesForNFS-Server) or the RPC Port Mapper service (portmap).

  • An administrator stopped the Server for NFS service.

To determine the underlying cause, inspect the Windows System event log for messages from Source Microsoft-Windows-ServicesForNFS-Server with one of the following event IDs:

  • Event 4004 - Windows failed a request to load the Network File System (NFS) driver.

  • Event 4005 - Service Control Manager failed a request to start Server for NFS.

  • Event 4009 – Server for NFS stopped.

  • Event 4018 - Server for NFS received a failure from the NFS driver during phase 2 initialization.

Event 4018 has several possible causes including the following:

  • Trouble looking up SIDs

  • Trouble acquiring tokens

  • Memory allocation failures

  • Failure to create network endpoints or register with network stack

  • Failure reading the registry

If the health state is unknown, it means that monitoring has not yet begun for this object.

Resolutions

Increase available system resources

To increase available system resources, use the following procedure:

1. At an elevated command prompt on the affected server, type nfsadmin server stop to stop the Server for NFS service.

2. Type net stop portmap to stop the RPC Port Mapper service.

3. Close all programs and stop unnecessary services.

4. Type nfsadmin server start to start the Server for NFS service and the RPC Port Mapper service.

Note The Server for NFS service and the Server for NFS driver are dependent on the RPC Port Mapper service. Stopping the RPC Port Mapper service will also stop the Server for NFS service and its driver.

Verification

To verify Server for NFS startup status, use the following procedure:

1. At an elevated command prompt, type net start.

2. Verify that Server for NFS appears in the list of results.

This monitor automatically resets to a Healthy state after Server for NFS is restarted.

External References
This monitor does not contain any external references.

See Also for Windows Server File & iSCSI Services Management Pack


Downloads for Windows Server File & iSCSI Services 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