WMI Fun !! 〜 WMI に興味がある方・システム管理者は必見です! 〜
 WMI Step|WMI Sample|WMI Reference|WMI Library|Enquete|About WMI Fun !!
 My Let'snote|Personal|Insomnia|Link

WMI Fun !! > WMI Library > MSFT_ExtendedStatus クラス

このエントリーをはてなブックマークに追加
Panasonic Let'snote を長年愛用しています、その理由は My Let'snote で…
中古車買うならやっぱりカーセンサーnet、お気に入りの 1 台が見つかります
IT 関連情報を気軽に知りたい方へ、キーマンズネットがおすすめです

MSFT_ExtendedStatus クラス - WMI Library

MSFT_ExtendedStatus クラスの説明

A Windows error object that encapsulates what is in CIM_Error as well as includes original_error.



プロパティ リスト

  • CIMStatusCode
 Data Type: uint32
 Access Type: Read Only

The CIM status code that characterizes this instance. This property defines the status codes that MAY be return by a conforming CIM Server or Listener. Note that not all status codes are valid for each operation. The specification for each operation SHOULD define the status codes that may be returned by that operation. The following values for CIM status code are defined: 1 - CIM_ERR_FAILED. A general error occurred that is not covered by a more specific error code. 2 - CIM_ERR_ACCESS_DENIED. Access to a CIM resource was not available to the client. 3 - CIM_ERR_INVALID_NAMESPACE. The target namespace does not exist. 4 - CIM_ERR_INVALID_PARAMETER. One or more parameter values passed to the method were invalid. 5 - CIM_ERR_INVALID_CLASS. The specified Class does not exist. 6 - CIM_ERR_NOT_FOUND. The requested object could not be found. 7 - CIM_ERR_NOT_SUPPORTED. The requested operation is not supported. 8 - CIM_ERR_CLASS_HAS_CHILDREN. Operation cannot be carried out on this class since it has instances. 9 - CIM_ERR_CLASS_HAS_INSTANCES. Operation cannot be carried out on this class since it has instances. 10 - CIM_ERR_INVALID_SUPERCLASS. Operation cannot be carried out since the specified superclass does not exist. 11 - CIM_ERR_ALREADY_EXISTS. Operation cannot be carried out because an object already exists. 12 - CIM_ERR_NO_SUCH_PROPERTY. The specified Property does not exist. 13 - CIM_ERR_TYPE_MISMATCH. The value supplied is incompatible with the type. 14 - CIM_ERR_QUERY_LANGUAGE_NOT_SUPPORTED. The query language is not recognized or supported. 15 - CIM_ERR_INVALID_QUERY. The query is not valid for the specified query language. 16 - CIM_ERR_METHOD_NOT_AVAILABLE. The extrinsic Method could not be executed. 17 - CIM_ERR_METHOD_NOT_FOUND. The specified extrinsic Method does not exist. 18 - CIM_ERR_UNEXPECTED_RESPONSE. The returned response to the asynchronous operation was not expected. 19 - CIM_ERR_INVALID_RESPONSE_DESTINATION. The specified destination for the asynchronous response is not valid. 20 - CIM_ERR_NAMESPACE_NOT_EMPTY. The specified Namespace is not empty. 21 - CIM_ERR_INVALID_ENUMERATION_CONTEXT. The enumeration context supplied is not valid. 22 - CIM_ERR_INVALID_OPERATION_TIMEOUT. The specified Namespace is not empty. 23 - CIM_ERR_PULL_HAS_BEEN_ABANDONED. The specified Namespace is not empty. 24 - CIM_ERR_PULL_CANNOT_BE_ABANDONED. The attempt to abandon a pull operation has failed. 25 - CIM_ERR_FILTERED_ENUMERATION_NOT_SUPPORTED. Filtered Enumeratrions are not supported. 26 - CIM_ERR_CONTINUATION_ON_ERROR_NOT_SUPPORTED. Continue on error is not supported. 27 - CIM_ERR_SERVER_LIMITS_EXCEEDED. The WBEM Server limits have been exceeded (e.g. memory, connections, ...). 28 - CIM_ERR_SERVER_IS_SHUTTING_DOWN. The WBEM Server is shutting down. 29 - CIM_ERR_QUERY_FEATURE_NOT_SUPPORTED. The specified Query Feature is not supported.



  • CIMStatusCodeDescription
 Data Type: string
 Access Type: Read Only

