"Error: the operation is not allowed in the current state" when installing Veeam's I/O filter

Products

• VMware vCenter Server

Issue/Introduction

Symptoms:

• You see an error in vCenter: "Error: the operation is not allowed in the current state"
• Any task related to Veeam such as Create or Remove works fine
• You see errors from Veeam such as: 
  
  
  
  
• You see messages from vpxd.log similar to:

2021-12-28T16:02:52.383Z error vpxd[7FED1B790700] [Originator@6876 sub=Iofilter opID=6b4a23a] iofilter: GetVibInfo: Received EAM runtime fault: eam.fault.EamServiceNotInitialized.
2021-12-28T16:02:52.383Z info vpxd[7FED1B790700] [Originator@6876 sub=vpxLro opID=6b4a23a] [VpxLRO] -- FINISH task-5630948
2021-12-28T16:02:52.383Z info vpxd[7FED1B790700] [Originator@6876 sub=Default opID=6b4a23a] [VpxLRO] -- ERROR task-5630948 -- IoFilterManager -- vim.IoFilterManager.installIoFilter: vim.fault.InvalidS
tate:
--> Result:
--> (vim.fault.InvalidState) {
-->  faultCause = (vmodl.MethodFault) null,
-->  faultMessage = <unset>
-->  msg = ""
--> }
--> Args:
-->
--> Arg vibUrl:
--> "https://VBACK-MAIN.GBB.LOC:33034/dapi/bundle/6.5.0/11.1.94" >> Veeam Backup URL
--> Arg compRes:
--> 'vim.ClusterComputeResource:domain-c93679'

• You see messages from eam.log similar to:

1-12-28T14:41:02.152Z | WARN | VLSI-client-connection-monitor-23155 | HttpConfigurationCompilerBase.java | 81 | Interrupted, no more connection pool cleanups will be performed.

2021-12-28T14:41:02.167Z | INFO | vim-monitor | VcConnection.java | 635 | Connecting to https://VCENTER.GBB.LOC:8089/sdk/vimService via vCenter proxy http://localhost:80

2021-12-28T14:41:06.222Z | ERROR | vim-monitor | VcConnection.java | 210 | 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.

2021-12-28T14:41:06.222Z | WARN | vim-monitor | VcListener.java | 110 | Trying to recover from error

(vim.fault.InvalidLogin) {

  faultCause = null,
  faultMessage = null

}
    at sun.reflect.GeneratedConstructorAccessor68.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)

    atcom.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.im

Resolution

This issue can happen if there is a mismatch between vpxd-extension certificate stored in VECS and the certificate information stored in the vCenter Server Database for EAM extension.

To resolve the issue, follow the knowledgebase article, EAM "Failed to login to vCenter as extension, Cannot complete login due to an incorrect user name or password" after replacing the vCenter Server certificates