Cluster Baseline Compliance scan fails immediately with the error: "There are errors during the scan operation. Check the events and log files for details."

Products

• VMware vCenter Server

Issue/Introduction

When doing cluster baseline compliance scan, it fails immediately with the error: "There are errors during the scan operation. Check the events and log files for details." for one or more of the Hosts in the cluster, but not necessarily all Hosts.

Review of the vmware-vum-server log on the vCenter Server confirms the scan task failure. The log records an inability to acquire a write lock for the affected Host, throwing an integrity.fault.ScanFailure fault.

The vmware-vum-server log records the following sequence during the failed scan task execution:

2026-05-11T09:50:33.776Z info vmware-vum-server[2933065] [Originator@6876 sub=VciScanTask.ScanTask{1785}] [vciTaskBase 689] Task started...
2026-05-11T09:50:33.776Z error vmware-vum-server[2933065] [Originator@6876 sub=InventoryTree] [InventoryTree 265] [AcquireWriteLock] Node host-#### is in bad state.
2026-05-11T09:50:33.777Z warning vmware-vum-server[2933065] [Originator@6876 sub=InventoryTree] [InventoryTree 2178] Failed to write lock host-####; Node host-#### is in a bad state
.
.
.
2026-05-11T09:50:33.793Z info vmware-vum-server[2933065] [Originator@6876 sub=VciScanTask.ScanTask{1785}] [vciTaskBase 1496] SerializeToVimFault fault:
--> (integrity.fault.ScanFailure) {
-->    faultCause = (vmodl.MethodFault) null,
-->    faultMessage = <unset>,
-->    reason = <unset>
-->    msg = "Failed to lock entities"

Cause

The VMware Update Manager (VUM) service entered an inconsistent internal state regarding the specific Host object referenced in the error message, preventing it from acquiring the necessary write lock to perform the scan operation.

 

Resolution

Restart the VMware Update Manager service on the vCenter Server appliance using the following command:

service-control --restart vmware-updatemgr