Would you be able to try that VBScript script and see if you get the same error? My code uses the same WMI classes as the script. Comment out the email code and add objHostInstance.Stop before objHostInstance.Start.
I'm still baffled as to why it would be mentioning 333 at all, because the code takes the same WMI object instance and calls Stop() on it (which worked), refreshes the state, then calls Start(). The log output matches the code.
I've never had a cluster to test it on, so unfortunately I had to fly blind writing the code with guidance from TechNet and docs.
Thanks,
Tom
I'm still baffled as to why it would be mentioning 333 at all, because the code takes the same WMI object instance and calls Stop() on it (which worked), refreshes the state, then calls Start(). The log output matches the code.
I've never had a cluster to test it on, so unfortunately I had to fly blind writing the code with guidance from TechNet and docs.
Thanks,
Tom