Event Id | 4870 |
Source | Microsoft-Windows-FailoverClustering |
Description | User mode health monitoring has detected that the system is not being responsive. The Failover cluster virtual adapter has lost contact with the '%1' process with a process ID '%2', for '%3' seconds. Recovery action will be taken. |
Event Information | According to Microsoft : Cause : This event is logged when User mode health monitoring has detected that the system is not being responsive. Resolution : Discover process that is draining resources or otherwise slowing down the node The health monitoring process that is part of failover clustering has detected that system responsiveness has slowed. If you do not currently have Event Viewer open, see "Opening Event Viewer and viewing events related to failover clustering." Using the information from the event, review the applications and services running on the node to discover which process is draining resources or otherwise slowing down the node. You can use one or more of the following methods: Use Task Manager. For more information, see "Using Task Manager to work with applications or services consuming large amounts of memory." Generate a System Diagnostics Report, which will present system information collected for 60 seconds. This may take several minutes if the system is critically low on resources. For more information, see "Generating a System Diagnostics Report." Use Resource Monitor to determine, in real-time, how many system resources a service or application is utilizing. This may take several minutes if the system is critically low on resources. To perform the following procedures, you must be a member of the local Administrators group on each clustered server, or you must have been delegated the equivalent authority. Using Task Manager to work with applications or services consuming large amounts of memory To use Task Manager to work with applications or services consuming large amounts of memory:
If Windows cannot close the application normally, you will be prompted to end the process. Ending a process can cause data loss. Generating a System Diagnostics Report To generate a System Diagnostics Report:
To start Resource Monitor: Important : Resource Monitor stops collecting information while a System Diagnostics Report is being generated. To start collecting information after a System Diagnostics Report has completed, in Monitor , click Start .
To open Event Viewer and view events related to failover clustering:
Use Performance Monitor to confirm that system resources are not being drained and the node is functioning normally. |
Reference Links | Event ID 4870 from Microsoft-Windows-FailoverClustering |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.