ALL:
I'm receiving two errors consistently in my VMM 2012 instance. I have searched the web with no luck so I am posting here with hopes of some answers! Any assistance would be greatly appreciated.
Here is a review of our environment:
2 Node Hyper-V 2008 R2 SP1 Cluster
Fully patched (including recommended hotfixes)
Storage is connected via fiber to NETAPP SAN
VMM 2012 and SQL2008 R2 SP1 each have their own vm running in the cluster
Refresh virtual machine properties:
I get the following error message constantly from both of of my Hyper-V Nodes.
Error (2916)
VMM is unable to complete the request. The connection to the agent denprdhvsc02.blah.com was lost.
Unknown error (0x80338126)
Recommended Action
Ensure that the WS-Management service and the agent are installed and running and that a firewall is not blocking HTTPS traffic.
This problem can also be caused by WMI service crash. Ensure that KB 982293 (http://support.microsoft.com/kb/982293) is installed on the machine if it is running Windows Server 2008 R2.
If the error persists, reboot denprdhvsc02.blah.com and then try the operation again.
I have done everything suggested in the recommended action suggestion with no luck. I have also done the following:
1. Veriefed Win RM connectivity on both hosts and the vmm server.
2. Firewall is off on both nodes and on the vmm server
Create virtual machine:
I get the following error when creating a new vm from a template. This is a new error that has recently started. The only thing that has changed in the environment is we added a second CSV volume to the cluster.
Error (2912)
An internal error has occurred trying to contact an agent on the DENPRDSCVMM01.blah.com server: NO_PARAM: NO_PARAM.
Unknown error (0x80072f0d)
Recommended Action
Ensure the agent is installed and running. Ensure the WS-Management service is installed and running, then restart the agent.
Information (11037)
There currently are no network adapters with network optimization available on host denprdhvsc01.blah.com.
I saw on another forum post that someone reinstalled VMM 2012 and that fixed the issue but reinstalling VMM at this point is not an acceptable solution.
Thanks again for your help in advance,
Nate