What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

the vm could not be found. is it powered off?

Votes:

0

hi

I have start using free edition of PRTG nework monitor. Some of VM's on my hyper-v box show above error

I can clearly see those VM's running fine

How to fix this issue

Thanks

hyper-v prtg vmware

Created on Jul 28, 2014 2:52:37 PM



6 Replies

Votes:

0

Have those VM's moved hosts at all? If so, the index number that PRTG uses to find their monitoring information may have changed. If this is the case, you can recreate the sensors with the new ID's.

Created on Jul 29, 2014 7:52:43 PM by Greg Campion [Paessler Support]



Votes:

0

hi

Thanks for reply.

Well those VM's move from windows 2008 R2 Hypver-v sever to Windows 2012 R2 Hypver-v server months ago before even installing PRTG monitoring software few days ago

So do you think it make any sense ?

I can see those VM cleraling running and PRTG says stats as down

How you I re-create sensor for those VM on hypver-v server

Any idea???

Created on Jul 30, 2014 5:27:34 AM



Votes:

0

hi

I deleted the Hyper-V Virtual Machine Sensor for VM's and recreated again on Hypver-V server

But still same error

Please help

Created on Jul 30, 2014 6:00:22 AM



Votes:

0

Please try and disable User Account Control (UAC) in the control panel of the Windows operating system which is running on these virtual machines. Otherwise, the sensor might switch into a down status with the error message "The virtual is not running or is powered off".

Created on Jul 30, 2014 11:42:42 AM by Greg Campion [Paessler Support]



Votes:

0

hi

I have disabled the UA still same issue. :(

Created on Jul 30, 2014 12:18:17 PM



Votes:

0

Is it also disabled on the host server as well as the VM's themselves? Have you tried rebooting the VM's after making the change and then recreating the sensors?

Created on Jul 31, 2014 8:26:18 AM by Greg Campion [Paessler Support]




Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.