Hyper-V VM can't be managed from the Hyper-V Dashboard (4293881)

When attempting to make changes to a Hyper-V virtual machine through Foglight, it failed to complete any of these changes.

• DCOM/WMI configuration has already been completed in the monitored host.
• Credentials have been configured in the Hyper-V Automation Configuration dashboard.
• Network communication between the FMS and the Hyper-V servers has been confirmed.
• These errors were found in the FMS logs:

2018-12-04 11:05:35.174 WARN    [http-exec-N] com.quest.vcontrol2.aputil.handler.interceptor.SimpleExceptionHander - Exception event id: 16779f7b146
com.quest.vcontrol2.aputil.ActionException: Cannot connect to HOSTNAME.
at com.quest.vcontrol2.actionpack.hyperv.ConnectionPool.getConnection(ConnectionPool.java:67)
at com.quest.vcontrol2.actionpack.hyperv.actions.AbstractServerAction.invoke(AbstractServerAction.java:36)
at com.quest.vcontrol2.aputil.handler.interceptor.InvokeActionInterceptor.intercept(InvokeActionInterceptor.java:33)
at com.quest.vcontrol2.aputil.handler.interceptor.DefaultHandlerInterceptorChain.invoke(DefaultHandlerInterceptorChain.java:42)
at com.quest.vcontrol2.aputil.handler.interceptor.InvokeActionHandlerInterceptor.intercept(InvokeActionHandlerInterceptor.java:34)

[...]

Caused by: com.quest.vcontrol2.dcom.DcomException: org.jinterop.dcom.common.JIException: Class not registered. If you are using a DLL/OCX , please make sure it has "DllSurrogate" flag set. Faq A(6) in readme.html. [0x80040154]
at com.quest.vcontrol2.dcom.ServiceConnection.(ServiceConnection.java:71)
at com.quest.vcontrol2.dcom.DcomBaseObject.(DcomBaseObject.java:46)at com.quest.vcontrol2.dcom.impl.MsDCOMFileSystemObject.(MsDCOMFileSystemObject.java:38)
at com.quest.vcontrol2.hypervapi.impl.DcomProvider.(DcomProvider.java:47)at com.quest.vcontrol2.hypervapi.impl.MshvScriptExecutor.(MshvScriptExecutor.java:63)
at com.quest.vcontrol2.hypervapi.impl.MshvServiceImpl.(MshvServiceImpl.java:47)
at com.quest.vcontrol2.actionpack.hyperv.Connection.(Connection.java:28)at com.quest.vcontrol2.actionpack.hyperv.ConnectionPool.getConnection(ConnectionPool.java:65)... 286 moreCaused by: org.jinterop.dcom.common.JIException: Class not registered. If you are using a DLL/OCX , please make sure it has "DllSurrogate" flag set. Faq A(6) in readme.html. [0x80040154]at org.jinterop.dcom.core.JIComServer.init(JIComServer.java:580)at org.jinterop.dcom.core.JIComServer.initialise(JIComServer.java:481)
at org.jinterop.dcom.core.JIComServer.(JIComServer.java:414)at com.quest.vcontrol2.dcom.ServiceConnection.(ServiceConnection.java:60)
... 293 more
Caused by: org.jinterop.dcom.common.JIRuntimeException: Class not registered. If you are using a DLL/OCX , please make sure it has "DllSurrogate" flag set. Faq A(6) in readme.html. [0x80040154]
at org.jinterop.dcom.core.JIRemActivation.read(JIRemActivation.java:192)
at ndr.NdrObject.decode(NdrObject.java:36)
at rpc.ConnectionOrientedEndpoint.call(ConnectionOrientedEndpoint.java:137)
at rpc.Stub.call(Stub.java:113)
at org.jinterop.dcom.core.JIComServer.init(JIComServer.java:568)
... 296 more

ActionPack for Hyper-V uses DCOM to perform these actions, but a known issue (APMSHV-338) causes the actions to fail if the Hyper-V agents have been collecting using WinRM.

1. Setup Hyper-V agents to use DCOM communication.
2. Make sure the connection is successful.
3. Test an automation action like Restart VM or Edit.
4. After confirming automation actions are completed successfully, revert connection method from DCOM to WinRM. Automation actions should still be successful after this change.

This issue is planned to be addressed by changing the actions from being executed from the FMS to being executed by the Hyper-V agent in the FglAM. This is being tracked as APMSHV-339.