TOTALLY agreed !!
What are vmware doing ??? So many hardly tested BETA-LIKE product being released ?
Last version (5.1 was the fastest ever since its release) but now it's back to being even slower than the initial release.
It also has continual drop-outs and even stops responding completely.
I have tested everything else on my network and nothing has changed except the new VCSA.
Sadly I have to use this to get advanced features enabled when importing OVF.
What a silly move to drop development for the Windows C# client which most of the known world of admins use and oh boy why even bother with FLASH !
This web-client and SSO is nothing but a pain in the butt and makes admin and management such a pain.
For the die hard trouble-shooter who have the time .. the build info is :
| Vendor: | VMware Inc. |
| Appliance Name: | VMware vCenter Server Appliance |
| Appliance Version: | 5.5.0.10000 Build 1624811 |
And that took >5 mins to get
Have tried all 3 major IE, Firefox,Chrome.... gave up waiting for chrome eventually :-(
Oh and just for the record ...how do you manage a vcenter properly when the web-client is dead ?
And ..wait for it ... how do you intend to manage individual esxi hosts when you dump the Windows client ? Oh no not command line again ?
So here's the quick fix .. which is not so quick because it means back to windows ..
Install Windows (or clone it .. but how without vcenter ...PFFT ?)
Install vcenter on it (yes we are going back to the roots)
(lots of issues in 5.1 with this like forgetting to add web-client to simple install - but don't worry who cares about wasting clients time)
use windows vcenter instead of VCSA.
If anyone can shed some (non-silver) light here I would appreciate it
In the dark
Dina
PS .. here's and error message too (this happens infrequently)
Error Stack
---------------------
TypeError: Error #1009
at com.vmware.vsphere.client.views.navigator.tree::NavTreeMediator/notifyErrorIfAny()
at com.vmware.vsphere.client.views.navigator.tree::NavTreeMediator/onGetNodeReturn()
at EventFunctor/notifyTarget()
at EventFunctor/onEvent()
at flash.events::EventDispatcher/dispatchEvent()
at com.vmware.frinje::EventBus/dispatchEvent()
at com.vmware.frinje::CallbackUtil$/dispatchResponse()
at com.vmware.frinje::CallbackUtil$/dispatchResponseUsingRequestContext()
at com.vmware.vsphere.client.utils.navigator::EventResponseUtils$/returnError()
at com.vmware.vsphere.client.model.navigator::InventoryData/respondWithErrorToOriginator()
at com.vmware.vsphere.client.model.navigator::InventoryData/onDataServiceResponse()
at com.vmware.flexutil.proxies::BaseProxy/notify()
at com.vmware.flexutil.proxies::BaseProxy/fault()
at com.vmware.flexutil.proxies::BaseProxy/onInvocationComplete()
at OperationInvoker/faultResponseForRequest()
at OperationInvoker/fault()
at mx.rpc::AsyncToken/http://www.adobe.com/2006/flex/mx/internal::applyFault()
at mx.rpc.events::FaultEvent/http://www.adobe.com/2006/flex/mx/internal::callTokenResponders()
at mx.rpc::AbstractOperation/http://www.adobe.com/2006/flex/mx/internal::dispatchRpcEvent()
at mx.rpc::AbstractInvoker/http://www.adobe.com/2006/flex/mx/internal::faultHandler()
at mx.rpc::Responder/fault()
at mx.rpc::AsyncRequest/fault()
at mx.messaging::ChannelSet/faultPendingSends()
at mx.messaging::ChannelSet/channelFaultHandler()
at flash.events::EventDispatcher/dispatchEvent()
at mx.messaging::Channel/connectFailed()
at mx.messaging.channels::PollingChannel/connectFailed()
at mx.messaging.channels::AMFChannel/statusHandler()
