| Previous | Next |
| UTC_E_REACHED_MAX_ESCALATIONS | UTC_E_INTENTIONAL_SCRIPT_FAILURE |
UTC_E_FORWARDER_PRODUCER_MISMATCH
Read this as a lifecycle result: forwarder producer contract
When UTC_E_FORWARDER_PRODUCER_MISMATCH (0x87C51012) is returned, the producing layer is trigger-forwarder lifecycle. Treat this HRESULT as a state-machine report, not as a generic telemetry outage. The rejected object or state is forwarder producer contract, and the specific condition is that an update or state request supplied a forwarder object created for a different producer kind. Keep this first HRESULT even if a later service call reports another error.
Trigger forwarders connect a producer to scenario trigger processing and have their own registration and enable state. Reusing a handle after configuration reload or crossing producer types can fail before any scenario filter is evaluated.
Diagnostic record
| UTC diagnostic field | Value |
|---|---|
| Owning state or object | forwarder producer contract |
| Producing layer | trigger-forwarder lifecycle |
| Do not confuse with | UTC_E_TRIGGER_MISMATCH compares a trigger instance with an expected trigger type |
| Evidence to collect | expected and actual producer types, forwarder handle origin, registration generation and callback identity |
| Narrow comparison | create a new forwarder from the intended producer and repeat the update with identical trigger data |
Isolate one changing condition
- Associate this result with one request, one scenario version and one service process ID.
- Save expected and actual producer types, forwarder handle origin, registration generation and callback identity and the first lower-level HRESULT if one exists.
- Change no policy, provider set or destination except for this test: create a new forwarder from the intended producer and repeat the update with identical trigger data.
- Compare the produced artifacts and operational events, not only the top-level return value.
Nearby result: UTC_E_TRIGGER_MISMATCH — compares a trigger instance with an expected trigger type.
Platform-state note
Capture capability and identity state at the moment this result is returned. Session, container, service and destination state can change asynchronously, so a later successful query does not describe the state at failure.
Operational response
Keep producer-specific handles separate and invalidate cached forwarders after configuration reload.
Technical references
- Microsoft Open Specifications: Windows error-code registry — reference for trigger-forwarder lifecycle while interpreting this result.
- Microsoft: Universal Telemetry Client configuration diagnosis — reference for trigger-forwarder lifecycle while interpreting this result.
- Microsoft: Event Tracing for Windows — reference for trigger-forwarder lifecycle while interpreting it.
- Microsoft: UniversalTelemetryClient operational-log guidance
Looking for a different code? Search another status or error code.