Skip to main content
NetApp Knowledge Base

Windows Server VM goes into unresponsive state

Views:
84
Visibility:
Public
Votes:
0
Category:
netapp-hci
Specialty:
virt
Last Updated:

Applies to

  • NetApp HCI
  • Microsoft Windows Server
  • VMware ESXi

Issue

A VM running Microsoft Windows Server goes into an unresponsive state.

The VM's vmware.log within the ESXi host logs show errors such as:

024-06-21T11:28:46.798Z In(05) vmx - GuestRpcSendTimedOut: message to toolbox timed out.
2024-06-21T11:28:46.799Z In(05) vmx - Tools: [AppStatus] Last heartbeat value 5120557 (last received 7s ago)
2024-06-21T11:28:46.799Z In(05) vmx - TOOLS: appName=toolbox, oldStatus=1, status=2, guestInitiated=0.
2024-06-21T11:29:06.800Z In(05) vmx - GuestRpcSendTimedOut: message to toolbox timed out.
2024-06-21T11:29:06.800Z In(05) vmx - GuestRpc: app toolbox's second ping timeout; assuming app is down
2024-06-21T11:29:06.800Z In(05) vmx - Tools: [AppStatus] Last heartbeat value 5120557 (last received 27

 

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.