SCVMM 2019 Cretae VM Mount ISO error 2912

Question

All other operations in VMM are functioning normally, including refreshing virtual machines and clusters, as well as creating VMs through VHD. This error only occurs when mounting ISO files or using templates.

Error info:

================================================

An internal error occurred when attempting to contact the server "VMHOST22": NO_PARAM: NO_PARAM.

WinRM: URL: [http://vmhost22:5985], Verb: [INVOKE], Method: [GetError], Resource: [http://schemas.microsoft.com/wbem/wsman/1/wmi/root/microsoft/bits/BitsClientJob?JobId={67A9533A-DF5A-4542-9FF6-1C2CDF1CA25F}]

Unknown error (0x80072f05)

Suggested operations: Check whether the WS-Management service is installed and running on the server "VMHOST22". For more details, use the command "winrm helpmsg hresult". If "VMHOST22.cdtm.com" is a host/library/update server or PXE server role, ensure that the VMM agent is installed and running. For more information, please refer to http://support.microsoft.com/kb/2742275.

Answer 1

Hi,

It sounds like you're encountering a HostAgentFail (2912) error when trying to mount ISO files or use templates in SCVMM 2019. This error often relates to issues with the WS-Management service or the VMM agent on the host server.

Here are some steps you can take to troubleshoot and resolve this issue:

• Ensure the WS-Management (WinRM) service is installed and running on the server "VMHOST22". You can do this by running the command:

winrm quickconfig

• This command will start the WinRM service, set it to auto-start, and configure a listener for WS-Management protocol messages.
• Ensure that the VMM agent is installed and running on "VMHOST22". You can check the VMM agent status by reviewing the VMM agent installation log file located in the %systemdrive%\ProgramData\VMMLogs directory.
• Ensure that the necessary ports for VMM communication are open and not blocked by a firewall. VMM typically uses TCP ports 443, 5985, and 5986[2].

By following these steps, you should be able to identify and resolve the issue causing the error. If the problem persists, you might want to refer to the detailed troubleshooting guide provided by Microsoft.

HostAgentFail (2912) error in SCVMM activities - Virtual Machine ...

Feel free to ask if you need further assistance or have any other questions!

Answer 2

• Ensure the WS-Management (WinRM) service is installed and running on the server "VMHOST22". You can do this by running the command: winrm quickconfig This command will start the WinRM service, set it to auto-start, and configure a listener for WS-Management protocol messages. A: it's ok.
• Ensure that the VMM agent is installed and running on "VMHOST22". You can check the VMM agent status by reviewing the VMM agent installation log file located in the %systemdrive%\ProgramData\VMMLogs directory. A: it's ok.
• Ensure that the necessary ports for VMM communication are open and not blocked by a firewall. VMM typically uses TCP ports 443, 5985, and 5986 A: it's ok.

=========================================

Since the jobs of separately refreshing the VMM host and virtual machines are functioning normally, I personally think it is not a conventional WMI issue.