A free-form string containing a human-readable description of CIMStatusCode. This description MAY extend, but MUST be consistent with, the definition of CIMStatusCode.



  • error_Category
 Data Type: uint16
 Access Type: Read Only

Error Category.



  • error_Code
 Data Type: uint32
 Access Type: Read Only

Error code.



  • error_Type
 Data Type: string
 Access Type: Read Only

Error Type.



  • error_WindowsErrorMessage
 Data Type: string
 Access Type: Read Only

Windows error message.



  • ErrorSource
 Data Type: string
 Access Type: Read Only

The identifying information of the entity (i.e., the instance) generating the error. If this entity is modeled in the CIM Schema, this property contains the path of the instance encoded as a string parameter. If not modeled, the property contains some identifying string that names the entity that generated the error. The path or identifying string is formatted per the ErrorSourceFormat property.



  • ErrorSourceFormat
 Data Type: uint16
 Access Type: Read Only

An array containing the dynamic content of the message.



  • ErrorType
 Data Type: uint16
 Access Type: Read Only

Primary classification of the error. The following values are defined: 2 - Communications Error. Errors of this type are principally associated with the procedures and/or processes required to convey information from one point to another. 3 - Quality of Service Error. Errors of this type are principally associated with failures that result in reduced functionality or performance. 4 - Software Error. Error of this type are principally associated with a software or processing fault. 5 - Hardware Error. Errors of this type are principally associated with an equipment or hardware failure. 6 - Environmental Error. Errors of this type are principally associated with a failure condition relating the to facility, or other environmental considerations. 7 - Security Error. Errors of this type are associated with security violations, detection of viruses, and similar issues. 8 - Oversubscription Error. Errors of this type are principally associated with the failure to allocate sufficient resources to complete the operation. 9 - Unavailable Resource Error. Errors of this type are principally associated with the failure to access a required resource. 10 -Unsupported Operation Error. Errors of this type are principally associated with requests that are not supported.



  • Message
 Data Type: string
 Access Type: Read Only

The formatted message. This message is constructed by combining some or all of the dynamic elements specified in the MessageArguments property with the static elements uniquely identified by the MessageID in a message registry or other catalog associated with the OwningEntity.



  • MessageArguments
 Data Type: string
 Access Type: Read Only

An array containing the dynamic content of the message.



  • MessageID
 Data Type: string
 Access Type: Read Only

An opaque string that uniquely identifies, within the scope of the OwningEntity, the format of the Message.



  • original_error
 Data Type: object
 Access Type: Read Only

N/A



  • OtherErrorSourceFormat
 Data Type: string
 Access Type: Read Only

A string defining "Other" values for ErrorSourceFormat. This value MUST be set to a non NULL value when ErrorSourceFormat is set to a value of 1 ("Other"). For all other values of ErrorSourceFormat, the value of this string must be set to NULL.



  • OtherErrorType
 Data Type: string
 Access Type: Read Only

A free-form string describing the ErrorType when 1, "Other", is specified as the ErrorType.



  • OWningEntity
 Data Type: string
 Access Type: Read Only

A string that uniquely identifies the entity that owns the definition of the format of the Message described in this instance. OwningEntity MUST include a copyrighted, trademarked or otherwise unique name that is owned by the business entity or standards body defining the format.



  • PerceivedSeverity
 Data Type: uint16
 Access Type: Read Only

