Solution to "Unable to extract requested data" in vCenter Server 6.7 HTML 5 client
In the HTML 5 client of vCenter Server 6.7, when browsing "Monitoring→vSAN→Virtual Objects", "Unable to extract requested data. Please check vSphere Client logs for details. Check vSphere Client logs for details).", as shown in Figure 1.
Figure 1 Error 1
If you click "Host", a similar error appears in "Monitoring→vSAN→Performance".
For this issue, VMware has introduced KB74731 (link address is https://kb.vmware.com/s/article/74731?lang=zh_CN) and said that this issue has been resolved in ESXi 6.7 Update 3a. But after upgrading ESXi and vCenter to Update 3a or later, the problem remains.
The vCenter Server 6.7 in this environment is upgraded from 6.5 U2. vCenter Server 6.5 U2 has a bug. After the certificate expires and the certificate is renewed, vCenter Server cannot log in or prompts that the password is incorrect. At this time, you need to go to https://kb.vmware.com/s/article/76719?lang= en_US&queryTerm=76719 Download a script named fixsts.sh, upload it to the vCenter Server Appliance to execute the script, and replace the STS (Security Token Service) certificate to solve the problem of incorrect passwords.
After replacing the STS certificate, the computer's SSL certificate may not match the SSL certificate used for service registration used by the vCenter Server node URI, and the error in Figure 1 will appear. For this problem, you can use the check-trust-anchors -cml script to fix.
Use ssh to log in to vCenter Server, use vi check-trust-anchors in the /tmp folder to edit the new file, and then on the Windows computer, open the downloaded check-trust-anchors file with "Notepad", copy all the content, Press the insert button in vi, paste the copied content, press the ESC key, enter: wq to save and exit.
Then execute chmode +x check-trust-anchors
./ check-trust-anchors -cmlf
Repair the certificate.
Figure 2 Repair SSL certificate
Check the string behind SHA1 Fingerprint=, you can see that there is a fingerprint that does not match, this example is B9:77:05:11:00:88:72:B1:E5:CC:18:42:8E:39:01 :D6:E2:B7:91:94
Enter Y, SSO account, password below, and enter the fingerprint of the trust anchor to be updated
Proceed with updating trust anchors? [Y/N]: y
Enter SSO admin [[email protected]]: [email protected]
Enter password for [email protected]:
Enter fingerprint of trust anchor(s) to update: B9:77:05:11:00:88:72:B1:E5:CC:18:42:8E:39:01:D6:E2:B7:91:94
Enter the FQDN of the node to update: VC name or IP
The problem can be resolved after the update is complete, as shown in Figure 3.
Figure 3 can view data