locked
GetDiskPartitionSpace.vbs for Hyper-V Nodes RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    All,

    Multiple times a week we receive an alert that the GetDiskPartitionSpace.vbs script fails with error: Invalid procedure call or argument. This script is targetted at our hyper-v host servers and tries to determine the free space for the guest.
    During my research to fix this script error I've discovered that the Virtual Machine View (in Microsoft Hyper-V Folder) contains multiple instances of guests for the various hyper-v nodes. 

    For example. The hyper-v cluster consists of 4 nodes, we might have 2 or 3 instances in the Virtual Machine state view, where only one is monitor. The unmonitored instances seem to create the afore mentioned script error. Which seems logical, the host cannot reach the VM (its on a different host). The discovery of the VM's runs every 24 hours.

    Does anyone else experience this behaviour? How can we make sure that only the current host of the Virtual Machine has the VM instance on it?

    Regards,

    Mark

    Friday, April 15, 2011 2:36 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    If this isn't happening every time the scripts run (or always on the same servers) then what you can do is try and correlate what is going on on the hosts at the time of the alert.  For instance, is someone doing maintenance on the hyper-v servers at these times?

    Also try looking for more details on the individual hyper-v hosts - look in the windows event log named operations manager.  If there are more details there, it would help since there isn't much to go on.  The cluster behavior is interesting.

    Microsoft Corporation
    • Marked as answer by Vivian Xing Friday, April 22, 2011 9:29 AM
    Friday, April 15, 2011 3:48 PM