When attempting to configure or validate VMware hosts in Cisco Packaged Contact Center Enterprise (PCCE), the operation fails with a generic error in the user interface: "Unable to connect to host(s)."
Cisco Application Log: The application crashes with an XML parsing error, indicating it received an unexpected response format: java.rmi.RemoteException: VI SDK invoke exception:org.dom4j.DocumentException: Error on line 1 of document : Content is not allowed in prolog.
ESXi Host Log (envoy-access.log): The ESXi host immediately rejects the incoming request with a protocol error: HTTP/1.1 400 http1.codec_error DPE 0 11 0 - - [IP_Address] ...
ESXi Host Log (hostd.log): Basic authentication appears successful (HTTP 200), but subsequent complex tasks (e.g., VMConfigValidator) fail.
ESXi 8.0.1
ESXi 8.0.2
Cisco Contact Center Enterprise (CCE) Version 12.6
This issue is caused by a software incompatibility between the legacy VMware SDK used by Cisco PCCE 12.6 and the security hardening introduced in ESXi 8.0 Update 1.
Legacy Library: The Cisco application uses an older version of the vijava library. This library sends SOAP API requests containing an empty soapAction header, which was permitted in older ESXi versions.
Strict Enforcement: ESXi 8.0 U1 introduced a stricter Envoy reverse proxy to handle web requests. Envoy enforces RFC 7230 (HTTP/1.1) standards and classifies empty soapAction headers as a Protocol Violation.
The Failure: Envoy rejects the request with an HTTP 400 error. The Cisco application expects an XML response but receives the HTML error page, causing the Content is not allowed in prolog exception.
To resolve this issue, the Cisco application must be updated to use a modern VMware SDK that complies with HTTP/1.1 standards.
Open a support case with Cisco TAC.
checking the ESXi release notes will show when a new version of Envoy have been introduced - (OS hardening)