An enumerated value that describes the severity of the Indication from the notifier's point of view: 0 - the Perceived Severity of the indication is unknown or indeterminate. 1 - Other, by CIM convention, is used to indicate that the Severity's value can be found in the OtherSeverity property. 2 - Information should be used when providing an informative response. 3 - Degraded/Warning should be used when its appropriate to let the user decide if action is needed. 4 - Minor should be used to indicate action is needed, but the situation is not serious at this time. 5 - Major should be used to indicate action is needed NOW. 6 - Critical should be used to indicate action is needed NOW and the scope is broad (perhaps an imminent outage to a critical resource will result). 7 - Fatal/NonRecoverable should be used to indicate an error occurred, but it's too late to take remedial action. 2 and 0 - Information and Unknown (respectively) follow common usage. Literally, the Error is purely informational or its severity is simply unknown.



  • ProbableCause
 Data Type: uint16
 Access Type: Read Only

An enumerated value that describes the probable cause of the error.



  • ProbableCauseDescription
 Data Type: string
 Access Type: Read Only

A free-form string describing the probable cause of the error.



  • RecommendedActions
 Data Type: string
 Access Type: Read Only

A free-form string describing recommended actions to take to resolve the error.





メソッド リスト



WQL サンプル (e.g. VB/PowerShell)

MSFT_ExtendedStatus

VB6/VBS
SWbemServicesクラスのExecQueryメソッドからWQLを実行可能です。
Set PrcSet = Service.ExecQuery("MSFT_ExtendedStatus")

VB.Net
ObjectQueryクラスのQueryStringプロパティにWQLを設定し、ManagementObjectSearcherクラスのGetメソッドからWQLを実行可能です。
Searcher.Query.QueryString = "MSFT_ExtendedStatus"
PrcSrc = Searcher.Get

PowerShell
Get-WmiObjectコマンドレットのqueryオプションを指定しWQLを実行可能です。
Get-WmiObject -query "MSFT_ExtendedStatus"


このサイトの情報について

このコンテンツはWMIの各コンポーネントが持っているMSFT_ExtendedStatusクラス情報を参照・抽出しリファレンスとして作成・提供しています。
参照したWMIの名前空間はroot/CIMV2、参照OS環境はWindows 2000以降のOSを対象としております。

WMIの使い方(VB6, VBS, VBA, VB.NET, VC#, PowerShellを対象)に関してはWMI Stepも参考にしてみてください。(WMI初心者・入門編としてもおすすめです。)
各種言語を使用したWMIを使用するたたき台としてソーステンプレートも公開しています。プログラム/スクリプト作成時に役立てば…と思っています。


ご意見・ご要望・ご感想をこちらのアンケートからお待ちしています
WMI に関して調べているけど探し物が見つからない…という方は右上の検索窓検索してみましょう!

MCP (Microsoft Certified Professional)、 MCA (Microsoft Certified Associate)CompTIA A+
一応 MCP (Microsoft Certified Professional)、MCA (Microsoft Certified Associate)、
CompTIA A+ を所有してたりします…

- WMI Fun !! -
http://www.wmifun.net/
Microsoft 社のテクノロジーである WMI (Windows Management Instrumentation) の使い方を
Visual Basic を使ってのんびり公開しています
WMI は Windows 7 や Windows 8、Windows 10 で便利に使えますよ!
また VB や VBA、.Net (VB・C#) などの開発環境以外でも Win32/Win64 API に依存しないので WMIC や
WSH (VBS・JS)・PowerShell などスクリプト言語・コマンドラインから有効に活用が出来ます
Windows ベースの社内 IT システムに関する資産管理、アセットマネジメントや監視業務の効率化、
インベントリ情報収集系システムツール開発に WMI はお勧めです

This website is created by Toh.
Copyright(C) 1997-2016 WMI Fun !! All rights reserved.
WMI Fun !! へのリンクはご自由に…相互リンクに関するお問い合わせはアンケートページからお願いします

∧ ページの先頭へ…