Server for NFS could not register the Network Status Manager (NSM) protocol on the specified port. Server for NFS did not start. Without the NSM protocol, NFS clients would not be able to reclaim files locks on this server, if either the server of client's service is disrupted. Verify that no other programs are registered on the specified NSM protocol port, or use the Nfsadmin command-line tool to specify a different port.
Server for NFS could not read the character translation file . Server for NFS cannot translate characters in file names. ...
Server for NFS could not register the mount protocol on the specified port. Server for NFS did not start. Without the mount ...
Server for NFS could not register the Network File System (NFS) protocol on the specified port (%6). Server for NFS is will ...
Server for NFS could not register the Network Lock Manager (NLM) protocol on the specified port. Server for NFS did not 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 ...