| File name: | EventTracingManagement.dll.mui |
| Size: | 19968 byte |
| MD5: | 62911de59846e193097694cc02a93d71 |
| SHA1: | e529ed7c7d69c929af52c088ea6432a31b2b65bf |
| SHA256: | 90a9731e30bf94cc4700e98f0ee15bd2c632daabfc99d4fe49a86282672283af |
| Operating systems: | Windows 10 |
| Extension: | MUI |
If an error occurred or the following message in Chinese (Simplified) language and you cannot find a solution, than check answer in English. Table below helps to know how correctly this phrase sounds in English.
| id | Chinese (Simplified) | English |
|---|---|---|
| 1 | InstanceID 是一个可选属性，可用于在实例化 Namespace 的作用域内模糊并唯一地标识此类的实例。此类的各种子类可能会替代此属性，使其成为必要属性或密钥。此类子类可能还会修改首选的算法，以确保唯一性（如下方所定义）。 为确保在 NameSpace 内的唯一性，InstanceID 的值应使用以下“首选”算法来构造: : 其中 和 以冒号 (:) 分隔，并且 中必须包含用于创建或定义 InstanceID 的版权、商标或商业实体拥有的其他唯一名称，或者公认世界权威机构向该商业实体分配的注册 ID。(此要求与架构类名称的 _ 结构类似。) 此外，为确保唯一性， 中必须包含一个冒号 (:)。在使用此算法时，InstanceID 中的第一个冒号必须位于 和 之间。 由商业实体选择，不得再用于标识其他基础(实际)元素。如果 不为空并且不使用上述“首选”算法，则负责定义的实体必须保证最终构造的 InstanceID 不会在此提供程序或任何其他提供程序为此实例的 NameSpace 创建的任何 InstanceID 中发生重复使用情况。 如果对于 DMTF 定义的实例， 未设置为空，则必须使用“首选”算法，并且将 设置为 CIM。 |
InstanceID is an optional property that may be used to opaquely and uniquely identify an instance of this class within the scope of the instantiating Namespace. Various subclasses of this class may override this property to make it required, or a key. Such subclasses may also modify the preferred algorithms for ensuring uniqueness that are defined below. To ensure uniqueness within the NameSpace, the value of InstanceID should be constructed using the following "preferred" algorithm: : Where and are separated by a colon (:), and where must include a copyrighted, trademarked, or otherwise unique name that is owned by the business entity that is creating or defining the InstanceID or that is a registered ID assigned to the business entity by a recognized global authority. (This requirement is similar to the _ structure of Schema class names.) In addition, to ensure uniqueness, must not contain a colon (:). When using this algorithm, the first colon to appear in InstanceID must appear between and . is chosen by the business entity and should not be reused to identify different underlying (real-world) elements. If not null and the above "preferred" algorithm is not used, the defining entity must assure that the resulting InstanceID is not reused across any InstanceIDs produced by this or other providers for the NameSpace of this instance. If not set to null for DMTF-defined instances, the "preferred" algorithm must be used with the set to CIM. |
| 2 | Caption 属性是关于对象的简短描述文字(只有一行的字符串)。 | The Caption property is a short textual description (one- line string) of the object. |
| 3 | Description 属性提供关于对象的文字描述。 | The Description property provides a textual description of the object. |
| 4 | 对象的用户友好名称。此属性允许每个实例在其密钥属性、标识数据和描述信息之外创建一个用户友好名称。 请注意，ManagedSystemElement 的 Name 属性也被定义为用户友好名称。但是，该属性通常被分类为密钥子类。正常情况下，同一属性无法在不引起任何不一致的情况下既标识身份又充当用户友好名称。如果存在 Name 属性并且其不是密钥属性(例如 LogicalDevice 的该属性)，则 Name 属性和 ElementName 属性中可显示相同的信息。请注意，如果存在 CIM_EnabledLogicalElementCapabilities 的关联实例，则此属性可能会受在该类的 ElementNameMask 和 MaxElementNameLen 属性中定义的限制所限。 |
A user-friendly name for the object. This property allows each instance to define a user-friendly name in addition to its key properties, identity data, and description information. Note that the Name property of ManagedSystemElement is also defined as a user-friendly name. But, it is often subclassed to be a Key. It is not reasonable that the same property can convey both identity and a user-friendly name, without inconsistencies. Where Name exists and is not a Key (such as for instances of LogicalDevice), the same information can be present in both the Name and ElementName properties. Note that if there is an associated instance of CIM_EnabledLogicalElementCapabilities, restrictions on this properties may exist as defined in ElementNameMask and MaxElementNameLen properties defined in that class. |
| 5 | 2.19.0 | 2.19.0 |
| 6 | ManagedElement 是一个抽象类，为 CIM 架构中的非关联类提供一个公共超类(即继承树的顶部)。 | ManagedElement is an abstract class that provides a common superclass (or top of the inheritance tree) for the non-association classes in the CIM Schema. |
| 7 | 一个日期时间值，表示对象的安装时间。缺少该值并不表示未安装对象。 | A datetime value that indicates when the object was installed. Lack of a value does not indicate that the object is not installed. |
| 8 | Name 属性定义对象的名称标签。在被分类为子类时，Name 属性可能会被替代为密钥属性。 | The Name property defines the label by which the object is known. When subclassed, the Name property can be overridden to be a Key property. |
| 9 | 表明元素的当前状态。定义了各种工作状态。其中的许多枚举\值都一目了然。但是，也有少数值并非如此，以下将对这些值予以详细说明。 “已强调”表明元素正在工作，但是需要注意。过载、过热等都属于“强调”状态。 “预测故障”表明元素表面上正在工作，但是预计不久会出现故障。 “正在维修”说明元素正在接受配置、维护、清洁或其他方式的管理。 “无连接”表明监视系统了解此元素，但是一直无法与其建立通信。 “通信中断”表明 ManagedSystem 元素已知存在，并且过去曾成功建立联系，但是现在不可访问。 “已停止”和“已中止”类似，只是前者暗示正常有序地停止，而后者暗示紧急停止，元素的状态和配置可能需要更新。 “休止”表明元素处于非活动状态或静态。 “支持实体出错”表明此元素可能“良好”，但是此元素所依赖的另一个元素可能出现错误。由于低层网络问题而无法工作的网络服务或端点就属于这种情况。 “已完成”表明该元素已完成操作。此值应与“良好”、“错误”或“已降级”组合使用，使客户端可以确定整个操作是已经良好地完成(已通过)、已经完成但出现错误(出现故障)，还是已经完成但是降级(操作已完成，但是未“良好”地完成或未报告错误)。 “电源模式”表明元素在 Associated PowerManagementService 关联中包含其他电源模式信息。 OperationalStatus 替换 ManagedSystemElement 的 Status 属性，以便提供一致的枚举方法，满足实现数组属性的需要，从而可以从现在\的环境迁移到未来的环境。以前未进行此更改是因为需要 DEPRECATED 限定符。由于在管理应用程序中广泛使用现有的 Status 属性，强烈建议提供程序/工具同时提供 Status 和 OperationalStatus 属性。此外，OperationalStatus 的第一个值应包含元素的主要状态。如果有 Status 属性，则 Status (由于是单值)也应提供元素的主要状态。 |
Indicates the current statuses of the element. Various operational statuses are defined. Many of the enumeration\'s values are self-explanatory. However, a few are not and are described here in more detail. "Stressed" indicates that the element is functioning, but needs attention. Examples of "Stressed" states are overload, overheated, and so on. "Predictive Failure" indicates that an element is functioning nominally but predicting a failure in the near future. "In Service" describes an element being configured, maintained, cleaned, or otherwise administered. "No Contact" indicates that the monitoring system has knowledge of this element, but has never been able to establish communications with it. "Lost Communication" indicates that the ManagedSystem Element is known to exist and has been contacted successfully in the past, but is currently unreachable. "Stopped" and "Aborted" are similar, although the former implies a clean and orderly stop, while the latter implies an abrupt stop where the state and configuration of the element might need to be updated. "Dormant" indicates that the element is inactive or quiesced. "Supporting Entity in Error" indicates that this element might be "OK" but that another element, on which it is dependent, is in error. An example is a network service or endpoint that cannot function due to lower-layer networking problems. "Completed" indicates that the element has completed its operation. This value should be combined with either OK, Error, or Degraded so that a client can tell if the complete operation Completed with OK (passed), Completed with Error (failed), or Completed with Degraded (the operation finished, but it did not complete OK or did not report an error). "Power Mode" indicates that the element has additional power model information contained in the Associated PowerManagementService association. OperationalStatus replaces the Status property on ManagedSystemElement to provide a consistent approach to enumerations, to address implementation needs for an array property, and to provide a migration path from today\'s environment to the future. This change was not made earlier because it required the deprecated qualifier. Due to the widespread use of the existing Status property in management applications, it is strongly recommended that providers or instrumentation provide both the Status and OperationalStatus properties. Further, the first value of OperationalStatus should contain the primary status for the element. When instrumented, Status (because it is single-valued) should also provide the primary status of the element. |
| 10 | 未知 | Unknown |
| 11 | 其他 | Other |
| 12 | 良好 | OK |
| 13 | 已降级 | Degraded |
| 14 | 已强调 | Stressed |
| 15 | 预测故障 | Predictive Failure |
| 16 | 错误 | Error |
| 17 | 不可恢复的错误 | Non-Recoverable Error |
| 18 | 正在启动 | Starting |
| 19 | 正在停止 | Stopping |
| 20 | 已停止 | Stopped |
| 21 | 正在维修 | In Service |
| 22 | 无连接 | No Contact |
| 23 | 通信中断 | Lost Communication |
| 24 | 已中止 | Aborted |
| 25 | 休止 | Dormant |
| 26 | 支持实体出错 | Supporting Entity in Error |
| 27 | 已完成 | Completed |
| 28 | 电源模式 | Power Mode |
| 29 | DMTF 保留 | DMTF Reserved |
| 30 | 供应商保留 | Vendor Reserved |
| 31 | 描述各种 OperationalStatus 数组值的字符串。例如，如果为 OperationalStatus 分配的值为“正在停止”，则此属性可能包含对对象停止原因的描述。请注意，此数组中的项与 OperationalStatus 中处于相同数组索引的项相关。 | Strings describing the various OperationalStatus array values. For example, if "Stopping" is the value assigned to OperationalStatus, then this property may contain an explanation as to why an object is being stopped. Note that entries in this array are correlated with those at the same array index in OperationalStatus. |
| 32 | 表明对象当前状态的字符串。定义了各种工作和非工作状态。此属性替代 OperationalStatus 被弃用，后者在枚举中包括相同的语义。此更改出于以下 3 个原因: 1) 以数组的形式更准确地定义状态。当某个状态实际上是多值属性时(例如，某个元素的状态可能是“良好”和“已停止”)，这种定义便能克服通过单个值描述状态的局限性。 2) MaxLen 为 10 的限制太严格，无法清楚地描述枚举值。 3) 对 uint16 数据类型的更改在定义 CIM V2.0 时已讨论。但是，现有的 V1.0 使用的是字符串属性，不希望修改其代码。因此，Status 归属到 Schema 中。使用 Deprecated 限定符可以保留现有的属性，同时允许使用 OperationalStatus 改进定义。 |
A string indicating the current status of the object. Various operational and non-operational statuses are defined. This property is deprecated in lieu of OperationalStatus, which includes the same semantics in its enumeration. This change is made for 3 reasons: 1) Status is more correctly defined as an array. This definition overcomes the limitation of describing status using a single value, when it is really a multi-valued property (for example, an element might be OK AND Stopped. 2) A MaxLen of 10 is too restrictive and leads to unclear enumerated values. 3) The change to a uint16 data type was discussed when CIM V2.0 was defined. However, existing V1.0 implementations used the string property and did not want to modify their code. Therefore, Status was grandfathered into the Schema. Use of the deprecated qualifier allows the maintenance of the existing property, but also permits an improved definition using OperationalStatus. |
| 33 | 表明元素当前的运行状况。此属性表明此元素(不必是其子组件)的运行状况。可能的值为 0 到 30，其中 5 意味着元素完全正常，30 意味着元素完全无法工作。定义的 Continuum 如下: “不可恢复的错误”(30) - 元素以失败而告终，并且无法恢复。此元素提供的所有功能均已丧失。 “关键故障”(25) - 元素无法工作，并且可能无法恢复。 “主要故障”(20) - 元素失败。此组件的部分或全部功能可能已降级或无法使用。 “次要故障”(15) - 所有功能均可以使用，但是有些功能可能已降级。 “已降级/警告”(10) - 元素正在工作，并且提供所有功能。但是元素未实现最佳效果。例如，元素可能未实现最佳性能或报告了可恢复的错误。 “良好”(5) - 元素功能完全正常，使用正常的操作参数工作，没有出现错误。 “未知”(0) - 此时无法报告 HealthState。 DMTF 在 Continuum 中为以后增加 HealthStates 保留了未用的部分。 |
Indicates the current health of the element. This attribute expresses the health of this element but not necessarily that of its subcomponents. The possible values are 0 to 30, where 5 means the element is entirely healthy and 30 means the element is completely non-functional. The following continuum is defined: "Non-recoverable Error" (30) - The element has completely failed, and recovery is not possible. All functionality provided by this element has been lost. "Critical Failure" (25) - The element is non-functional and recovery might not be possible. "Major Failure" (20) - The element is failing. It is possible that some or all of the functionality of this component is degraded or not working. "Minor Failure" (15) - All functionality is available but some might be degraded. "Degraded/Warning" (10) - The element is in working order and all functionality is provided. However, the element is not working to the best of its abilities. For example, the element might not be operating at optimal performance or it might be reporting recoverable errors. "OK" (5) - The element is fully functional and is operating within normal operational parameters and without error. "Unknown" (0) - The implementation cannot report on HealthState at this time. DMTF has reserved the unused portion of the continuum for additional HealthStates in the future. |
| 34 | 已降级/警告 | Degraded/Warning |
| 35 | 次要故障 | Minor failure |
| 36 | 主要故障 | Major failure |
| 37 | 关键故障 | Critical failure |
| 39 | CommunicationStatus 表明检测与基础 ManagedElement 的通信能力。CommunicationStatus 包含以下某个值: 未知、无、通信良好、通信中断或无连接。 如果返回空值，则表明该检测(提供程序)未实现此属性。 “未知”表明该实现一般情况下能返回此属性，但是当前无法返回。 “不可用”表明该检测(提供程序)能返回此属性的值，但是一直无法为此硬件返回此属性的值，或者由于此属性并不提供任何有意义的信息(例如某个属性只是为了向另一个属性添加附加信息)，因而有意未使用此属性。 “通信良好”表明已与元素建立了通信，但是未传输任何服务质量信息。 “无连接”表明监视系统了解此元素，但是一直无法与其建立通信 “通信中断”表明 ManagedElement 元素已知存在，并且过去曾成功建立联系，但是现在不可访问。 |
CommunicationStatus indicates the ability of the instrumentation to communicate with the underlying ManagedElement. CommunicationStatus consists of one of the following values: Unknown, None, Communication OK, Lost Communication, or No Contact. A Null return indicates the implementation (provider) does not implement this property. "Unknown" indicates the implementation is in general capable of returning this property, but is unable to do so at this time. "Not Available" indicates that the implementation (provider) is capable of returning a value for this property, but not ever for this particular piece of hardware/software or the property is intentionally not used because it adds no meaningful information (as in the case of a property that is intended to add additional info to another property). "Communication OK " indicates communication is established with the element, but does not convey any quality of service. "No Contact" indicates that the monitoring system has knowledge of this element, but has never been able to establish communications with it. "Lost Communication" indicates that the Managed Element is known to exist and has been contacted successfully in the past, but is currently unreachable. |
| 40 | 不可用 | Not Available |
| 41 | 通信良好 | Communication OK |
| 42 | DetailedStatus 作为 PrimaryStatus 的补充，可提供其他状态详细信息。它包含以下某个值: 不可用、无其他信息、已强调、预测故障、错误、不可恢复的错误或支持实体出错。DetailedStatus 是对元素 PrimaryStatus 的扩充。 如果返回空值，则表明该检测(提供程序)未实现此属性。 “不可用”表明该检测(提供程序)能返回此属性的值，但是一直无法为此硬件返回此属性的值，或者由于此属性并不提供任何有意义的信息(例如某个属性只是为了向另一个属性添加附加信息)，因而有意未使用此属性。 “无其他信息”表明元素如 PrimaryStatus 的“良好”状态所示在正常工作。 “已强调”表明元素正在工作，但是需要注意。过载、过热等都属于“强调”状态。 “已强调”表明元素正在工作，但是需要注意。过载、过热等都属于“强调”状态。 “预测故障”表明元素表面上正在工作，但是预计不久会出现故障。 “正在维修”说明元素正在接受配置、维护、清洁或其他方式的管理。 “无法恢复的错误”表明此元素出现需要人工干预的错误。 “支持实体出错”表明此元素可能“良好”，但是此元素所依赖的另一个元素可能出现错误。由于低层网络问题而无法工作的网络服务或端点就属于这种情况。 |
DetailedStatus compliments PrimaryStatus with additional status detail. It consists of one of the following values: Not Available, No Additional Information, Stressed, Predictive Failure, Error, Non-Recoverable Error, SupportingEntityInError. Detailed status is used to expand upon the PrimaryStatus of the element. A Null return indicates the implementation (provider) does not implement this property. "Not Available" indicates that the implementation (provider) is capable of returning a value for this property, but not ever for this particular piece of hardware/software or the property is intentionally not used because it adds no meaningful information (as in the case of a property that is intended to add additional info to another property). "No Additional Information" indicates that the element is functioning normally as indicated by PrimaryStatus = "OK". "Stressed" indicates that the element is functioning, but needs attention. Examples of "Stressed" states are overload, overheated, and so on. "Predictive Failure" indicates that an element is functioning normally but a failure is predicted in the near future. "Non-Recoverable Error " indicates that this element is in an error condition that requires human intervention. "Supporting Entity in Error" indicates that this element might be "OK" but that another element, on which it is dependent, is in error. An example is a network service or endpoint that cannot function due to lower-layer networking problems. |
| 43 | 无其他信息 | No Additional Information |
| 44 | OperatingStatus 提供针对元素工作状况的当前状态值，可用于提供有关 EnabledState 值的更多详细信息。当元素从一种状态向另一种状态过渡时，例如元素处于 EnabledState 与 RequestedState 之间的过渡或其他过渡期，OperatingStatus 还可以提供过渡状态信息。 OperatingStatus 包含以下某个值:未知、不可用、正在使用、正在启动、正在停止、已停止、已中止、已休止、已完成、正在迁移、正在向外迁移、正在向内迁移、正在拍摄快照、正在关闭或正在测试 如果返回空值，则表明该检测(提供程序)未实现此属性。 “未知”表明该实现一般情况下能返回此属性，但是当前无法返回。 “无”表明该检测(提供程序)能返回此属性的值，但是一直无法为此硬件返回此属性的值，或者由于此属性并不提供任何有意义的信息(例如某个属性只是为了向另一个属性添加附加信息)，因而有意未使用此属性。 “正在维修”说明元素正在接受配置、维护、清洁或其他方式的管理。 “正在启动”表明元素正在初始化。 “正在停止”表明元素正在进入有序的停止状态。 “已停止”和“已中止”类似，只是前者暗示正常有序地停止，而后者暗示紧急停止，元素的状态和配置可能需要更新。 “休止”表明元素处于非活动状态或静态。 “已完成”表明该元素已完成操作。此值应与 PrimaryStatus 中的“良好”、“错误”或“已降级”组合使用，使客户端可以确定整个操作是已经良好地完成(已通过)、已经完成但出现错误(出现故障)，还是已经完成但是降级(操作已完成，但是未“良好”地完成或未报告错误)。 “正在迁移”表明元素正在宿主元素之间移动。 “正在向内迁移”表明元素正在向某个新的宿主元素移入。 “正在向外迁移”表明元素正在从宿主元素移出。 “正在关闭”表明元素正在进入紧急停止状态。 “正在测试”表明元素正在执行测试功能。 “正在过渡”表明元素处于两种状态之间的过渡期，即该元素目前在前一状态和下一状态中均不完全可用。在没有其他适用的值可以表明到某个特定状态的过渡时，应使用此值。 “正在工作”表明元素正在工作，可以使用。 |
OperatingStatus provides a current status value for the operational condition of the element and can be used for providing more detail with respect to the value of EnabledState. It can also provide the transitional states when an element is transitioning from one state to another, such as when an element is transitioning between EnabledState and RequestedState, as well as other transitional conditions. OperatingStatus consists of one of the following values: Unknown, Not Available, In Service, Starting, Stopping, Stopped, Aborted, Dormant, Completed, Migrating, Emmigrating, Immigrating, Snapshotting. Shutting Down, In Test A Null return indicates the implementation (provider) does not implement this property. "Unknown" indicates the implementation is in general capable of returning this property, but is unable to do so at this time. "None" indicates that the implementation (provider) is capable of returning a value for this property, but not ever for this particular piece of hardware/software or the property is intentionally not used because it adds no meaningful information (as in the case of a property that is intended to add additional info to another property). "Servicing" describes an element being configured, maintained, cleaned, or otherwise administered. "Starting" describes an element being initialized. "Stopping" describes an element being brought to an orderly stop. "Stopped" and "Aborted" are similar, although the former implies a clean and orderly stop, while the latter implies an abrupt stop where the state and configuration of the element might need to be updated. "Dormant" indicates that the element is inactive or quiesced. "Completed" indicates that the element has completed its operation. This value should be combined with either OK, Error, or Degraded in the PrimaryStatus so that a client can tell if the complete operation Completed with OK (passed), Completed with Error (failed), or Completed with Degraded (the operation finished, but it did not complete OK or did not report an error). "Migrating" element is being moved between host elements. "Immigrating" element is being moved to new host element. "Emigrating" element is being moved away from host element. "Shutting Down" describes an element being brought to an abrupt stop. "In Test" element is performing test functions. "Transitioning" describes an element that is between states, that is, it is not fully available in either its previous state or its next state. This value should be used if other values indicating a transition to a specific state are not applicable. "In Service" describes an element that is in service and operational. |
| 45 | 正在服务 | Servicing |
| 46 | 正在迁移 | Migrating |
| 47 | 正在迁出 | Emigrating |
| 48 | 正在迁入 | Immigrating |
| 49 | 正在快照 | Snapshotting |
| 50 | 正在关闭 | Shutting Down |
| 51 | 正在测试 | In Test |
| 52 | 正在转换 | Transitioning |
| 53 | PrimaryStatus 提供了一个高级状态值，用来对应状态的红-黄-绿三种类型展示。该值应与 DetailedStatus 一同使用，这样才能提供 ManagedElement 及其子组件的高级和详细的运行状况状态。 PrimaryStatus 的值包括: 未知、正常、降级或错误。“未知”表示执行通常能够返回此属性，但当时还无法返回。 “正常”表示 ManagedElement 运行正常。 “降级”表示 ManagedElement 运行在正常级别之下。 “错误”表示 ManagedElement 出现了错误状况。 |
PrimaryStatus provides a high level status value, intended to align with Red-Yellow-Green type representation of status. It should be used in conjunction with DetailedStatus to provide high level and detailed health status of the ManagedElement and its subcomponents. PrimaryStatus consists of one of the following values: Unknown, OK, Degraded or Error. "Unknown" indicates the implementation is in general capable of returning this property, but is unable to do so at this time. "OK" indicates the ManagedElement is functioning normally. "Degraded" indicates the ManagedElement is functioning below normal. "Error" indicates the ManagedElement is in an Error condition. |
| 54 | CIM_ManagedSystemElement 是 System Element 层次结构的基类。任何可辨别的系统组件都能包含在此类中。系统组件的示例包括: - 应用程序服务器、数据库和应用程序等软件组件 - 文件、进程和线程等操作系统组件 - 磁盘驱动器、控制器、处理器和打印机等设备组件 - 芯片和卡等物理组件。 |
CIM_ManagedSystemElement is the base class for the System Element hierarchy. Any distinguishable component of a System is a candidate for inclusion in this class. Examples of system components include: - software components such as application servers, databases, and applications - operating system components such as files, processes, and threads - device components such as disk drives, controllers, processors, and printers - physical components such as chips and cards. |
| 55 | 2.22.0 | 2.22.0 |
| 56 | CIM_LogicalElement 是所有代表抽象系统组件(例如文件、进程或 LogicalDevices)的系统组件的基类。 | CIM_LogicalElement is a base class for all the components of a System that represent abstract system components, such as Files, Processes, or LogicalDevices. |
| 57 | 2.6.0 | 2.6.0 |
| 58 | 提供程序的名称 | The name of the provider |
| 59 | GUID，计算机上安装的提供程序的唯一 ID。 | Guid, the unique id of the provider installed on the computer. |
| 60 | 提供程序的自动记录程序(属于自动记录程序配置时)。 | The Autologger of the provider, when part of a Autologger configuration. |
| 61 | 提供程序的会话(属于会话时)。 | The session of the provider, when part of a session. |
| 62 | 事件捕获的最高事件级别。 | The maximum event level for the event capture. |
| 63 | 为事件捕获指定的 MatchAnyKeyword 掩码。 | The MatchAnyKeyword mask specified for the event capture. |
| 64 | 为事件捕获指定的 MatchAllKeyword 掩码。 | The MatchAllKeyword mask specified for the event capture. |
| 65 | ETW 跟踪提供程序的属性标志。 | Property flags of the ETW trace provider. |
| 66 | 此类用于封装计算机上的 ETW 跟踪提供程序。 | This class encapsulates an ETW Trace provider on a computer. |
| 67 | 1.0 | 1.0 |
| 68 | 要获取的 ETW 跟踪会话的名称。 | Name of the ETW trace session to get. |
| 69 | ETW 跟踪会话的日志文件模式。 | Log file mode of ETW trace session. |
| 70 | ETW 跟踪会话缓冲区大小，以 KB 为单位。 | ETW trace session buffer size in KB. |
| 71 | ETW 跟踪会话缓冲区的最小数目。 | Minimum number of buffers of ETW trace session. |
| 72 | ETW 跟踪会话缓冲区的最大数目。 | Maximum number of buffers of ETW trace session. |
| 73 | ETW 跟踪会话刷新捕获缓冲区的超时值。 | Timeout value for ETW trace session to flush capture buffer. |
| 74 | ETW 会话时钟类型。 | ETW session clock types. |
| 75 | 性能计数器值(高分辨率) | Performance counter value (high resolution) |
| 76 | 系统计时器 | System timer |
| 77 | CPU 周期计数器 | CPU cycle counter |
| 78 | 用于记录事件的文件的最大大小 | Maximum size of the file used to log events |
| 79 | 事件捕获跟踪要写入到的本地文件名。 | Local filename to which event capture traces will be written to. |
| 80 | 将指定的 ETW 跟踪会话的日志文件发送到配置的远程共享。 | Send log file of the specified ETW trace session to configured remote share. |
| 81 | 实时 ETW 跟踪会话类。 | Live ETW trace session class. |
| 82 | 新自动记录程序会话配置的名称。 | Name of new autologger session configuration. |
| 83 | 每个缓冲区的大小，以 KB 为单位。应小于 1 MB。 | The size of each buffer, in kilobytes. Should be less than one megabyte. |
| 84 | 记录每个事件的时间戳时使用的计时器。 | The timer to use when logging the time stamp for each event. |
| 85 | 若要禁用实时持久性，请将此值设置为 1。 | To disable real time persistence, set this value to 1. |
| 86 | ETW 创建的日志文件实例的最大数目。 | The maximum number of instances of the log file that ETW creates. |
| 87 | 日志文件的完全限定路径。默认值为 %SystemRoot%\System32\LogFiles\WMI\.etl。 | The fully qualified path of the log file. Default is %SystemRoot%\System32\LogFiles\WMI\.etl. |
| 88 | 强制刷新跟踪缓冲区的频率，以秒为单位。 | How often, in seconds, the trace buffers are forcibly flushed. |
| 89 | 自动记录程序会话配置 ID。 | Autologger session configuration ID. |
| 90 | 指定一种或多种日志模式，例如 EVENT_TRACE_REAL_TIME_MODE 0x100。每种模式都是一个位域。 | Specify one or more log modes, such as EVENT_TRACE_REAL_TIME_MODE 0x100. Each mode is a bit field. |
| 91 | 在创建新的日志文件之前现有日志文件的最大大小，以 MB 为单位。默认值为 100 MB。 | Maximum size in MByte of log file before a new one created. Default is 100 MB. |
| 92 | 1: 启动时创建一个 ETW 跟踪会话; 0: 启动时不创建此类会话。 | 1: create an ETW trace session at boot time; 0: otherwise. |
| 93 | 自动记录程序的启动状态; 否则为 win32 错误代码。 | The startup status of the AutoLogger; Otherwise win32 error code. |
| 94 | 自动记录程序会话配置类。 | Autologger session configuration class. |
| 5001 | 此计算机上已有名为“%1!s!”的活动跟踪会话。 | There is already an active tracing session on this computer with the name '%1!s!'. |
| 5002 | 此计算机上没有名为“%1!s!”的活动跟踪会话。 | There are no active tracing sessions on this computer with the name '%1!s!'. |
| 5003 | 拒绝访问。此操作需要管理员特权。 | Access Denied. This operation requires administrator privileges. |
| 5004 | 有另一个活动跟踪会话写入到所提供的 LocalFilePath，或者路径无效:“%1!s!”。 | There is another active tracing session writing to the provided LocalFilePath, or the path is invalid: '%1!s!'. |
| 5005 | 无法启动会话“%1!s!”。StartTrace 失败，显示错误 0x%2!x!。 | Failed to start session '%1!s!'. StartTrace failed with error 0x%2!x!. |
| 5006 | 无法更新会话“%1!s!”。ControlTrace 失败，显示错误 0x%2!x!。 | Failed to update session '%1!s!'. ControlTrace failed with error 0x%2!x!. |
| 5007 | 无法为会话“%1!s!”启用或禁用提供程序。EnableTraceEx2 失败，显示错误 0x%2!x!。 | Failed to enable or disable provider to session '%1!s!'. EnableTraceEx2 failed with error 0x%2!x!. |
| 5008 | 指定的提供程序 GUID 无法转换为有效的 GUID (%1!s!)。 | The specified provider GUID could not be converted into a valid GUID (%1!s!). |
| 5009 | 无法在注册表中打开自动记录器配置。RegOpenKeyEx 失败，显示错误 0x%1!x!。 | Failed to open autologger configuration in the registry. RegOpenKeyEx failed with error 0x%1!x!. |
| 5010 | 无法将提供程序添加到注册表中的自动记录器配置。RegCreateKeyExW 失败，显示错误 0x%1!x!。 | Failed to add provider to the autologger configuration in the registry. RegCreateKeyExW failed with error 0x%1!x!. |
| 5011 | 无法为自动记录器“%3!s!”的提供程序“%2!s!”设置注册表值“%1!s!”。RegSetKeyValueW 失败，显示错误 0x%4!x!。 | Failed to set the registry value '%1!s!' for provider '%2!s!' for autologger '%3!s!'. RegSetKeyValueW failed with error 0x%4!x!. |
| 5012 | 无法删除自动记录器 %2!s! 的提供程序“%1!s!”的注册表项。RegDeleteTreeW 失败，显示错误 0x%3!x!。 | Failed to delete the registry key for provider '%1!s!' for autologger %2!s!. RegDeleteTreeW failed with error 0x%3!x!. |
| 5013 | 缓冲模式与 LocalFilePath 设置不兼容。 | Buffering mode is not compatible with setting LocalFilePath. |
| 5014 | 缓冲模式与其他文件模式不兼容。 | Buffering mode is not compatible with other file modes. |
| 5015 | 顺序文件模式与循环文件模式不兼容。 | Sequential file mode is not compatible with circular file mode. |
| 5016 | 全局序列号模式与本地序列号模式不兼容。 | Global sequence number mode is not compatiable with local sequence number mode. |
| 5017 | LocalFilePath 是当前 LogFileMode (0x%1!x!)所必需的。 | LocalFilePath is required for the current LogFileMode (0x%1!x!). |
| 5018 | 循环文件模式与追加文件模式不兼容。 | Circular file mode is not compatible with append file mode. |
| 5019 | MaximumFileSize 是当前 LogFileMode (0x%1!x!)所必需的。 | MaximumFileSize is required for the current LogFileMode (0x%1!x!). |
| 5020 | 预分配文件模式需要设置 MaximumFileSize。 | Preallocate file mode requires MaximumFileSize to be set. |
| 5021 | 预分配文件模式与 newfile 或追加文件模式不兼容。 | Preallocate file mode is not compatible with either newfile or append file mode. |
| 5022 | 新会话不允许使用不可停止模式。 | Nonstoppable mode is not allowed for new sessions. |
| 5023 | 一次只能指定一种混合关闭模式。 | Only one hybrid shutdown mode can be specified at a time. |
| 5024 | 循环文件模式与 newfile 文件模式不兼容。 | Circular file mode is not compatible with newfile file mode. |
| 5025 | Newfile 文件模式与系统记录器模式不兼容。 | Newfile file mode is not compatible with system logger mode. |
| 5026 | Newfile 文件模式与追加文件模式不兼容。 | Newfile file mode is not compatible with append file mode. |
| 5027 | 系统记录器不能使用分页内存。 | System loggers cannot use paged memory. |
| 5028 | 只有缓冲模式才支持压缩。 | Compression is only supported for buffering mode. |
| 5029 | 不支持重新记录模式。 | Relog mode is not supported. |
| 5030 | 不支持专用进程内模式。 | Private in-proc mode is not supported. |
| 5031 | 需要会话名称。 | A session name is required. |
| 5032 | 会话名称过长。会话名称必须短于 1024 个字符。 | The session name is too long. Session names must be shorter than 1024 characters. |
| 5033 | LocalFilePath 过长。文件路径必须短于 1024 个字符。 | LocalFilePath is too long. File paths must be shorter than 1024 characters. |
| 5034 | DestinationFolder 必须设置为文件模式跟踪会话的输出文件夹或缓冲模式跟踪会话的完整输出文件路径。 | DestinationFolder must be set to an output folder for file mode tracing sessions or to a full output file path for buffering mode tracing sessions. |
| 5035 | 无法确认更改。未做任何更改。 | Failed to confirm changes. No changes have been made. |
| 5036 | 因分配失败而处理失败。内存不足。 | Processing failed due to a failed allocation. Out of memory. |
| 5037 | 无法获取活动跟踪会话的列表。QueryAllTraces 失败，显示错误 0x%1!x!。 | Failed to get the list of active tracing sessions. QueryAllTraces failed with error 0x%1!x!. |
| 5038 | 会话“%1!s!”未配置为记录到文件，并且不是缓冲模式会话。 | Session '%1!s!' is not configured to log to a file and is not a buffering mode session. |
| 5039 | DestinationFolder 可能过长或文件路径无效:“%1!s!”。 | DestinationFolder is may too long or an invalid file path: '%1!s!'. |
| 5040 | DestinationFolder 可能过长或文件路径无效。最终输出文件路径无效:“%1!s!\%2!s!”。 | DestinationFolder is may too long or an invalid file path. The final output file path was invalid: '%1!s!\%2!s!'. |
| 5041 | 跟踪会话的新文件名可能过长或文件路径无效。最终输出文件路径无效:“%1!s!\%2!s!”。 | The new file name for the tracing session may too long or an invalid file path. The final output file path was invalid: '%1!s!\%2!s!'. |
| 5042 | 在缓冲模式会话(“%1!s!”)上调用发送时，DestinationFolder 必须是文件路径，而不是目录。 | DestinationFolder must be a file path, not a directory, when calling Send on a buffering mode session ('%1!s!'). |
| 5043 | 不能同时指定 SessionName 和 AutologgerName。 | SessionName and AutologgerName cannot both be specified at the same time. |
| 5044 | 必须指定 SessionName 或 AutologgerName。 | SessionName or AutologgerName must be specified. |
| 5045 | 在此计算机上已有名为“%1!s!”的自动记录器。 | There is already an autologger on this computer with the name '%1!s!. |
| 5046 | 已为名为“%2!s!”的自动记录器启用提供程序 %1!s!。 | Provider %1!s! is already enabled to the autologger named %2!s!. |
| 5047 | 无法枚举此计算机上的已注册提供程序列表。EnumerateTraceGuidsEx(TraceGuidQueryList) 失败，显示错误 0x%1!x!。 | Failed to enumerate the list of registered providers on this computer. EnumerateTraceGuidsEx(TraceGuidQueryList) failed with error 0x%1!x!. |
| 5048 | 无法枚举为其启用提供程序“%1!s!”的会话的列表。EnumerateTraceGuidsEx(TraceGuidQueryInfo) 失败，显示错误 0x%1!x!。 | Failed to enumerate the list of sessions provider '%1!s!' is enabled to. EnumerateTraceGuidsEx(TraceGuidQueryInfo) failed with error 0x%1!x!. |
| 5049 | 无法获取会话 ID %1!hu! 的会话属性。ControlTrace 失败，显示错误 0x%2!x!。 | Failed to get the session properties for session ID %1!hu!. ControlTrace failed with error 0x%2!x!. |
| 5050 | 无法枚举注册表中的自动记录器配置。RegEnumKeyExW 失败，显示错误 0x%1!x!。 | Failed to enumerate autologger configuration in the registry. RegEnumKeyExW failed with error 0x%1!x!. |
| 5201 | 启动新跟踪会话 | Start new tracing session |
| 5202 | 更新跟踪会话 | Update tracing session |
| 5203 | 停止跟踪会话 | Stop tracing session |
| 5204 | 将缓冲模式跟踪会话刷新到磁盘 | Flush buffering mode tracing session to disk |
| 5205 | 将跟踪会话切换到新的输出文件 | Switch tracing session to a new output file |
| 5206 | 将原始 ETL 复制到目标文件夹 | Copy original ETL to destination folder |
| 5207 | 删除原始 ETL 文件 | Delete original ETL file |
| 5208 | 为会话“%2!s!”启用提供程序“%1!s!” | Enable provider '%1!s!' to session '%2!s!' |
| 5209 | 从会话“%2!s!”禁用提供程序“%1!s!” | Disable provider '%1!s!' from session '%2!s!' |
| 5210 | 在会话“%2!s!”上修改提供程序“%1!s!”的启用设置 | Modify enablement for provider '%1!s!' on session '%2!s!' |
| 5211 | 将提供程序“%1!s!”添加到自动记录器“%2!s!” | Add provider '%1!s!' to autologger '%2!s!' |
| 5212 | 从自动记录器“%2!s!”中删除提供程序“%1!s!” | Delete provider '%1!s!' from autologger '%2!s!' |
| 5213 | 在自动记录器“%2!s!”上修改提供程序“%1!s!”的启用设置 | Modify enablement for provider '%1!s!' on autologger '%2!s!' |
| File Description: | 用于 ETW 的 WMI 提供程序 |
| File Version: | 10.0.15063.0 (WinBuild.160101.0800) |
| Company Name: | Microsoft Corporation |
| Internal Name: | "EventTracingManagement.dll" |
| Legal Copyright: | © Microsoft Corporation. All rights reserved. |
| Original Filename: | "EventTracingManagement.dll".mui |
| Product Name: | Microsoft® Windows® Operating System |
| Product Version: | 10.0.15063.0 |
| Translation: | 0x804, 1200 |