VMM Error after updating to UR7 - An internal error has occurred trying to contact the * server: *: *.

I updated several different environments to UR7, all hosting their own independent version of VMM in identical configurations, and in the process found one of them stopped being able to deploy service templates. When an administrator attempted to deploy a template to a cloud the following error appeared in the log:

Error (22042)
The service APP01 was not successfully deployed. Review the event log to determine the cause and corrective actions. Recommended Action
The deployment can be restarted by retrying the job.
Error (2912)
An internal error has occurred trying to contact the * server: *: *.* Unknown error (0x80072f0d) Recommended Action
Check that WS-Management service is installed and running on server *. For more information use the command "winrm helpmsg hresult". If * is a host/library/update server or a PXE server role then ensure that VMM agent is installed and running. Refer to http://support.microsoft.com/kb/2742275 for more details. Please contact your system administrator with this error ID.
Error (2912)
An internal error has occurred trying to contact the * server: *: *. * Unknown error (0x80072f0d) Recommended Action
Check that WS-Management service is installed and running on server *. For more information use the command "winrm helpmsg hresult". If * is a host/library/update server or a PXE server role then ensure that VMM agent is installed and running. Refer to http://support.microsoft.com/kb/2742275 for more details. Please contact your system administrator with this error ID.

The oddest part of this error is the *:*.* which appears to mean it cannot resolve the server name for the cloud but this turned out not to be the case.

I thought at first this was related to the agent updates and other changes but it appears to be coincidental as all of the other environments updated without issue, and can deploy Service Templates without error.  Digging into the logs of all of the hosts and the VMM server showed no further information, and all hosts were accessible and WMI was responding correctly.

I ran the debug trace while performing the deployment and managed to capture an exception that pointed at the library which is also located on one of the hosts:

[1916] *** \\HOST.DOMAIN.COM\VMMLibrary\unattend.xml ** VMM.DOMAIN.COM ** 444 ** WinRM: URL: [http://VMM.DOMAIN.COM:5985], Verb: [INVOKE], Method: [GetError], Resource: [http://schemas.microsoft.com/wbem/wsman/1/wmi/root/microsoft/bits/BitsClientJob?JobId={1BCA816F-33EE-4E23-931C-FC5F91437874}] ** VMM.DOMAIN.COM **

I exported all of the Service Templates and VM Templates, removed the library from VMM, removed the host from VMM, rebooted the host, readded the HOST and then the library and re-imported all of the templates.

Success - all of the templates are now deploying happily.

Thought I'd report it just in case someone else strikes the error as well.


UPDATED :  Don't forget to check any already deployed templates using resources in the library that are tagged as deleting and re-adding the library will orphan most of those resources and you will spend a lot of time fixing the links between the deployed templates and the items in the library.
  • Edited by BevanSNZ Monday, August 24, 2015 9:41 PM update
August 24th, 2015 9:18pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics