Error Reporting
This section about IANet_ExtendedStatus describes how to handle errors generated by WMI and CDM
Providers.
How and when an error object is returned depends on whether a call is synchronous, semi-synchronous or asynchronous. In most cases, the HRESULT
is set to WBEM_E_FAILED when an error occurs. At this point, however, it is unknown whether WMI or the Providers generated the error.
To get the error object for synchronous calls, use GetErrorInfo() to get the IErrorInfo object. Use QueryInterface() to get the IWbemClassObject that contains the error information.
To get the error object for asynchronous calls, the IWbemClassObject is passed back as the last item in the last SetStatus() call.
After you get the error object instance, you can check the __Class property to determine the origin of the error.
WMI creates an instance of __ExtendedStatus, and the Providers create an instance of IANet_ExtendedStatus for errors
relating to IANet_ classes. IANet_ExtendedStatus is derived from __ExtendedStatus and contains the following error object qualifiers:
- Description — Description of the error tailored to the current locale.
- File — Code file where the error was generated.
- Line — Line number of the code file with the error.
- ParameterInfo — Class or attribute that was being utilized when the error occurred.
- Operation — Operation being attempted when the error occurred.
- ProviderName — Name of the Provider that caused the error.
- StatusCode — Code returned from the internal call that failed.
- SessionHandle — Session handle used for the operation.
- RuleFailureReasons — Reason for operation failure. An operation can fail because a technical rule has failed. (e.g., you must have a management adapter in certain teams).
Error Codes
For all error codes, the Providers give a description customized to the locale. Error codes are in the form of HRESULT with severity set to one (1) and facility set to ITF. An application may use the following codes as a basis for a recovery action:
- 0x80040901 — "WMI: Put property failed"
- 0x80040902 — "WMI: No class object"
- 0x80040903 — "WMI: Failed to create class"
- 0x80040904 — "WMI: Failed to spawn instance of class"
- 0x80040905 — "WMI: Failed to create safe array"
- 0x80040906 — "WMI: Failed to put safe array"
- 0x80040907 — "WMI: Failed to return object to WMI"
- 0x80040908 — "WMI: Get property failed"
- 0x80040909 — "WMI: Unexpected type while getting property"
- 0x8004090A — "WMI: Class not implemented by this provider"
- 0x8004090B — "WMI: Unable to parse WQL statement"
- 0x8004090C — "WMI: Providers only support WQL"
- 0x8004090D — "WMI: Parameter in context has the wrong type"
- 0x8004090E — "WMI: Error formatting debug log"
- 0x8004090F — "WMI: bad object path"
- 0x80040910 — "WMI: Failed to update setting"
- 0x80040911 — "WMI: Null parameter passed to method"
- 0x80040912 — "Setting value too small."
- 0x80040913 — "Setting value too big."
- 0x80040914 — "Setting not in step"
- 0x80040915 — "String setting is too long"
- 0x80040916 — "Setting is not one of the allowed values"
- 0x80040917 — "WMI: Qualifier not found"
- 0x80040918 — "WMI: Qualifer set not found"
- 0x80040919 — "WMI: Safe array access failed"
- 0x8004091A — "WMI: Unhandled exception"
- 0x8004091B — "WMI: Operation is not supported for this class"
- 0x8004091C — "WMI: Unexpected event class"
- 0x8004091D — "WMI: Bad event data"
- 0x8004091E — "WMI: Operation succeeded with warnings"
- 0x8004081F — "WMI: The NCS Service has been stopped."
- 0x80040801 — "EAL: Internal exception"
- 0x80040802 — "EAL: General failure"
- 0x80040803 — "EAL: Not initialized"
- 0x80040804 — "EAL: Failed to initialize."
- 0x80040805 — "EAL: Session limits exceeded"
- 0x80040806 — "EAL: Out of memory"
- 0x80040807 — "EAL: Rule syntax error"
- 0x80040808 — "EAL: Unexpected end of list"
- 0x80040809 — "EAL: Rule link error"
- 0x8004080A — "EAL: Device Creation Failed"
- 0x8004080B — "EAL: Media service not found"
- 0x8004080C — "EAL: Device service not found"
- 0x8004080D — "EAL: PCI bus module not found"
- 0x8004080E — "EAL: Adapter is a member of a team"
- 0x8004080F — "EAL: Rule Access Point creation error"
- 0x80040810 — "EAL: Registry key error"
- 0x80040811 — "EAL: Registry XML file path error"
- 0x80040812 — "EAL: Unknown event class"
- 0x80040813 — "EAL: Unknown module id"
- 0x80040814 — "EAL: Rule service not found"
- 0x80040815 — "EAL: NULL input pointer"
- 0x80040816 — "EAL: Rule grammar error"
- 0x80040817 — "EAL: Rule failed"
- 0x80040818 — "EAL: Setting is already grouped"
- 0x80040220 — "Sync Layer: Team removal failed."
- 0x80040221 — "Sync Layer: Vlan creation failed."
- 0x80040222 — "Sync Layer: Vlan removal failed."
- 0x80040223 — "Sync Layer: Adapter removal failed."
- 0x80040224 — "Sync Layer: Setting Change/Creation/Removal failed."
- 0x80040225 — "Sync Layer: Parameter Change/Removal failed."
- 0x80040226 — "Sync Layer: NetConfig subsystem locked. "
- 0x80040227 — "Sync Layer: System Update In Progress. Please try again later."
- 0x80040228 — "Sync Layer: Adapter is Locked"
- 0x80040229 — "Sync Layer: Flash read failed."
- 0x8004022A — "Sync Layer:"
- 0x80040210 — "Sync Layer: Invalid event offset"
- 0x80040211 — "Sync Layer: Invalid input"
- 0x80040212 — "Sync Layer: Invalid key"
- 0x80040213 — "Sync Layer: Adapter not team member"
- 0x80040214 — "Sync Layer: Driver not loaded"
- 0x80040215 — "Sync Layer: Client impersonation failed"
- 0x80040216 — "Sync Layer: Caught exception"
- 0x80040217 — "Sync Layer: Session not locked"
- 0x80040218 — "Sync Layer: Hardware access layer is not available"
- 0x80040219 — "Sync Layer: Flash not available"
- 0x8004021A — "Sync Layer: Diagnostics not supported"
- 0x8004021B — "Sync Layer: Diagnostic test not running"
- 0x8004021C — "Sync Layer: Boot Agent update not available"
- 0x8004021D — "Sync Layer: Boot Agent corrupted."
- 0x8004021E — "Sync Layer: Flash write failed."
- 0x8004021F — "Sync Layer: Team creation failed."
- 0x80040201 — "Sync Layer: Initialization failed"
- 0x80040202 — "Sync Layer: Invalid initialization handle"
- 0x80040203 — "Sync Layer: Session handle already exists"
- 0x80040204 — "Sync Layer: Invalid session handle"
- 0x80040205 — "Sync Layer: The maximum number of sessions has been reached."
- 0x80040206 — "Sync Layer: The session lock handle already exists"
- 0x80040207 — "Sync Layer: Invalid session lock handle"
- 0x80040208 — "Sync Layer: Session already locked"
- 0x80040209 — "Sync Layer: Invalid media service module Id"
- 0x8004020A — "Sync Layer: Invalid Advanced Service Module Id"
- 0x8004020B — "Sync Layer: Invalid device service module Id"
- 0x8004020C — "Sync Layer: Invalid component type Id"
- 0x8004020D — "Sync Layer: Invalid bus interface module Id"
- 0x8004020E — "Sync Layer: Invalid sink window handle"
- 0x8004020F — "Sync Layer: Invalid event Id"
- 0x80040401 — "HAM PCI: Invalid memory map address"
- 0x80040402 — "HAM PCI: Configuration driver failed to load"
- 0x80040403 — "HAM PCI: Configuration driver version mismatch"
- 0x80040404 — "HAM PCI: Device slot not found"
- 0x80040405 — "HAM PCI: Diagnostic driver failed to load"
- 0x80040406 — "HAM PCI: Diagnostic driver version mismatch"
- 0x80040407 — "HAM PCI: Diagnostic driver initialization failed"
- 0x80040408 — "HAM PCI: Diagnostics not initialized"
- 0x80040409 — "HAM PCI: Diagnostics already initialized"
- 0x8004040A — "HAM PCI: Diagnostic test already running"
- 0x8004040B — "HAM PCI: Diagnostic test not running"
- 0x8004040C — "HAM PCI: Diagnostic test terminated"
- 0x8004040D — "HAM PCI: Diagnostic Invalid test number"
- 0x8004040E — "HAM PCI: Diagnostic hardware missing"
- 0x8004040F — "HAM PCI: Diagnostic send receive initialization failed"
- 0x80040511 — "Media Service: NDIS IO call failed"
- 0x80040512 — "Media Service: Miniport not loaded"
- 0x8004051B — "Media Service: Invalid device handle"
- 0x8004051C — "Media Service: Invalid adapter handle"
- 0x8004051D — "Media Service: Invalid team handle"
- 0x8004051E — "Media Service: Invalid VLAN handle"
- 0x8004051F — "Media Service: Device missing"
- 0x80040520 — "Media Service: Invalid setting type"
- 0x80040521 — "Media Service: Unknown invalid object"
- 0x80040522 — "Media Service: Invalid Setting Handle"
- 0x80040523 — "Media Service: Invalid Team Mode"
- 0x80040525 — "Media Service: Setting Already Exists"
- 0x80042001 — "RAP: Already initialized"
- 0x80042002 — "RAP: Invalid XML file"
- 0x80042003 — "RAP: XML load error"
- 0x80042004 — "RAP: Not initialized"
- 0x80042005 — "RAP: Rule not extracted before"
- 0x80042006 — "RAP: Conditions count mismatch"
- 0x80042007 — "RAP: Results apply error"
- 0x80042008 — "RAP: Invalid rule"
- 0x80042009 — "RAP: Node not found"
- 0x8004200A — "RAP: Error no single node"
- 0x8004200B — "RAP: No action rule"
- 0x8004200C — "RAP: Zero condition"
- 0x8004200D — "RAP: Zero action"
- 0x8004200E — "RAP: XML Decode error"
Home
Copyright© 2002 Intel Corporation. Legal Information