After Windows VCenter Migration from 6.5 to VCSA 6.7 Web Client Error 1069

We did a really nice migration from a Windows VCenter 6.5 U3 to a VCSA 6.7 U1 in the last week. In the first place everything seems to work fine and the vast majority of functions is working fine.

Unless there is a slight error concerning the Web Client (Flash) and we can´t get any clue. every time we authenticate to the Web Client we get the internal error #1069 and if we do not want to reload the web client it is working as designed.

Our first clue was we have a damaged plugin or incompatible one, and we have to remove it:

Here we are with the mob webinterface:

extensionList["com.vmware.vim.sms"] Extension

extensionList["com.vmware.vim.vsm"] Extension

extensionList["VirtualCenter"] Extension

extensionList[""] Extension

extensionList["com.vmware.vim.sps"] Extension


extensionList["com.vmware.vim.vcha"] Extension

extensionList["hostdiag"] Extension

extensionList[""] Extension

extensionList["com.netapp.aegis"] Extension

extensionList["com.netapp.scvm.webclient"] Extension

extensionList[""] Extension

extensionList["com.vmware.imagebuilder"] Extension

extensionList["com.vmware.ovf"] Extension

extensionList["com.vmware.vcenter.iso"] Extension

extensionList["com.vmware.vcIntegrity"] Extension

extensionList["com.vmware.vdc"] Extension

extensionList["com.vmware.vim.eam"] Extension

extensionList["com.vmware.vmcam"] Extension

extensionList[""] Extension

extensionList["com.vmware.vcenter.vmtx"] Extension

extensionList["com.vmware.vsan.dp"] Extension

extensionList["com.vmware.vsphere.client.h5vsan"] Extension

extensionList["com.vmware.rbd"] Extension


if the error message is displayed then following is in the vsphere_client_virgo.log:

[ERROR] http-nio-9090-exec-3         70041378 100412 200049 com.vmware.vise.util.logging.LogServiceImpl                       [Flex|AppErrorHandler]Error #1069

ReferenceError: Error #1069

at com.vmware.vsphere.client.views.notifications::HistoricalImportNotifier/getValidStatusCollection()

at com.vmware.vsphere.client.views.notifications::HistoricalImportNotifier/onHistoricalImportStatusDataRetrieved()

at EventFunctor/notifyTarget()

at EventFunctor/onEvent()


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

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



at DataAccessItem/notify()

at DataAccessItem/handleResult()

at DataAccessItem/processResult()



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/


at mx.rpc::AbstractOperation/

at mx.rpc::AbstractInvoker/

at mx.rpc::Responder/result()

at mx.rpc::AsyncRequest/acknowledge()

at NetConnectionMessageResponder/resultHandler()

at mx.messaging::MessageResponder/result()

Does anyone have an idea what is happening here?

0 Kudos
1 Reply

Please check if your Upgrade Path is supported.
VMware Product Interoperability Matrices

Maybe there was something introduced in 6.5 U3 that is not available in 6.7 U1.

Did you already open a SR with VMware Support?

Maybe Upgrading to 6.7 U3 will have some impact on this issue, maybe not.

Best regards


0 Kudos