| Previous | Next |
| UTC_E_SCENARIODEF_NOT_FOUND | UTC_E_FORWARDER_ALREADY_ENABLED |
UTC_E_TRACEPROFILE_NOT_FOUND
Map the code to the scenario graph: trace-profile reference
When UTC_E_TRACEPROFILE_NOT_FOUND (0x87C51006) is returned, the producing layer is DiagTrack scenario-definition processing. A reliable investigation preserves the producing action before any cleanup runs. The rejected object or state is trace-profile reference, and the specific condition is that a scenario or API request named a trace profile that is absent from the active configuration set. Keep this first HRESULT even if a later service call reports another error.
DiagTrack scenarios are configuration-driven state machines. A scenario definition, its diagnostic rules, referenced profiles, triggers and action graph must all come from a compatible configuration generation. Mixing authoring files or package versions can make an otherwise valid identifier unusable.
Data needed for triage
| UTC diagnostic field | Value |
|---|---|
| Owning state or object | trace-profile reference |
| Producing layer | DiagTrack scenario-definition processing |
| Do not confuse with | UTC_E_SCENARIODEF_NOT_FOUND means the outer scenario itself cannot be found |
| Evidence to collect | profile ID, referencing scenario/action, package version, architecture, target SKU and configuration-load events |
| Narrow comparison | substitute a known profile ID without changing the scenario transition that invokes it |
Reproduce without collateral changes
- Associate this result with one request, one scenario version and one service process ID.
- Save profile ID, referencing scenario/action, package version, architecture, target SKU and configuration-load events and the first lower-level HRESULT if one exists.
- Change no policy, provider set or destination except for this test: substitute a known profile ID without changing the scenario transition that invokes it.
- Compare the produced artifacts and operational events, not only the top-level return value.
Nearby result: UTC_E_SCENARIODEF_NOT_FOUND — means the outer scenario itself cannot be found.
Configuration-generation check
Hash the scenario, rules and referenced profile files used and record the UTC process start time. If files changed after the process loaded them, restart only after preserving the prior generation so the comparison remains auditable.
Fix the contract
Install the matching configuration package or correct the reference to an existing profile.
Technical references
- Microsoft Open Specifications: Windows error-code registry — reference for DiagTrack scenario-definition processing while interpreting this result.
- Microsoft: Universal Telemetry Client configuration diagnosis
- Microsoft: UniversalTelemetryClient operational-log guidance
- Microsoft: Windows Event Log query schema
Looking for a different code? Search another status or error code.