Invalid namespace running WMI Run action

Hi again,

I’m trying to run an executable throught he WMI Run action on a remote computer but in the second it runs it gives the error:
"An error occured attempting to connect via WMI: Invalid namespace"

I tried to connec to different machines in the domain, same error.

What am I doing wrong?


Thanks,
NirS

I just tried to run it on my laptop and it didn’t give this error, so it’s a local problem, the question is what exactly.

Hi Nir,

Which Windows version are you using, and which are you connecting to? Which FinalBuilder version do you have?

Thanks.

- Angus

This TechNet topic might give you some clues:
http://www.microsoft.com/technet/scriptcenter/topics/help/wmi.mspx

Hi,

The computer I am trying to connect to is Windows 2000.
The first computer from which I get the error is windows 2000, and the laptop (the good one) is Win XP.

Tate, I looked at the technote but since I’m using the same target machine, it can’t be a namespace problem in that machine.

Thanks,
NirS

Hi Nir,

What Service Pack are you running on the Windows 2000 computers? Are they different? The default security levels for Windows 2000 SP2 are insufficent to connect to SP4 or later.

I can change the WMI action so it tries alternate connection levels before failing outright. However, it may not even be this (I don’t know why it is coming up as a Namespace Error - all the WMI actions try to do is connect to \root\cimv2 via the local computer’s default WMI settings.)

Regards,


Angus

Hi Nir,

Could you please try this test build and let me know if it makes any difference?

https://www.finalbuilder.com/downloads/finalbuilder/500/FB500_71.exe

Regards,


Angus

Hi Angus,

This build fixes the problem :slight_smile:

What was the bug?
Thanks,
NirS

Hi Nir,

I’m not sure… it could be that some W2K versions are fussy about the namespace format (it was using \root\cimv2, changed it to ROOT\cimv2), or it could be that SP2 was using insufficiently strong security settings for SP4 (the action now tries with the system defaults, then tries again with stronger settings if the defaults fail.)

Glad you got it working.

Regards,


Angus