September update to VCenter VCSA causes nothing but grief...

[WhiskyTangoFoxt]

I decided to do a fool thing and update VCenter (after backup and snapshot of course), and it has been trouble.

There were no errors or indications of problems with the update, but after rebooting it and logging in, I'm finding it useless. I updated the VMWare update manager on the Windows server that it was connected to as well.

Errors a plenty, and not much to find on them:

Type error 1009 when attempting to do anything with VSAN. Migrating a powered off VM from any another host onto the VSAN cluster results in the 1009 error: Selecting "no" and trying to continue only results in a spinning wheel when verifying VSAN policy.

TypeError: Error #1009

    at com.vmware.vsphere.client.util.vm.migration::SpbmWhatIfProvider/hasVsanCreateCostDataErrors()

    at com.vmware.vsphere.client.util.vm.migration::SpbmWhatIfProvider/processCreateCostResults()

    at com.vmware.vsphere.client.util.vm.migration::SpbmWhatIfProvider/onProvisioningCostRetrieved()

    at EventFunctor/notifyTarget()

    at EventFunctor/onEvent()

    at flash.events::EventDispatcher/dispatchEvent()

    at com.vmware.frinje::EventBus/dispatchEvent()

    at com.vmware.frinje::EventBus/onEvent()

    at flash.events::EventDispatcher/dispatchEvent()

    at com.vmware.data.query.commands::DataRequestCommand/onSingleEntityDataReturn()

    at DataAccessItem/notify()

    at DataAccessItem/handleResult()

    at DataAccessItem/processResult()

    at com.vmware.data.query::DataAccessManager/onDataRetrieved()

    at com.vmware.flexutil.proxies::BaseProxy/notify()

    at com.vmware.flexutil.proxies::BaseProxy/result()

    at com.vmware.flexutil.proxies::BaseProxy/onInvocationComplete()

    at OperationInvoker/resultResponseForRequest()

    at OperationInvoker/result()

    at mx.rpc::AsyncToken/http://www.adobe.com/2006/flex/mx/internal::applyResult()

    at mx.rpc.events::ResultEvent/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::resultHandler()

    at mx.rpc::Responder/result()

    at mx.rpc::AsyncRequest/acknowledge()

    at NetConnectionMessageResponder/resultHandler()

    at mx.messaging::MessageResponder/result()

Type error 1034 when making any changes to a VM: again want to shut down the web client, but clicking on "no" to shut it down allows me to continue are "normal":

TypeError: Error #1034

    at com.vmware.vsphere.client.util::PropertyRequest/onRequestReturn()

    at EventFunctor/notifyTarget()

    at EventFunctor/onEvent()

    at flash.events::EventDispatcher/dispatchEvent()

    at com.vmware.frinje::EventBus/dispatchEvent()

    at com.vmware.frinje::EventBus/onEvent()

    at flash.events::EventDispatcher/dispatchEvent()

    at com.vmware.data.query.commands::DataRequestCommand/onSingleEntityDataReturn()

    at DataAccessItem/notify()

    at DataAccessItem/handleResult()

    at DataAccessItem/processResult()

    at com.vmware.data.query::DataAccessManager/onDataRetrieved()

    at com.vmware.flexutil.proxies::BaseProxy/notify()

    at com.vmware.flexutil.proxies::BaseProxy/result()

    at com.vmware.flexutil.proxies::BaseProxy/onInvocationComplete()

    at OperationInvoker/resultResponseForRequest()

    at OperationInvoker/result()

    at mx.rpc::AsyncToken/http://www.adobe.com/2006/flex/mx/internal::applyResult()

    at mx.rpc.events::ResultEvent/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::resultHandler()

    at mx.rpc::Responder/result()

    at mx.rpc::AsyncRequest/acknowledge()

    at NetConnectionMessageResponder/resultHandler()

    at mx.messaging::MessageResponder/result()

I am able to perform the migration fine with the C++ client just fine, so the problem seems to be totally with the web client.

Problem #3 is that VUM is no longer anywhere in the Web client, although it works fine in the C++ app.

Anyone have any ideas? I've tried the removing of the old SerenityDB files, but it hasn't made any difference.

[weda]

I'm using this one .. sorry for having no solution for your problem..

I even can't log into the VCSA webclient after upgrading to U1 (upgrade did not run into errors or warnings).Now I receive a flash based error "An internal error has occurred - Index '0' specified is out of bounds".

.net client works fine!

I tried resolving this by changing the clients, browser and flash versions without any success. Logfiles are clean.

[noc2]

Did you ever figure this out?  Waiting to hear back from vmware support - thus far no good answers.

[Gringo5000]

I ran into this issue today after a fresh install and patch to 6.0.0U1. I finally got it working by rebooting my VM and hypervisor that I accessed VCSA from.

UPDATE:

I've hit the problem again and several hours later after rebooting and connecting from other machines, I'm still unable to log in. Filed a case with VMware, but no response yet.

[Andy_Kay]

I ran into the same problem. After udpating the vcenter from 6.0 to 6.0 U1 i cannot login in the web client with the " index 0..." error.

I opened a ticket at vmware, after uploading the logfiles and deleting the SerenityDB, i had to roll back to the 6.0 version via snapshot.

vmware couldn't say something about this problem.

without the vcenter update we could not udpate the ESXi to 6.0U1a because it is not supported by vmware.

It would be nice, if somebody could post a positive reaction from vmware support.

[de2rfg]

Do you have any web client plugins or extensions installed? Try to disable them. I had a lot 1009 errors after update, but after disabling all of the plugins (Emulex, Fujitsu...) I haven't seem the error again.

[Gringo5001]

When I updated, I had a fresh install of vCenter 6.0.0 with no plugins. When I installed the patch, I started having problems.

[lmoglie]

Hello,

in my case the problem was caused from the Veeam plug-ins.... removed from the Veeam Enterprise Manager and restarted the vsphere web client services, all started to work properly.

Bye

LM