A Windows subsystem failed a critical request. RPC Port Mapper was unable to start.

Details
Product: Windows Operating System
Event ID: 3000
Source: portmap
Version: 5.2.3790.1830
Message: A Windows subsystem failed a critical request. RPC Port Mapper was unable to start.
   
Explanation

The NFS protocol uses the RPC Port Mapper to enable NFS clients to discover the ports for various NFS services, such as mount, Network Lock Manager (NLM), and Network Status Manager (NSM).

If the RPC Port Mapper cannot start, Server for NFS will not start and NFS clients will not be able to access Server for NFS file shares.

Cause

Windows may be low on system resources.

   
User Action

Try closing programs and restarting Server for NFS. Click Start and then Control Panel. In Control Panel, double-click Administrative Tools, then click Services. Click Server for NFS. In the Action menu, click Start.

Related:

Drive %1 is nearly full. %2 bytes are available. Please warn users and delete unneeded files.

Details
Product: Windows Operating System
Event ID: 3000
Source: Alerter
Version: 5.0
Symbolic Name: ALERT_Disk_Full
Message: Drive %1 is nearly full. %2 bytes are available. Please warn users and delete unneeded files.
   
Explanation

If the drive becomes too full, programs that need disk space for temporary files will fail.

   
User Action

Warn the users and either ask them to delete unneeded files or tell them that you will delete certain files and that they need to make copies of the files they want to keep.

Related:

The DNS server has encountered numerous run-time events. To determine the initial cause of these run-time events, examine the DNS server event log entries that precede this event. To prevent the DNS server from filling the event log too quickly, subsequent events with Event IDs higher than 3000 will be suppressed until events are no longer being generated at a high rate.

Details
Product: Windows Operating System
Event ID: 3000
Source: DNS
Version: 5.2
Symbolic Name: DNS_EVENT_START_LOG_SUPPRESS
Message: The DNS server has encountered numerous run-time events. To determine the initial cause of these run-time events, examine the DNS server event log entries that precede this event. To prevent the DNS server from filling the event log too quickly, subsequent events with Event IDs higher than 3000 will be suppressed until events are no longer being generated at a high rate.
   
Explanation

This event occurs when numerous other events are logged
and does not have a specific single cause.

   
User Action

Examine the DNS server event log entries that precede this event and troubleshoot those events.

For more information about DNS and DNS troubleshooting procedures, see Domain Name System(DNS)Center.

Related: