Jan 31, 2018 02:22 PM
Jan 31, 2018 06:16 PM
Some common problems would be that the VMware web API is not running on 10.0.0.10, or that the beacon does not have network connectivity to port 443 (HTTPS) on the VMware server.
For troubleshooting, you could try using a web browser running on the beacon to browse to https://10.0.0.10/mob and ensure you do not get a "connection failed" or "404 not found" type response. (You may still get an error browsing to that URL, but you want an error which indicates that a connection was successfully made, and that there seems to be something running there.)
Chris @ Flexera
Feb 01, 2018 09:40 AM
Unfortunately I've tried both of these. The only clue I can gander from the logs is that the Beacon is having issues connecting to https://
/sdk/. The actual REST interface is sitting at https:// /sdk/vim.wsdl. I have no issues connecting to it from the browser level on the beacon itself via HTTPS...
Feb 05, 2018 09:33 AM
You may want to test/troubleshoot using the ESXQuery inventory tool that can be executed manually, please download it from https://flexeracommunity.force.com/customer/articles/en_US/INFO/Additional-Inventory-Tools-for-FlexNet-Manager-Suite
Feb 07, 2018 01:10 PM
Feb 08, 2018 03:06 PM
Feb 13, 2018 10:21 AM
Mar 19, 2018 10:17 AM
Found this conversation in Google and had exactly the same problem. In our case it was caused by Windows and its TLS 1.2 support.
I was able to sort it out for ESXQuery. Unfortunately the Beacon still won't talk to the service but ESXQuery is a good workaround.
On the Beacon open registry key:
Create a DWord entry called DefaultSecureProtocols
- To support TLS 1.1 AND 1.2 assign the following hex value: A00
- To support TLS 1.2 only assign the following hex value: 200
- To support TLS 1.1 only assign the following hex value: 800
Just to be on the safe side I also created the same entry in
We used value A00 and it resolved the probem. Here's a description from Microsoft: https://support.microsoft.com/en-ca/help/4467770/update-to-enable-tls-1-1-and-tls-1-2-as-secure-protocols-on-winhttp
Mar 11, 2020 09:41 AM