vCenter Server 8.0.3.0 WSDL Method Resolution Failure

Products

• VMware vCenter Server

Issue/Introduction

VMware vCenter Server 8.0.3.0 reports continuous log spam regarding a WSDL method resolution failure. The specific error observed is: "Unable to resolve WSDL method name PbmQueryAssociatedProfile in vim.version.v8_0_3_0". The request originates from a local service account (e.g., VSPHERE.LOCAL\<REDACTED_USER>) and is associated with storage integration activity involving the session ID <REDACTED_UUID>.

In /var/log/vmware/vpxd/vpxd.log you see flooded with thousands of repetitive WSDL resolution errors:

error vpxd[1025283] [Originator@6876 sub=Req@vim25/8.0.3.0 opID=Run-Http2ServerSession-3] Unable to resolve WSDL method name PbmQueryAssociatedProfile in vim.version.v8_0_3_0 (vim25/8.0.3.0)

Environment

VMware vCenter Server 8.0.3.0

Cause

An external third-party storage integration (such as the HPE Alletra plugin) or custom automation script running under a service account is executing Policy-Based Management (PBM) API commands against the standard vSphere Management API (/sdk) instead of the required PBM endpoint (/pbm or /pbm/sdk).

Resolution

1. Audit all HPE Alletra integrations, including storage plugins, VASA providers, and custom automation scripts utilizing the service account associated with the storage hardware.

2. Verify if a compatibility patch or update is available for the HPE Alletra storage integration that supports vSphere 8.0.3.0 API routing specifications.

3. For custom automation scripts, update the API configuration to target the /pbm or /pbm/sdk endpoint instead of the standard /sdk endpoint.

4. Validate the fix by monitoring vpxd logs to ensure the WSDL resolution errors have ceased.

Additional Information

For details on vSphere API specifications, refer to the Broadcom Developer Portal.