Go to Google Groups Home    microsoft.public.scripting.vbscript
Re: WMI error

Tom K <thomas.dotk...@thighmarkdot.com>

"Tom Lavedas" <tglba...@cox.net> wrote in message

news:cefc4adb-91b3-47f7-803e-e28a96f01a6f@f63g2000hsf.googlegroups.com...

> On Mar 18, 9:15 am, "Tom K" <thomas.DOTk...@ThighmarkDOT.com> wrote:
>> This line in our logon script...

>> Set oWMIService =
>> GetObject("winmgmts:{impersonationLevel=impersonate}!\\.\root\cimv2")

>> ...returns an error code 80041002 on some systems.

>> Anyone have ideas what might be causing it?

>> Thanks,

>> Tom

> Are these WinNT systems?  That error is WBEM_E_NOT_FOUND according to
> a search at MSDN.  IIRC, NT does not have WMI installed, though it can
> run it.

> If they are not NT, then the problem must presumably be related to a
> fault in the WMI installation.

> In any case, it would appear to be a configuration problem, not a
> scripting fault.  You may get more help at the WMI or a sys admin
> group.

> Tom Lavedas
> ===========
> http://members.cox.net/tglbatch/wsh/

Thanks for the quick reply, Tom.  These are all fully patched Windows XP SP2
systems that are displaying the problem.  I forgot to include the WMI group
on my OP so I've added them now.  Hopefully those wizards will have
something for me.

The $65,000 question is what is the quickest and easiest way to rebuild the
WMI installation?

Tom