Tech Tip: UIM - hyperv probe cannot connect to server

Document created by danst04 Employee on Mar 13, 2017Last modified by danst04 Employee on Mar 13, 2017
Version 2Show Document
  • View in full screen mode

Document ID:  TEC000002402
Last Modified Date:  12/22/2016
Show Technical Document Details

Problem:

Connection to hyperv host machine fails.

Environment:

hyperv probe: any version

hyperv requirements:

- Installation of .Net framework 3.5 is required on the machine where the hyperv probe will be deployed.
- Nimsoft Robot 3.00 or higher

- hypervisor system (Windows 2008/2012/2012 R2 Server + Hyper-V / Windows 2008 Server Core + Hyper-V

- Virtual Machines configured on the Host OS

Note: Version 3.0 or later of the probe is available only through the web-based GUI. The Infrastructure Manager (IM) GUI is only available for version 2.2 or earlier.

Resolution:

Increase the log level to 5, and logsize to 20000

Deactivate the probe, wait for the probe to turn grey, then Activate the probe.

Test the connection via the GUI and then review the log.

 

If you are seeing ACCESS DENIED errors, e.g.,

Connection failed: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))

-> then you probably have to change the username to use the domain or workgroup, e.g., workgroup\administrator.

If its not an access issue, and you're receiving this popup error:

Host Response (popup window)

 

"Failed to query the host '10.x.x.x'
The reason for this could be one opf many, please check:

 

- The hostname or ip address is illegal or wrong."

Please run through the commands listed below to make sure hyperv can connect to the server.

 

Configuration commands: (edit to suit your environment)

 

Enable-PSRemoting
reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v LocalAccountTokenFilterPolicy /t REG_DWORD /d 1 /f
netsh advfirewall firewall add rule name="WinRM-HTTPS" dir=in localport=5986 protocol=TCP action=allow
netsh advfirewall firewall add rule name="WinRM-HTTP" dir=in localport=5985 protocol=TCP action=allow
netsh advfirewall firewall add rule name="WinRM-HTTPS" dir=in localport=5986 protocol=TCP action=allow
Set-Item "wsman:\localhost\client\trustedhosts" -Value '*.xxxxx.xx' -Force
Set-Item "wsman:\localhost\client\trustedhosts" -Value '*' -Force
Configure-SMRemoting.exe –enable
winrm set winrm/config/client/auth '@{Basic="true"}'
winrm set winrm/config/service/auth '@{Basic="true"}'
winrm set winrm/config/service '@{AllowUnencrypted="true"}'
winrm set winrm/config/client '@{AllowUnencrypted="true"}'
winrm set winrm/config/client '@{TrustedHosts="*"}'
winrm set winrm/config/winrs '@{MaxMemoryPerShellMB="1024"}'

 

Test commands:

 

Test-WSMan -ComputerName (IP or host name)
Get-WmiObject -Query "Select * from Win32_PerfRawData_Counters_HyperVVirtualStorageDevice" -Namespace "root\cimv2"

 

 

Additional Info:

https://docops.ca.com/ca-unified-infrastructure-management-probes/en/alphabetical-probe-articles/hyperv-microsoft-hyper-v-monitoring/hyperv-microsoft-hyper-v-monitoring-release-notes

1 person found this helpful

Attachments

    Outcomes