Error: "query execution timed out because of a back-end property-provider" when adding a datastore within vCenter
searchcancel
Error: "query execution timed out because of a back-end property-provider" when adding a datastore within vCenter
book
Article ID: 324326
calendar_today
Updated On: 01-30-2025
Products
VMware vCenter ServerVMware vSphere ESXi
Issue/Introduction
When adding a new datastore from the vCenter Client, the following error occurs and the UI fails to show available LUNs:
The query execution timed out because of a back-end property-provider 'com.vmware.vsphere.client.storage.impl.DatastorePropertyProvider' which took more than 120 seconds
There are a large amount of unresolved unmounted datastores or snapshot LUNs.
Cause
This is a known behavior.
When querying a list of unresolved VMFS volumes and snapshot LUNs from vCenter, ESXi host performs additional filesystem liveness check for all unresolved volumes. This liveness check takes at least 16 seconds per volume. When there are a large number of unresolved volumes, the query does not complete within the timeout of the dataservice at on the web client side and fails to show the volumes.
Resolution
Option 1: Disabling the filesystem liveness check on the ESXi host side:
Log in directly to the ESXi host Client
Navigate to the host's Advanced System Settings
Change VMFS.UnresolvedVolumeLiveCheck to FALSE
Save changes.
or
Log in to ESXi host as root via console or SSH.
Edit /etc/vmware/hostd/config.xml and add the following parameter under plugins/hostsvc/storage node.