System Center Virtual Machine Manager – Solving the 2912 NO_PARAM error

In some scenarios, a refresh host or configurations to be applied on a Hyper-V host can fail with error 2912 (NO_PARAM). In this Tutorial, we are going to check one possible cause of this issue and work on the resolution of this issue.

Solution


When trying to refresh a host the error 2912 may show up as depicted in the image below. This issue can be caused for a certificate mismatch between the host server and VMM.

image

Checking the server VMM Server…

The first step is to open the Computer certificate store on the VMM Server (Open mmc, add certificates and select computer store), and navigate to Trusted People \ Certificates and from that list of certificates, double click on the one related to the VMM Server (in our example CATORVMM02), click on Details and select Serial Number and make a note of that serial number information.

image

Checking the Hyper-V Host..

The second step is to go to the same location on the Hyper-V host and check if the certificate that we have there matches the information. If they match we are good, however when we have that NO_PARAM error, it is most likely that information is not matching.

image

Solving the issue..

The solution is easy, we just need to re-associate the Hyper-V host on VMM. Logged on Virtual Machine Manager Command Shell run the following cmdlet

$cred = Get-Credential

Get-VMMManagedComputer -ComputerName “<computer-name>” | Register-SCVMMManagedComputer  -Credential $credential

The cmdlet in action can be seen in the image below.

image