 Custom Search Guy recommends : Get more ideas for your PowerShell scripts with SolarWinds’ WMI Monitor. Funny computer jokesTroubleshooting Code 80041010 – Invalid ClassIntroduction to Code 80041010Error code, 80041010 occurs when you execute a VBScript connecting to WMI (Windows Management Instrumentation). This is a spelling error check the names of the objects. Alternatively, you could be trying to use a class that does not exist. In particular check for plurals which should be singulars e.g. win32_OperatingSystem and not win32_OperatingSystemS. The Symptoms You GetThe script does not manipulate the WMI object as you had hoped, instead you get a Windows Script Host error message. The Cause of Code 80041010Your VBScript contains a misspelled object name. Code 80041010 is an unusual Error in that a number is returned rather than ‘Syntax Error’ or other message. The SolutionsCheck the class definitions in the WMI section of the your script, check for extra letters, plurals can be a particular problem, e.g. system or systemS. As ever, pay close attention to the line number: Line: 4. In this case it Char: 1 is not to blame. When none of the line can execute, the error gets charged to the first character.
Example of Error Code 80041010 ScriptNote: Line 4: win32_OperatingSystemsOperatingSystems It should be win32_OperatingSystem (Singular) ‘WMI Script Correct Version – Thanks to Ed Crowley‘WMI Script See a PowerShell example of Win32_OperatingSystem » Seven General Troubleshooting Strategies for 800 Errors
See More Windows Update Error Codes 8004 Series• Error 80004005 Unspecified Error •Error 80041021 •Error 80041001 •Error 80041002 • Error 80048820 •Error 8004100E •Review of SolarWinds Application Monitor (SAM) • Error 80040E14 • Error 80040E37 • Error 80041006 • Error 80041006
|
