Failed to install the VAIO filter

Article ID: 81397

Article Type: Troubleshooting

Last Modified:

If there is a mismatch between the vpxd-extension certificate stored in VECS and the certificate information stored in vCenter Server Database for EAM extension, the VAIO filter installation fails.

Symptoms

The VAIO filter installation fails, and the following error appears in the log:

BlrdvInstall.log 15420 5908 07/19 17:56:14 254709 Installing IO filter cvtblrh 15420 5908 07/19 17:56:15 254709 Failed to install IO filter http://<webconsole fqdn>:80/webconsole/downloads/VAIO/cvtblrh-<version#>/<esx version#>/offline-bundle.zip on cluster abc-HA, Error:[The operation is not allowed in the current state.] 15420 5908 07/19 17:56:15 254709 CBlrDrvInstall::Install(460) - Failed to install Head IO filter. Host:[abc-VCENTER.abc.com.tw] Err:[0xFFFFFFFF:{BlrVSOperation::InstallIOFilter(751)/Int.-1.0xFFFFFFFF-Couldn't install Head IO filter}]

Causes

The VAIO filter installation fails because the certificate in VECS does not match with the certificate in vCenter Server Database.

Resolution

  1. Run curl on the vib URL using the following command:

curl <vib URL>

Example command: curl http://<webconsole fqdn>:80/webconsole/downloads/VAIO/cvtblrh-<version#>/<esx version#>/offline-bundle.zip

2. Verify the vpxd log for the following EAM error:

2023-07-19T17:56:14.966+08:00 error vpxd[04955] [Originator@6876 sub=Iofilter opID=75941fcf] Received EAM runtime fault: N3Eam5Fault24EamServiceNotInitialized9ExceptionE(Fault cause: eam.fault.EamServiceNotInitialized --> )

  1. If curl is running, verify whether the EAM service is running using the following command:

service-control --status eam

  1. If EAM service is running, verify the EAM log for the following error:

2023-07-20T09:59:39.514+08:00 | ERROR | vim-monitor | VcConnection.java | 213 | Failed to login to vCenter as extension. vCenter has probably not loaded the EAM extension.xml yet.: Cannot complete login due to an incorrect user name or password.2023-07-20T09:59:39.514+08:00 |  WARN | vim-monitor | VcListener.java | 111 | Trying to recover from error(vim.fault.InvalidLogin) {   faultCause = null,   faultMessage = null} at sun.reflect.GeneratedConstructorAccessor71.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at java.lang.Class.newInstance(Class.java:442) at com.vmware.vim.vmomi.core.types.impl.ComplexTypeImpl.newInstance(ComplexTypeImpl.java:174) at com.vmware.vim.vmomi.core.types.impl.DefaultDataObjectFactory.newDataObject(DefaultDataObjectFactory.java:25) at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.ComplexStackContext.<init>(ComplexStackContext.java:30) at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl$UnmarshallSoapFaultContext.parse(UnmarshallerImpl.java:150) at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl$UnmarshallSoapFaultContext.unmarshall(UnmarshallerImpl.java:101) at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl.unmarshalSoapFault(UnmarshallerImpl.java:88) at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl.unmarshalSoapFault(UnmarshallerImpl.java:83) at com.vmware.vim.vmomi.client.common.impl.SoapFaultStackContext.setValue(SoapFaultStackContext.java:40) at com.vmware.vim.vmomi.client.common.impl.ResponseUnmarshaller.processNextElement(ResponseUnmarshaller.java:127) at com.vmware.vim.vmomi.client.common.impl.ResponseUnmarshaller.unmarshal(ResponseUnmarshaller.java:70) at com.vmware.vim.vmomi.client.common.impl.ResponseImpl.unmarshalResponse(ResponseImpl.java:274) at com.vmware.vim.vmomi.client.common.impl.ResponseImpl.setResponse(ResponseImpl.java:230) at com.vmware.vim.vmomi.client.http.impl.HttpExchangeBase.parseResponse(HttpExchangeBase.java:156) at com.vmware.vim.vmomi.client.http.impl.HttpExchange.run(HttpExchange.java:53) at com.vmware.vim.vmomi.client.http.impl.HttpProtocolBindingBase.executeRunnable(HttpProtocolBindingBase.java:226) at com.vmware.vim.vmomi.client.http.impl.HttpProtocolBindingImpl.send(HttpProtocolBindingImpl.java:106) at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$CallExecutor.sendCall(MethodInvocationHandlerImpl.java:629) at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$CallExecutor.executeCall(MethodInvocationHandlerImpl.java:610) at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.completeCall(MethodInvocationHandlerImpl.java:360) at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.invokeOperation(MethodInvocationHandlerImpl.java:311) at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.invoke(MethodInvocationHandlerImpl.java:184) at com.sun.proxy.$Proxy36.loginExtensionByCertificate(Unknown Source) at com.vmware.eam.vc.VcConnection.connectEam(VcConnection.java:204) at com.vmware.eam.vc.VcListener.main(VcListener.java:126) at com.vmware.eam.vc.VcListener.call(VcListener.java:109) at com.vmware.eam.vc.VcListener.call(VcListener.java:55) at com.vmware.eam.async.impl.AuditedJob.call(AuditedJob.java:48) at com.vmware.eam.async.impl.FutureRunnable.run(FutureRunnable.java:53) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)2023-07-20T09:59:39.514+08:00 |  INFO | vim-monitor | VcListener.java | 118 | Retrying in 10 sec.2023-07-20T09:59:49.515+08:00 |  WARN | vim-monitor | HttpConfigurationCompilerBase.java | 92 | Shutting down the connection monitor.2023-07-20T09:59:49.515+08:00 |  WARN | VLSI-client-connection-monitor-4192 | HttpConfigurationCompilerBase.java | 84 | Interrupted, no more connection pool cleanups will be performed.

  1. If you find the error produced in step 4, follow the steps in the VMware KB article 2112577, and then reinstall the VAIO filter.
1 Commvault Way, Tinton Falls, NJ 07724 Sitemap | Legal Notices | Trademarks | Privacy Policy
Copyright © 2025 Commvault | All Rights Reserved.