Archive

Posts Tagged ‘2912’

VMM 2012 SP1 Error 2912 when Moving VM

October 3, 2013 2 comments

One of the most common error that I saw in many environment when you try to move VM from one Server to another you get this message

Error (2912)
An internal error has occurred trying to contact an agent on the Server.Domain.Local 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.

After checking SCVMM agent and services are running fine on hosts you have to check BITS related configuration, you can use these steps to adjust the BITS to remove this problem:

  1. On Server.Domain.Local , check if we have installed feature Background Intelligent Transfer Service (BITS) feature.
  2. Open Regedit and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft System Center Virtual Machine Manager Server\Settings
  3. Locate the BITSTcpPort name on the right. It’s data value should be 443
      a. Double click BITSTcpPort in order to modify the data. Make sure the Base is set to ‘Decimal’
      b. Change 443 to 765, or any other number less than 32768. Do not use a port that another protocol uses such as RDP (3389)
      c. Click ‘OK’ to save this value
  4. Restart the ‘Virtual Machine Manager’ and ‘Virtual Machine Manager Agent’ services on the SCVMM server. (On managed hosts simply restart the ‘Virtual Machine Manager Agent’ service’)
  5. Once complete on the SCVMM server and all Hosts you can continue using SCVMM

 

Categories: VMM, VMM2012 Tags:

SCVMM 2012 VM Migration Error 2912

February 10, 2013 4 comments

Symptom:

When you move VMs between different Windows 2008 R2 SP1 hosts you get this error

Error (2912)
An internal error has occurred trying to contact an agent on the Hostname 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.

Cause:

1- VMM agent is not running

2- WMI or WinRM services are not running

3- VMM BITS port configuration need adjustment

 

Resolution:

Check VMM agent, WinRM, WMI Services and start if anyone stopped

  1. On Hyper-V Server, check if we have installed feature Background Intelligent Transfer Service (BITS) feature.
  2. Open Regedit and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft System Center Virtual Machine Manager Server\Settings
  3. Locate the BITSTcpPort name on the right. It’s data value should be 443
      a. Double click BITSTcpPort in order to modify the data. Make sure the Base is set to ‘Decimal’
      b. Change 443 to 765, or any other number less than 32768. Do not use a port that another protocol uses such as RDP (3389)
      c. Click ‘OK’ to save this value
  4. Restart the ‘Virtual Machine Manager’ and ‘Virtual Machine Manager Agent’ services on the SCVMM server. (On managed hosts simply restart the ‘Virtual Machine Manager Agent’ service’)
  5. Once complete on the SCVMM server and all Hosts you can continue using SCVMM

NOTE: Changing the BITS port for SCVMM does not affect BITS ports used by other applications or Windows itself.

Categories: VMM, VMM2012 Tags: ,

P2V fails with Error 2912 0x80072F0C with System Center Virtual Machine Manager 2008

August 23, 2010 Leave a comment

Toolbox2When using System Center Virtual Machine Manager (SCVMM) to perform a Physical to Virtual (P2V) conversion, the job may fail at 60% with the following error:

Error (2912)
An internal error has occurred trying to contact an agent on the vmmserver.contoso.com server.

Recommended Action
Ensure the agent is installed and running. Ensure the WS-Management service is installed and running, then restart the agent.

Cause:

During the ‘Make operating system virtualizable’ step, files are copied from the destination host (the server that will host the virtualized system) to the SCVMM Server. This BITS operation fails due to a certificate problem as indicated by the error 0x80072F0C (ERROR_INTERNET_CLIENT_AUTH_CERT_NEEDED).

Resolution:

To resolve this issue, remove the managed host from the SCVMM server and also delete any residual certificates from the host on the VMM server, then re-add the host:

1. On the SCVMM server, remove the managed host from the console. The steps on how to remove a managed host are outlined in the following TechNet article:

http://technet.microsoft.com/en-us/library/cc956121.aspx (http://technet.microsoft.com/en-us/library/cc956121.aspx)

2. Now we need to locate and delete any certificates for the Host computer.

3. Open the Certificate console on the SCVMM server.

a. Open a new mmc and add the certificates snap-in.
b. Select the option of ‘computer account’ and ‘local computer’.
c. Select Finish and Ok to load the snap-in.

4. The certificates for the Host computer can be in any of the following locations.

a. Personal Certificates.
b. Trusted People (if the host is W2K8 or W2K8 R2).
c. Trusted Root Authorities (If the host is W2K3).

5. In each store, expand the Friendly Name field and locate the certificate[s] for the Host server that have a Friendly Name starting with ‘SCVMM_CERTIFICATE_KEY_CONTAINER’ followed by either the FQDN / IP address / NetBIOS name of the Host server and delete them.

6. Re-add the host in SCVMM which recreates the certificates as needed.

More Information:

SCVMM uses BITS to transfer payload between SCVMM managed computers. These data transfers are encrypted by using a self-signed certificate generated at the time a host machine is added to SCVMM. If these certificates are missing or corrupted from the SCVMM server or managed computers, the payload deployment job can fail. Deleting the certificates and re-adding the host will cause the certificates to be regenerated.

For the latest information on this issue see the following Knowledge Base article:

KB2385280 – P2V fails with Error 2912 0x80072F0C with System Center Virtual Machine Manager 2008 or System Center Virtual Machine Manager 2008 R2

J.C. Hornbeck | System Center Knowledge Engineer

Categories: Hyper-V R2, SCVMM, SCVMM R2, VMM Tags: , , ,
%d bloggers like this: