vCenter vSAN Services UI fails to load with error "Unable to extract requested data" in environments with high storage policy counts

Products

• VMware vCenter Server

Issue/Introduction

When navigating to the vSAN > Services section of a cluster in the vSphere Client, the following symptoms occur:

• vSAN Skyline Health shows 'vCenter and all hosts are connected to Key Management Servers' as Red or Warning.
• KMS connection status in vCenter UI flaps between Connected and Retrieving.
• Recurring 'Host Requires Encryption Mode Enabled' alarms on multiple clusters.
• Log analysis or manual connectivity checks show timeouts on Port 5696.
• The UI fails to load or displays the error: "Unable to extract requested data. Check vSphere client logs for details."
• The browser console may report: net::ERR_INSUFFICIENT_RESOURCES.
• The vsan-plugin.log (located at /var/log/vmware/vsphere-ui/logs/) contains a stack trace similar to:
  

  [YYYY-MM-DDT##:##:##.###Z][ERROR][8.0.203.10000:468043958][urn:vmomi:ClusterComputeResource:domain-##:cd64d189-77a3-41b8-b41a-############][com.vmware.vsan.client.h5vsanui.cluster.configure.vsan.generalConfig] ["[GLOBAL]",{"name":"TypeError","stack":"TypeError: Cannot read properties of undefined (reading 'config')\n

Environment

vCenter Server 7.x
vCenter Server 8.x

Cause

• The issue typically appears in environments managed by automated container platforms (e.g., Tanzu, OpenShift) that generate a high volume of storage policies.

• The vSAN UI plugin initiates concurrent API calls to check compliance for all defined storage policies when loading the Services card.

  • If the environment contains a massive number of storage policies (typically exceeding the configuration maximum of 1,024), these concurrent calls exceed the browser's connection limit.
  • The resulting browser-side resource exhaustion causes requests to stall or timeout, leading to the TypeError as the UI attempts to read configuration data from a failed/undefined request object.

Resolution

Clean up Storage Policies

Reduce the total number of storage policies to below the supported limit of 1,024.

1. Identify and delete unneeded or orphaned storage policies.
2. If using automated container deployments, verify the decommissioning workflow ensures that underlying storage policies are systematically deleted when containers/persistent volumes are removed.

Method 2: Adjust Object Repair Timer via CLI

If the UI is blocked and you must urgently change the Object Repair Timer (e.g., for maintenance), perform the following on each ESXi host in the cluster:

1. Log in to the ESXi host via SSH.
2. Run the following command to set the delay (e.g., to 60 minutes):
    
   esxcfg-advcfg -s 60 /VSAN/ClomRepairDelay
   
   Note: The value is in minutes

Additional Information

• Refer: Deleting a Virtual Machine Storage Policy
• Refer VMware Configuration Maximums to know the maximum number of virtual machine storage policies that needs to be configured. 

Note: Storage policies should be reused across multiple objects. Managing settings through a shared policy makes it easy to identify intent via a descriptive name and allows you to update settings for all linked objects simultaneously.