vSAN File Service UI disabled on vCenter.

Products

• VMware vSAN

Issue/Introduction

Symptoms:

• vSAN File Service is disabled on vCenter UI>vSAN cluster>Configure>vSAN>Services with below error:

"Unable to extract requested data. Check vSphere Client logs for details".

• Above issues may be observed after upgrading the vCenter to 8.0.x version.

 

Environment

VMware vSAN 8.x

Cause

vCenter File Service UI is disabled and fails to invoke File Service APIs due to a version incompatibility between the 80U3 cluster and the 70GA FSVM. This mixed-mode version effectively blocks all File Service operations through the UI.

Below errors are seen on /var/run/log/vsan.mgmt.log,

2025-09-06T10:02:35.456+10:00 ERROR vsan-mgmt[824480] [VsanHealthUtil::wrapper opID=noOpId] Failed to run API QueryFileSharesInternal
Traceback (most recent call last):
  File "bora/vsan/health/esx/pyMo/VsanHealthUtil.py", line 3668, in wrapper
  File "bora/vsan/fileservice/vpxd/VsanClusterFileServiceSystemImpl.py", line 1941, in QueryFileSharesInternal
  File "bora/vsan/fileservice/vpxd/VsanClusterFileServiceSystemImpl.py", line 1967, in _queryFileSharesImpl
  File "bora/vsan/fileservice/vpxd/VsanClusterFileServiceSystemImpl.py", line 1957, in _ValidateQuerySpec
PyCppVmomi.vmodl.fault.InvalidArgument: (vmodl.fault.InvalidArgument) {
  faultMessage = (vmodl.LocalizableMessage) [
    (vmodl.LocalizableMessage) {
      key = 'com.vmware.vsan.fileservice.fault.queryconfig',
      message = 'query with managedBy, protocols, properties or pageNumber can only be supported when fileservice upgraded to 7.0 Update 1 completely'
   }
 invalidProperty = 'querySpec'
2025-09-06T10:02:35.457+10:00 INFO vsan-mgmt[824480] [VsanHealthUtil::wrapper opID=noOpId] Start running API QueryFileSharesInternal

Resolution

FSVM needs to be upgraded to latest 8.0.3 version from vSAN Managed Object Browser (MOB). 

Please contact Broadcom Support for further assistance.