Unsolved

This post is more than 5 years old

1 Rookie

 • 

2 Posts

54927

February 9th, 2011 11:00

SWbemObjectEx: Invalid Parameter

I am new to the Dell OMCI stuff. So far the scripts seem to work well however when I run the restart script I get the following error: SampleRestart.vbs (51, 1) SWbemObjectEx: Invalid Parameter. I am running the sample script provided on the site. The system does shutdown but i want to find out why I am receiving this error message.

12 Posts

March 23rd, 2011 10:00

Balbaroy,

I feel the same pain. Trying to get the new RemoteBIOSUpdate command to work in the DCIM_BIOSService class. The published documentation is clearly out of date since a new instance of the InParms shows it also needs the AuthorizationToken (admin password for BIOS changes). Yet even when supplied... this method continues to throw: "invalid method parameters". =(

I will eagerly be looking for my post here to start showing up on a Google search of the term: RemoteBIOSUpdate
since the pickin's are really slim right now.

(in fact... let's list the parameter names as well, since those were producing zero matches in google:
Name : "AuthorizationToken" --- CIMType : wbemCimtypeString
Name : "rbuIPFName" --- CIMType : wbemCimtypeString )

10 Posts

November 16th, 2011 06:00

Sorry for taking this to an actual level.

but I'm struggling in OMCI scripting.

I've tested the OMCI Sample Scripts (v8) for resetting the chassis intrusion state. I commented out the password token thing and the script ran fine on a server with a domainadmin logged on and resetting an Optiplex 580 chassis intrusion state. The same constellation but on an Optiplex 740 ran into an error: SWbemObjectEx Invalid Parameter (71, 1)

in line 71 is something like:

For each objInstance in ColSystem

Set oInParams= objInstance.Methods_("SetBIOSAttributes").InParameters.SpawnInstance_

oInParams.AttributeName = strAttributeName

oInParams.AttributeValue = strAttributeValue

oInParams.AuthorizationToken = strAuthorizationToken

Set returnValue = objInstance.ExecMethod_("SetBIOSAttributes", oInParams)

Next

so where is the error, that a 580 is ok and a 740 not?

sorry forgot to mention: both (740 and 580) are OMCI v8 installations

1.1K Posts

November 16th, 2011 07:00

From the snippet of your script, I'm not sure that you need the strAuthorizationToken unless you have enabled a password.  

10 Posts

November 16th, 2011 08:00

here is the source

the only change, I made is the outcommenting of the strAuthorizationToken = " "

because of the absence of a BIOS-password

media.community.dell.com/.../samplechassisintrusionclear.vbs.txt

1.1K Posts

November 16th, 2011 08:00

I wouldn't comment out the strAuthorizationToken.  Change it from strAuthorizationToken=" " to strAuthorizationToken=""

10 Posts

November 16th, 2011 08:00

hmm... tried it already - same error.

Maybe it has to do with an older installation of omci 7.x? I made an update of omci with the v8. In "add remove programs" is the "Dell OpenMange Client Instrumentation"  instead of the OMCI entry.

I test the complete uninstall and reinstall of omci v8

edit: no change! (completely un- and reinstalled)

edit2: I remember, every time, I wanted to reset the chassis intrusion state manually in the BIOS, I had to do it twice. First time "Acknowledge", save and exit, then reboot, then 2nd "Acknowledge" and exit. I made little explorings with wbemtest on the 740 and found no "chassis Intrusion state" in the "DCIM_BIOSService"

edit3: tried to install the old namespace 7.x with omci v8 together. Seems to function right - the script (the one for 7.x) runs fine without any error. But the intrusion alert isn't resetted. It remains in the BIOS with "Acknowledge".

4 Posts

January 19th, 2012 05:00

I have the exact same problem.

New OptiPlex 790 workstations, running Windows 7 x64.  OMCI 8x64 installed using OM_APP_WIN_R300392.

I have downloaded a copy of the example script to clear chassis intrusion from here:

en.community.dell.com/.../omci-sample-scripts.aspx

We have not yet set a BIOS password so strAuthorizationToken = ""

Executing the script from an administrative command prompt using cscript results in the error "SWbemObjectEx: Invalid Parameter"

This is the exact script provided as an example on brand new hardware.  This should be the easiest thing in the world to test and yet it does not work.  If I am doing something wrong I would be grateful for the opportunity to admit and correct it but at this point I am unspeakably skeptical that this script would work if engineering actually tested it on a virgin install.

Any help would be greatly appreciated.

1.1K Posts

January 26th, 2012 09:00

Is the script issue limited to just the Optiplex 790 or does it happen on other systems?

0 events found

No Events found!

Top