Server for NFS encountered an error condition when checking for the presence of Failover Clustering (%1) and will continue to operate but in a non-clustered configuration only. To re-detect Failover Clustering and allow Server for NFS to operate in a clustered configuration, Server for NFS should be restarted using either the "Services for Network File System (NFS)" administrative tool or "nfsadmin server stop && nfsadmin server start".
Server for NFS could not register the Network Status Manager (NSM) protocol on the specified port. Server for NFS did not ...
Server for NFS could not register with RPC Port Mapper on all requested port/protocol combinations. Server for NFS will attempt ...
Server for NFS could not register with RPC Port Mapper. Server for NFS did not start. Network File System (NFS) clients discover ...
Server for NFS detected a low disk space condition and has stopped recording audits. Without audit logging, users will still ...
Server for NFS encountered an error condition when checking for the presence of Failover Clustering (%1) and will continue ...
Server for NFS encountered an error while querying User Name Mapping. At least one user is not mapped. Users who are not ...
Server for NFS failed while listening for update notification events. Windows may be low on system resources. Try increasing ...
Server for NFS is not configured for either Active Directory Lookup or User Name Mapping. Without either Active Directory ...
Server for NFS was not able to fit all the information from an audit into one audit entry. The next audit entry will be truncated. ...