On Tue, Apr 21, 2009 at 3:52 PM, Tim Golden m...@timgolden.me.uk wrote:
Actually I had previously placed a delay between the new_rule creation
and calling AddMembershipRule for another reason -- to make a clear
break in the timestamps on the server side wmi logs. Unfortunately
the delay
John Randolph wrote:
On Tue, Apr 21, 2009 at 3:52 PM, Tim Golden m...@timgolden.me.uk wrote:
Actually I had previously placed a delay between the new_rule creation
and calling AddMembershipRule for another reason -- to make a clear
break in the timestamps on the server side wmi logs.
John Randolph wrote:
Actually I had previously placed a delay between the new_rule creation
and calling AddMembershipRule for another reason -- to make a clear
break in the timestamps on the server side wmi logs. Unfortunately
the delay doesn't help.
Shame.
Adding a Put_ gave me a
Hi list:
I've been beating my head against this problem for 2 days and can't
figure it out. Searching the archives produced a semi-relevant thread
from the past but the former fixes haven't worked for me.
Using wmi 1.3.2, I've got the following simple code:
system =
On Fri, Apr 17, 2009 at 4:59 PM, John Randolph johnrando...@gmail.com wrote:
snip
wmi.x_wmi: -0x7ffdfff7 - Exception occurred.
Error in: SWbemObjectEx
-0x7ffbefff - Generic failure
(er, message got cut off)
anyway, enabling verbose WMI logging didn't produce anything revealing.
anyone have
John Randolph wrote:
Hi list:
I've been beating my head against this problem for 2 days and can't
figure it out. Searching the archives produced a semi-relevant thread
from the past but the former fixes haven't worked for me.
Using wmi 1.3.2, I've got the following simple code:
system =
On Fri, Apr 17, 2009 at 5:28 PM, Tim Golden m...@timgolden.me.uk wrote:
The first suggests a delay might help. The second doesn't come to
any conclusion except that if the last poster got it working then
it's something a bit environmental. Try the delay, perhaps.
FWIW, the WMI code probably
