| Previous | Next |
| UTC_E_RPC_TIMEOUT | UTC_E_API_BUSY |
UTC_E_RPC_WAIT_FAILED
Locate the rejected contract: synchronous API wait object
When UTC_E_RPC_WAIT_FAILED (0x87C5102A) is returned, the producing layer is Universal Telemetry Client API coordination for this HRESULT. The symbolic name points to a narrow UTC contract that can be tested directly for this HRESULT. The rejected object or state is synchronous API wait object, and the specific boundary is that the client could not successfully wait for the completion signal, independently of the operation result for this HRESULT. Later service errors should not replace this first result in the incident record for this HRESULT.
UTC API requests may cross an RPC boundary and complete asynchronously even when exposed through a synchronous wrapper for this HRESULT. Request submission, waiting, cancellation and result retrieval are separate stages, so one request ID should tie the evidence together 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.
Capture checklist
| UTC diagnostic field | Value |
|---|---|
| Owning state or object | synchronous API wait object |
| Producing layer | Universal Telemetry Client API coordination |
| Do not confuse with | UTC_E_RPC_TIMEOUT means the wait completed as a timeout rather than failing as a wait operation |
| Decisive evidence | request and wait handles, wait return code, thread apartment, cancellation, handle lifetime and service exit |
| Narrow comparison | use a fresh request on a dedicated thread and verify the wait handle remains valid until signaled |
The AllStat message names the immediate condition as “The synchronous API encountered a wait failure” 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.
Comparison with a passing case
- Associate this result with one request, one scenario version and one service process ID for this HRESULT.
- Save request and wait handles, wait return code, thread apartment, cancellation, handle lifetime and service exit and the first lower-level HRESULT if one exists for this HRESULT.
- Change no policy, provider set or destination except for this test: use a fresh request on a dedicated thread and verify the wait handle remains valid until signaled for this HRESULT.
- Compare the produced artifacts and operational events, not only the top-level return Value.
The most informative neighbor is UTC_E_RPC_TIMEOUT. The distinction is concrete: UTC_E_RPC_TIMEOUT means the wait completed as a timeout rather than failing as a wait operation 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.
Request-lifetime note
Assign a correlation identifier before submission and retain it through wait, callback, cancellation and result retrieval for this HRESULT. This prevents a late completion from being mistaken for the response to a newer request for this HRESULT.
Resolution and regression test
Correct handle ownership and shutdown ordering, retaining both the wait error and any server result 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 synchronous API wait object
- the nearby condition remains distinguishable: UTC_E_RPC_TIMEOUT means the wait completed as a timeout rather than failing as a wait operation
Technical references
- Microsoft Open Specifications: Windows error-code registry — reference for Universal Telemetry Client API coordination while interpreting this result.
- Microsoft: Universal Telemetry Client configuration diagnosis
- Microsoft: Remote Procedure Call documentation
- Microsoft: WaitForSingleObject
Looking for a different code? Search another status or error code.