Moderator: Tagging a large bunch of forum users and pleading for help isn’t necessary or desirable here, please wait for help from the forum community.
Your comment with the tags has been removed.
please provide more details about your environment. Which version of vSphere/vCenter are you using? Are you using vCenter for Windows or the vCenter appliance? Do you use an external PSC or an embedded one?
As a starting point you can also try to search for your specific error code (com.vmware.vim.vmomi.core.exception.CertificateValidationException) in the VMware Knowledgebase.
What is your vCenter server exact build number? If you are in an earlier version than 6.5b please check this: https://kb.vmware.com/s/article/2148196
Next, check the status of all vCenter's services via the VAMI interface (http://vcsa_IP:5480) and make sure everything is working fine.
Then please tell me did you ever change the default certification of the vCenter server or .... register a new product to the vSphere environment like the NSX? So check the following link about your problem: https://kb.vmware.com/s/article/2109074Please mark my comment as the Correct Answer if this solution resolved your problem
Thank you for the steps to resolve my issues.
- Which version of vSphere/vCenter are you using? vSphere 6.5
- Are you using vCenter for Windows or the vCenter appliance? Yes for windows Server 2016 Data center
- Do you use an external PSC or an embedded one? Embedded with DELL blade server PowerEdge M630 with Vcenter
I am keep on searching.
Thank you so much for your reply and support.
- What is your vCenter server exact build number? - I am using Version 6.5.0 , Build number - 4602587
I have gone through the details of articles and finally with an recomendation, I have updated the Vcenter server and restarted the Server.
Now, Alhamdulillah ..:)
Working fine and able to access the vSphere Web Client.
Thank you so much for all of you comments.
scott28tt Thank you for your advice and i wont tag any one here after, but I needed to figure it out and it was bit urgent, So i tagged some experts like you bro.
Tagging can be entirely appropriate when done for the right reasons - such as if you are already in conversation with someone within a thread, or there is a specific person you KNOW is an expert with a particular problem (eg. LucD in the PowerCLI area, continuum with corruption/recovery issues)
But tagging a large set of people simply to generate a notification to them is not necessary or desirable - the vast majority of us are here voluntarily, no matter how urgent your issue.
Anyways... Thanks for your support