Skip to main content

SCVMM Error (2912) when creating a VM from the Self-Service Portal workaround

While using the Self Service Portal on SCVMM, I received this error when creating a virtual machine.

 

Error (2941)
VMM is unable to complete the request. The connection to the agent on machine [SCVMMServer] has been lost.
(Unknown error (0x80072efe))

Recommended Action
Ensure that the WS-Management service and the agent are installed and running and that a firewall is not blocking HTTP traffic.

 

In the job details, the error occurred at step 1.5 Install VM Components.  This issue was reported to Microsoft on October 12, 2008.  The suggested fix on June 26, 2011 does work, but with an issue.  If you were using quotas to help manage the resources your users were consuming, the record of this quota usage will be lost.  The users quota will have those points returned to it as if they are not being used.

 

To prevent the loss of data associated with the host, here is an easy alternative.

 

  • Go to the Hyper-V manager on the host that the deployed VM resides on.
  • Make sure the correct VHD files are attached and that correct virtual network is attached.
  • Start the VM and finish any installation activities from the deployment.
  • Install the integration services if necessary.
  • Properly shut down the VM.
  • Start the VM back up.
  • In the VMM manager console, right click the VM and select Repair.
  • The only option you should get is Retry.  Should Ignore be an option, us it.
  • Let the process finish.  If it errors again, attempt the Repair.  You want it to present to you the option of Ignore. Once you can ignore the errors, your VM will be functional in the VMM console.

 

This procedure is a bit awkward, but it preserves not only the quota points, but all settings and database information associated with the host.

Comments

Popular posts from this blog

Adding a Comment to a GPO with PowerShell

As I'm writing this article, I'm also writing a customization for a PowerShell course I'm teaching next week in Phoenix.  This customization deals with Group Policy and PowerShell.  For those of you who attend my classes may already know this, but I sit their and try to ask the questions to myself that others may ask as I present the material.  I finished up my customization a few hours ago and then I realized that I did not add in how to put a comment on a GPO.  This is a feature that many Group Policy Administrators may not be aware of. This past summer I attended a presentation at TechEd on Group Policy.  One organization in the crowd had over 5,000 Group Policies.  In an environment like that, the comment section can be priceless.  I always like to write in the comment section why I created the policy so I know its purpose next week after I've completed 50 other tasks and can't remember what I did 5 minutes ago. In the Group Policy module for PowerShell V3, th

Return duplicate values from a collection with PowerShell

If you have a collection of objects and you want to remove any duplicate items, it is fairly simple. # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   # Remove the duplicate values. $Set1 | Select-Object -Unique 1 2 3 4 5 6 7 What if you want only the duplicate values and nothing else? # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   #Create a second collection with duplicate values removed. $Set2 = $Set1 | Select-Object -Unique   # Return only the duplicate values. ( Compare-Object -ReferenceObject $Set2 -DifferenceObject $Set1 ) . InputObject | Select-Object – Unique 1 2 This works with objects as well as numbers.  The first command creates a collection with 2 duplicates of both 1 and 2.   The second command creates another collection with the duplicates filtered out.  The Compare-Object cmdlet will first find items that are diffe

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.