| File name: | EventTracingManagement.dll.mui |
| Size: | 47104 byte |
| MD5: | 545aca9d8c4e5be1456907090cffca7b |
| SHA1: | 1a13c99b4ea0de7961f98f1a0cbd8a241b41252c |
| SHA256: | 3864630b8882d3b2fb019db782344dd26f882f428b2e6a818752e6895e5d1e0f |
| Operating systems: | Windows 10 |
| Extension: | MUI |
If an error occurred or the following message in Portuguese 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 | Portuguese | English |
|---|---|---|
| 1 | 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. |
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 | The Caption property is a short textual description (one- line string) of the object. | The Caption property is a short textual description (one- line string) of the object. |
| 3 | The Description property provides a textual description of the object. | The Description property provides a textual description of the object. |
| 4 | 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. |
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 is an abstract class that provides a common superclass (or top of the inheritance tree) for the non-association classes in the CIM Schema. | 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. | A datetime value that indicates when the object was installed. Lack of a value does not indicate that the object is not installed. |
| 8 | 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. | 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 | 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. |
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 | Unknown |
| 11 | Other | Other |
| 12 | OK | OK |
| 13 | Degraded | Degraded |
| 14 | Stressed | Stressed |
| 15 | Predictive Failure | Predictive Failure |
| 16 | Error | Error |
| 17 | Non-Recoverable Error | Non-Recoverable Error |
| 18 | Starting | Starting |
| 19 | Stopping | Stopping |
| 20 | Stopped | Stopped |
| 21 | In Service | In Service |
| 22 | No Contact | No Contact |
| 23 | Lost Communication | Lost Communication |
| 24 | Aborted | Aborted |
| 25 | Dormant | Dormant |
| 26 | Supporting Entity in Error | Supporting Entity in Error |
| 27 | Completed | Completed |
| 28 | Power Mode | Power Mode |
| 29 | DMTF Reserved | DMTF Reserved |
| 30 | Vendor Reserved | Vendor Reserved |
| 31 | 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. | 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 | 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. |
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 | 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. |
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 | Degraded/Warning |
| 35 | Minor failure | Minor failure |
| 36 | Major failure | Major failure |
| 37 | Critical failure | Critical failure |
| 38 | Non-recoverable error | Non-recoverable error |
| 39 | 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. |
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 | Not Available |
| 41 | Communication OK | Communication OK |
| 42 | 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. |
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 | No Additional Information |
| 44 | 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. |
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 | Servicing |
| 46 | Migrating | Migrating |
| 47 | Emigrating | Emigrating |
| 48 | Immigrating | Immigrating |
| 49 | Snapshotting | Snapshotting |
| 50 | Shutting Down | Shutting Down |
| 51 | In Test | In Test |
| 52 | Transitioning | Transitioning |
| 53 | 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. |
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 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. |
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 is a base class for all the components of a System that represent abstract system components, such as Files, Processes, or 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 | The name of the provider |
| 59 | Guid, the unique id of the provider installed on the computer. | Guid, the unique id of the provider installed on the computer. |
| 60 | The Autologger of the provider, when part of a Autologger configuration. | The Autologger of the provider, when part of a Autologger configuration. |
| 61 | The session of the provider, when part of a session. | The session of the provider, when part of a session. |
| 62 | The maximum event level for the event capture. | The maximum event level for the event capture. |
| 63 | The MatchAnyKeyword mask specified for the event capture. | The MatchAnyKeyword mask specified for the event capture. |
| 64 | The MatchAllKeyword mask specified for the event capture. | The MatchAllKeyword mask specified for the event capture. |
| 65 | Property flags of the ETW trace provider. | Property flags of the ETW trace provider. |
| 66 | This class encapsulates an ETW Trace provider on a computer. | This class encapsulates an ETW Trace provider on a computer. |
| 67 | 1.0 | 1.0 |
| 68 | Name of the ETW trace session to get. | Name of the ETW trace session to get. |
| 69 | Log file mode of ETW trace session. | Log file mode of ETW trace session. |
| 70 | ETW trace session buffer size in KB. | ETW trace session buffer size in KB. |
| 71 | Minimum number of buffers of ETW trace session. | Minimum number of buffers of ETW trace session. |
| 72 | Maximum number of buffers of ETW trace session. | Maximum number of buffers of ETW trace session. |
| 73 | Timeout value for ETW trace session to flush capture buffer. | Timeout value for ETW trace session to flush capture buffer. |
| 74 | ETW session clock types. | ETW session clock types. |
| 75 | Performance counter value (high resolution) | Performance counter value (high resolution) |
| 76 | System timer | System timer |
| 77 | CPU cycle counter | CPU cycle counter |
| 78 | Maximum size of the file used to log events | Maximum size of the file used to log events |
| 79 | Local filename to which event capture traces will be written to. | Local filename to which event capture traces will be written to. |
| 80 | Send log file of the specified ETW trace session to configured remote share. | Send log file of the specified ETW trace session to configured remote share. |
| 81 | Live ETW trace session class. | Live ETW trace session class. |
| 82 | Name of new autologger session configuration. | Name of new autologger session configuration. |
| 83 | The size of each buffer, in kilobytes. Should be less than one megabyte. | 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. | The timer to use when logging the time stamp for each event. |
| 85 | To disable real time persistence, set this value to 1. | To disable real time persistence, set this value to 1. |
| 86 | The maximum number of instances of the log file that ETW creates. | The maximum number of instances of the log file that ETW creates. |
| 87 | The fully qualified path of the log file. Default is %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. | How often, in seconds, the trace buffers are forcibly flushed. |
| 89 | Autologger session configuration ID. | Autologger session configuration ID. |
| 90 | Specify one or more log modes, such as EVENT_TRACE_REAL_TIME_MODE 0x100. Each mode is a bit field. | Specify one or more log modes, such as EVENT_TRACE_REAL_TIME_MODE 0x100. Each mode is a bit field. |
| 91 | Maximum size in MByte of log file before a new one created. Default is 100 MB. | Maximum size in MByte of log file before a new one created. Default is 100 MB. |
| 92 | 1: create an ETW trace session at boot time; 0: otherwise. | 1: create an ETW trace session at boot time; 0: otherwise. |
| 93 | The startup status of the AutoLogger; Otherwise win32 error code. | The startup status of the AutoLogger; Otherwise win32 error code. |
| 94 | Autologger session configuration class. | Autologger session configuration class. |
| 5001 | There is already an active tracing session on this computer with the name '%1!s!'. | There is already an active tracing session on this computer with the name '%1!s!'. |
| 5002 | There are no active tracing sessions on this computer with the name '%1!s!'. | There are no active tracing sessions on this computer with the name '%1!s!'. |
| 5003 | Access Denied. This operation requires administrator privileges. | Access Denied. This operation requires administrator privileges. |
| 5004 | There is another active tracing session writing to the provided LocalFilePath, or the path is invalid: '%1!s!'. | There is another active tracing session writing to the provided LocalFilePath, or the path is invalid: '%1!s!'. |
| 5005 | Failed to start session '%1!s!'. StartTrace failed with error 0x%2!x!. | Failed to start session '%1!s!'. StartTrace failed with error 0x%2!x!. |
| 5006 | Failed to update session '%1!s!'. ControlTrace failed with error 0x%2!x!. | Failed to update session '%1!s!'. ControlTrace failed with error 0x%2!x!. |
| 5007 | Failed to enable or disable provider to session '%1!s!'. EnableTraceEx2 failed with error 0x%2!x!. | Failed to enable or disable provider to session '%1!s!'. EnableTraceEx2 failed with error 0x%2!x!. |
| 5008 | The specified provider GUID could not be converted into a valid GUID (%1!s!). | The specified provider GUID could not be converted into a valid GUID (%1!s!). |
| 5009 | Failed to open autologger configuration in the registry. RegOpenKeyEx failed with error 0x%1!x!. | Failed to open autologger configuration in the registry. RegOpenKeyEx failed with error 0x%1!x!. |
| 5010 | Failed to add provider to the autologger configuration in the registry. RegCreateKeyExW failed with error 0x%1!x!. | Failed to add provider to the autologger configuration in the registry. RegCreateKeyExW failed with error 0x%1!x!. |
| 5011 | Failed to set the registry value '%1!s!' for provider '%2!s!' for autologger '%3!s!'. RegSetKeyValueW failed with error 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 | Failed to delete the registry key for provider '%1!s!' for autologger %2!s!. RegDeleteTreeW failed with error 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 | Buffering mode is not compatible with setting LocalFilePath. | Buffering mode is not compatible with setting LocalFilePath. |
| 5014 | Buffering mode is not compatible with other file modes. | Buffering mode is not compatible with other file modes. |
| 5015 | Sequential file mode is not compatible with circular file mode. | Sequential file mode is not compatible with circular file mode. |
| 5016 | Global sequence number mode is not compatiable with local sequence number mode. | Global sequence number mode is not compatiable with local sequence number mode. |
| 5017 | LocalFilePath is required for the current 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. | Circular file mode is not compatible with append file mode. |
| 5019 | MaximumFileSize is required for the current LogFileMode (0x%1!x!). | MaximumFileSize is required for the current LogFileMode (0x%1!x!). |
| 5020 | Preallocate file mode requires MaximumFileSize to be set. | Preallocate file mode requires MaximumFileSize to be set. |
| 5021 | Preallocate file mode is not compatible with either newfile or append file mode. | Preallocate file mode is not compatible with either newfile or append file mode. |
| 5022 | Nonstoppable mode is not allowed for new sessions. | Nonstoppable mode is not allowed for new sessions. |
| 5023 | Only one hybrid shutdown mode can be specified at a time. | Only one hybrid shutdown mode can be specified at a time. |
| 5024 | Circular file mode is not compatible with newfile file mode. | Circular file mode is not compatible with newfile file mode. |
| 5025 | Newfile file mode is not compatible with system logger mode. | Newfile file mode is not compatible with system logger mode. |
| 5026 | Newfile file mode is not compatible with append file mode. | Newfile file mode is not compatible with append file mode. |
| 5027 | System loggers cannot use paged memory. | System loggers cannot use paged memory. |
| 5028 | Compression is only supported for buffering mode. | Compression is only supported for buffering mode. |
| 5029 | Relog mode is not supported. | Relog mode is not supported. |
| 5030 | Private in-proc mode is not supported. | Private in-proc mode is not supported. |
| 5031 | A session name is required. | A session name is required. |
| 5032 | The session name is too long. Session names must be shorter than 1024 characters. | The session name is too long. Session names must be shorter than 1024 characters. |
| 5033 | LocalFilePath is too long. File paths must be shorter than 1024 characters. | LocalFilePath is too long. File paths must be shorter than 1024 characters. |
| 5034 | 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. | 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. | Failed to confirm changes. No changes have been made. |
| 5036 | Processing failed due to a failed allocation. Out of memory. | Processing failed due to a failed allocation. Out of memory. |
| 5037 | Failed to get the list of active tracing sessions. QueryAllTraces failed with error 0x%1!x!. | Failed to get the list of active tracing sessions. QueryAllTraces failed with error 0x%1!x!. |
| 5038 | Session '%1!s!' is not configured to log to a file and is not a buffering mode session. | Session '%1!s!' is not configured to log to a file and is not a buffering mode session. |
| 5039 | DestinationFolder is may too long or an invalid file path: '%1!s!'. | DestinationFolder is may too long or an invalid file path: '%1!s!'. |
| 5040 | DestinationFolder is may too long or an invalid file path. The final output file path was invalid: '%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 | 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!'. | 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 | DestinationFolder must be a file path, not a directory, when calling Send on a buffering mode session ('%1!s!'). | DestinationFolder must be a file path, not a directory, when calling Send on a buffering mode session ('%1!s!'). |
| 5043 | SessionName and AutologgerName cannot both be specified at the same time. | SessionName and AutologgerName cannot both be specified at the same time. |
| 5044 | SessionName or AutologgerName must be specified. | SessionName or AutologgerName must be specified. |
| 5045 | There is already an autologger on this computer with the name '%1!s!. | There is already an autologger on this computer with the name '%1!s!. |
| 5046 | Provider %1!s! is already enabled to the autologger named %2!s!. | Provider %1!s! is already enabled to the autologger named %2!s!. |
| 5047 | Failed to enumerate the list of registered providers on this computer. EnumerateTraceGuidsEx(TraceGuidQueryList) failed with error 0x%1!x!. | Failed to enumerate the list of registered providers on this computer. EnumerateTraceGuidsEx(TraceGuidQueryList) failed with error 0x%1!x!. |
| 5048 | Failed to enumerate the list of sessions provider '%1!s!' is enabled to. EnumerateTraceGuidsEx(TraceGuidQueryInfo) failed with error 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 | Failed to get the session properties for session ID %1!hu!. ControlTrace failed with error 0x%2!x!. | Failed to get the session properties for session ID %1!hu!. ControlTrace failed with error 0x%2!x!. |
| 5050 | Failed to enumerate autologger configuration in the registry. RegEnumKeyExW failed with error 0x%1!x!. | Failed to enumerate autologger configuration in the registry. RegEnumKeyExW failed with error 0x%1!x!. |
| 5201 | Start new tracing session | Start new tracing session |
| 5202 | Update tracing session | Update tracing session |
| 5203 | Stop tracing session | Stop tracing session |
| 5204 | Flush buffering mode tracing session to disk | Flush buffering mode tracing session to disk |
| 5205 | Switch tracing session to a new output file | Switch tracing session to a new output file |
| 5206 | Copy original ETL to destination folder | Copy original ETL to destination folder |
| 5207 | Delete original ETL file | Delete original ETL file |
| 5208 | Enable provider '%1!s!' to session '%2!s!' | Enable provider '%1!s!' to session '%2!s!' |
| 5209 | Disable provider '%1!s!' from session '%2!s!' | Disable provider '%1!s!' from session '%2!s!' |
| 5210 | Modify enablement for provider '%1!s!' on session '%2!s!' | Modify enablement for provider '%1!s!' on session '%2!s!' |
| 5211 | Add provider '%1!s!' to autologger '%2!s!' | Add provider '%1!s!' to autologger '%2!s!' |
| 5212 | Delete provider '%1!s!' from autologger '%2!s!' | Delete provider '%1!s!' from autologger '%2!s!' |
| 5213 | Modify enablement for provider '%1!s!' on autologger '%2!s!' | Modify enablement for provider '%1!s!' on autologger '%2!s!' |
| File Description: | WMI Provider for ETW |
| 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: | 0x816, 1200 |