wmimgmt.msc launch correcty
but an error occured, "impossible to connect, WMI not found"
it wasn't a problem in my script but it was with XP that was a bit too
much customized
thanks
Le 25/02/2010 11:17, Tim Golden a écrit :
On 25/02/2010 09:55, Christophe Deze wrote:
Le 24/02/2010 20:18, Tim Roberts a écrit :
Christophe Deze wrote:
i'm looking for information about this error
Traceback (most recent call last):
File "Frame1.pyo", line 235, in run
File "wmi.pyo", line 1267, in connect
File "wmi.pyo", line 241, in handle_com_error
x_wmi:<x_wmi: Unexpected COM Error (-2147352567, "Une exception s'est
produite.", (0, u'SWbemLocator', u'Non trouv\xe9 ', None, 0,
-2147217406), None)>
it run from windows XP
u'Non trouv\xe9 ' means object not found I think
Yes, -2147217406 is 0x80041002, which is WBEM_E_NOT_FOUND.
in my script line 235 is
c= wmi.WMI(computer=self.ip, user=self.adm, password=self.admmdp)
What did you pass for self.ip?
it 's just an address IP
172.16.127.250
Just to eliminate WMI as such, could you insert these lines
before your line 235:
<code snippet>
import socket
print self.ip
socket.socket ().connect ((self.ip, 135))
</snippet>
In principle this should show if there's some network
reachability issue at the DCOM level...
TJG
_______________________________________________
python-win32 mailing list
python-win32@python.org
http://mail.python.org/mailman/listinfo/python-win32
_______________________________________________
python-win32 mailing list
python-win32@python.org
http://mail.python.org/mailman/listinfo/python-win32
