vim.fault.HttpFault when sorting VMs in vSphere Client after 5.1 upgrade
Hello. I have recently completed a upgrade of vCenter from 5.0 > 5.1. I ran into some common teething problems with SSO but things look ok at the moment. I do have one problem that I'd really like...
View ArticleRe: vim.fault.HttpFault when sorting VMs in vSphere Client after 5.1 upgrade
Port 10443 is the vCenter 5.x Inventory Service HTTPS port. Make sure the vCenter Inventory Service is running and shows a healthy state in the vCenter Server Status health section of the vSphere...
View ArticleRe: vim.fault.HttpFault when sorting VMs in vSphere Client after 5.1 upgrade
Thanks for the response. The vCenter Inventory Service is running and shows healthy in the vCenter Service Status. All of the vCenter components are installed on the same server (using vCenter Server...
View ArticleRe: vim.fault.HttpFault when sorting VMs in vSphere Client after 5.1 upgrade
Are you able to sort the VMs by name/state and not by the other columns or even the sorting by name doesn't work? RegardsGirish
View ArticleRe: vim.fault.HttpFault when sorting VMs in vSphere Client after 5.1 upgrade
Hi Girish. I am unable to sort by anything - name, power state, OS. It's the same whether I am looking at VMs in the Hosts & Clusters view or the VMs & Templates view.
View ArticleRe: vim.fault.HttpFault when sorting VMs in vSphere Client after 5.1 upgrade
No, that message is perfectly normal as the server expects a more specific HTTP request of your vSphere Client instead of a simple browser GET request. I'm not sure what could be causing this error...
View ArticleRe: vim.fault.HttpFault when sorting VMs in vSphere Client after 5.1 upgrade
Unhelpfully, this problem resolved itself - no service restarts, no system reboots: it just worked the following day. I have given it some time to see if I could reproduce but haven't run into the...
View ArticleRe: vim.fault.HttpFault when sorting VMs in vSphere Client after 5.1 upgrade
Infuriatingly, the problem has returned!!! Nothing has changed on vCenter - no reboots or upgrades. There seems to be no logic to the problem. I am very much regretting this upgrade...
View ArticleRe: vim.fault.HttpFault when sorting VMs in vSphere Client after 5.1 upgrade
Does anyone have an answer for this. I have had this same issue on my vCenter Appliance since I upgraded to 5.1 and am still having the issue even after upgrading to 5.1.0 1b on Friday. Thoughts?...
View ArticleRe: vim.fault.HttpFault when sorting VMs in vSphere Client after 5.1 upgrade
I'm also having this issue, but I noticed that I CAN sort if all the VM's fit in the view window. If the scroll bar is there I get that same error. I thought at first it was just when I was sorting all...
View ArticleRe: vim.fault.HttpFault when sorting VMs in vSphere Client after 5.1 upgrade
I am also having the same problem. And I confirmed on the scroll bar behavior Phl11 talked about. I tested the scroll bar by increase and reduce the windows size. If the scroll bar isn't there, the...
View ArticleRe: vim.fault.HttpFault when sorting VMs in vSphere Client after 5.1 upgrade
I also found the sorting works when I an on the VMware vCenter itself... Andy
View ArticleRe: vim.fault.HttpFault when sorting VMs in vSphere Client after 5.1 upgrade
My apologies for not updating this post - I completely forgot I ended up placing a call with VMware and the resolution in my instance was to add my domain user account directly to the vCenter...
View ArticleRe: vim.fault.HttpFault when sorting VMs in vSphere Client after 5.1 upgrade
Phl11 & adykang,Were you able to resolve your issue when sorting with a scroll bar? I have the same issue and I'm using 5.5 vCenter Server Appliance.
View ArticleRe: vim.fault.HttpFault when sorting VMs in vSphere Client after 5.1 upgrade
Yes. While my active directory user account was in the VMware administrators group, the user account wasn't in the correct OU. Check your "Base DN for Users" and "Base DN for Groups" in your SSO...
View ArticleClik here to view.
Re: vim.fault.HttpFault when sorting VMs in vSphere Client after 5.1 upgrade
I finally resolved my issue. It turns out I used a newer version (v1.0.1) of OpenSSL which exports the key file in a different format. You can tell because the "incorrect" key file contents will have...
View Article