| 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 for this HRESULT. A reliable investigation preserves the producing action before any cleanup runs for this HRESULT. The rejected object or state is trace-profile reference, and the specific boundary is that a scenario or API request named a trace profile that is absent from the active configuration set for this HRESULT. Later service errors should not replace this first result in the incident record for this HRESULT.
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 for this HRESULT. Mixing authoring files or package versions can make an otherwise valid identifier unusable for this HRESULT. Record the configuration package or scenario generation together with the Windows build; otherwise a repaired file can be tested against a stale in-memory graph and appear to fail for the same reason for this HRESULT.
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 |
| Decisive evidence | 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 |
The AllStat message names the immediate condition as “Requested trace profile cannot be found” for this HRESULT. In practice, the useful extension is to ask whether the request was rejected before any side effect, after partial setup, or during cleanup for this HRESULT. Verify the existence and ownership of the expected output—session, directory, process, result object or emitted event—rather than assuming the message describes the final system state for this HRESULT.
Reproduce without collateral changes
- Associate this result with one request, one scenario version and one service process ID for this HRESULT.
- Save profile ID, referencing scenario/action, package version, architecture, target SKU and configuration-load events and the first lower-level HRESULT if one exists for this HRESULT.
- Change no policy, provider set or destination except for this test: substitute a known profile ID without changing the scenario transition that invokes it for this HRESULT.
- Compare the produced artifacts and operational events, not only the top-level return Value.
The most informative neighbor is UTC_E_SCENARIODEF_NOT_FOUND. The distinction is concrete: UTC_E_SCENARIODEF_NOT_FOUND means the outer scenario itself cannot be found for this HRESULT. Keeping both symbolic names in logs prevents a broad “DiagTrack error” bucket from hiding whether the failure occurred during parsing, authorization, resource acquisition, execution or teardown for this HRESULT.
Configuration-generation check
Hash the scenario, rules and referenced profile files used for this HRESULT, 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 for this HRESULT.
Fix the contract
Install the matching configuration package or correct the reference to an existing profile for this HRESULT. Apply that change only to the owning boundary for this HRESULT. A successful repair must make the controlled case cross this boundary while retaining the intended policy, trace providers, destination and security context for this HRESULT.
Avoid broad registry resets or global service-policy changes until the single-owner comparison has been run for this HRESULT. They can hide the original configuration generation without proving the contract was corrected for this HRESULT.
- the same request now produces its documented success or nonfatal status without a second hidden retry
- the operational log shows one coherent request lifetime and no orphaned action, timer, process or trace session
- teardown followed by a second run does not reuse stale state or recreate trace-profile reference
- the nearby condition remains distinguishable: UTC_E_SCENARIODEF_NOT_FOUND means the outer scenario itself cannot be found
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.