| Previous | Next |
| UTC_E_TRACE_MIN_DURATION_REQUIREMENT_NOT_MET | UTC_E_GETFILE_FILE_PATH_NOT_APPROVED |
UTC_E_EXCLUSIVITY_NOT_AVAILABLE
Identify the owning component: exclusive trace resource
UTC_E_EXCLUSIVITY_NOT_AVAILABLE (0x87C5102D) is a Universal Telemetry Client result from the ETW trace-session control layer. Correlate this HRESULT with the exact request attempt that returned it. The relevant state is exclusive trace resource: a profile marked exclusive could not start because a higher-priority trace already owns the exclusive resource. This identifies a specific UTC/DiagTrack condition, not a general service failure.
The Universal Telemetry Client controls ETW sessions on behalf of diagnostic scenarios. ETW sessions have controller-owned names, in-memory buffers, providers, logging modes and lifetimes; a status at this layer should be correlated with the actual session list rather than inferred from the presence of an ETL file.
What to capture before retrying
| UTC diagnostic field | Value |
|---|---|
| Producing layer | ETW trace-session control |
| Owning state or object | exclusive trace resource |
| Evidence to collect | requested/active profiles, priorities, exclusivity scopes, session GUIDs and controller identities |
| Narrow comparison | stop the owner normally or run a nonexclusive test profile with the same providers |
| Do not confuse with | UTC_E_ALTERNATIVE_TRACE_CANNOT_PREEMPT occurs during alternative-trace replacement logic |
Prove the condition
- Associate this result with one request, one scenario version and one service process ID.
- Save requested/active profiles, priorities, exclusivity scopes, session GUIDs and controller identities and the first lower-level HRESULT if one exists.
- Change no policy, provider set or destination except for this test: stop the owner normally or run a nonexclusive test profile with the same providers.
- Compare the produced artifacts and operational events, not only the top-level return value.
Nearby result: UTC_E_ALTERNATIVE_TRACE_CANNOT_PREEMPT — occurs during alternative-trace replacement logic.
Trace-session note
Use an ETW controller view to list session name, GUID, mode, buffers and enabled providers while this result is active. The presence of an ETL file from an earlier run is not proof that the required in-memory session currently exists or is owned by UTC.
Confirm the repair
Schedule captures or redesign provider sharing; do not terminate arbitrary kernel loggers.
Technical references
- Microsoft Open Specifications: Windows error-code registry — reference for ETW trace-session control while interpreting it.
- Microsoft: Universal Telemetry Client configuration diagnosis
- Microsoft: Event Tracing for Windows
- Microsoft: WPR and ETW sessions
Looking for a different code? Search another status or error code.