| Previous | Next |
| UTC_E_ACTION_NOT_SUPPORTED_IN_DESTINATION | UTC_E_FILTER_INVALID_TYPE |
UTC_E_FILTER_MISSING_ATTRIBUTE
Map the code to the scenario graph: filter command attribute validation
UTC_E_FILTER_MISSING_ATTRIBUTE (0x87C51045) is a Universal Telemetry Client result from the scenario filter parser and evaluator layer. A reliable investigation preserves the producing action before any cleanup runs. The relevant state is filter command attribute validation: a filter command omits a field required by that command grammar. This identifies a specific UTC/DiagTrack condition, not a general service failure.
UTC filters are typed programs, not plain text searches. Parsing, command validation, name lookup, signature binding and evaluation are distinct phases. Capturing the normalized expression and inferred operand types is essential for a useful diagnosis.
Data needed for triage
| UTC diagnostic field | Value |
|---|---|
| Producing layer | scenario filter parser and evaluator |
| Owning state or object | filter command attribute validation |
| Evidence to collect | command name, supplied attributes, schema version, XML location and parser diagnostics |
| Narrow comparison | add only the required attribute with a valid value and revalidate before replaying events |
| Do not confuse with | UTC_E_FILTER_INVALID_COMMAND means the command name or overall syntax is unrecognized |
Reproduce without collateral changes
- Associate this result with one request, one scenario version and one service process ID.
- Save command name, supplied attributes, schema version, XML location and parser diagnostics and the first lower-level HRESULT if one exists.
- Change no policy, provider set or destination except for this test: add only the required attribute with a valid value and revalidate before replaying events.
- Compare the produced artifacts and operational events, not only the top-level return value.
Nearby result: UTC_E_FILTER_INVALID_COMMAND — means the command name or overall syntax is unrecognized.
Typed-filter note
Save the filter after variable substitution and type inference, not only the authoring XML. A visually plausible expression can still fail because the runtime command table, scope or operand types differ from the authoring tool. Test with one synthetic event whose fields and types are known exactly.
Fix the contract
Fix the authoring source so every generated command carries its mandatory attributes.
Technical references
- Microsoft Open Specifications: Windows error-code registry — reference for scenario filter parser and evaluator while interpreting this result.
- Microsoft: Universal Telemetry Client configuration diagnosis — reference for scenario filter parser and evaluator while interpreting it.
- Microsoft: Windows Event Log query schema
- Microsoft: Querying Windows Event Log
Looking for a different code? Search another status or error code.