| Previous | Next |
| RO_E_CHANGE_NOTIFICATION_IN_PROGRESS | E_STRING_NOT_NULL_TERMINATED |
RO_E_ERROR_STRING_NOT_FOUND
No localized message text exists for the HRESULT
RO_E_ERROR_STRING_NOT_FOUND is HRESULT 2147483670 (0x80000016) from winerror.h. AllStat describes it as “The text associated with this error code could not be found.” In the Windows Runtime metadata, object lifetime, asynchronous operation, activation, and apartment model, the code identifies a specific failure boundary and should not be replaced by a generic COM exception.
The hexadecimal value and symbolic name this result should remain attached to the originating API and operation generation.
Where it is encountered
- C++/WinRT, WRL,.NET projections, or native WinRT ABI calls. Record the interface, method, component version, thread, apartment, process, and correlation ID.
- Runtime-class activation, WinMD reflection, asynchronous objects, observable state, or view lifecycle.
- Cross-thread and cross-apartment handoff between UI, ASTA, STA, MTA, broker, and background work.
The immediate focus for it is an error-display path that requested a system or runtime message for a code with no registered resource string. Keep it attached to that operation; the same numeric severity outside the owning API does not supply enough context.
Decisive interpretation boundary
Before choosing recovery, verify that the numeric HRESULT and symbolic constant remain available even when localized text lookup fails. Validate this condition for it using the owning API state, not an inferred UI symptom.
Also confirm that all observed objects, tokens, buffers, proxies, metadata files, or ACLs belong to the current operation generation and were not retained from an earlier attempt.
Correct handling and recovery
Display a safe application fallback containing the symbolic code and correlation ID, while retaining the original HRESULT for support and telemetry.
Repeat the operation after it only when the documented precondition, identity, apartment, object generation, buffer, or configuration has changed.
Lifetime, retry, and cleanup rules
After it, determine whether the current object, interface pointer, call context, token, stream, metadata reader, asynchronous operation, or access-control instance remains valid. Release only resources owned by the failing attempt, cancel callbacks through their documented mechanism, and avoid double close, double commit, repeated activation, or replay of a non-idempotent remote method.
The retry policy for it should state the trigger, maximum attempts, cancellation owner, and reconciliation step for effects that may have completed elsewhere.
Practical scenario
A diagnostic viewer cannot resolve a vendor HRESULT to localized text. It shows the hex value, module, operation, and support ID instead of replacing it with an empty message.
A regression test should reproduce it, assert the raw HRESULT and all relevant outputs, then correct only the decisive condition and verify the intended success or neighboring failure result.
Difference from nearby HRESULTs
It concerns message formatting, not the success or failure of the original operation whose code was being described.
Tests for it should force both results and verify that object lifetime, output use, and user messaging differ.
References
- Microsoft: C++/WinRT error handling
- Microsoft: concurrency and asynchronous operations
- Microsoft: WinMD files
- Microsoft: IAgileObject
- Microsoft: COM apartments
- Microsoft: HRESULT values
Looking for a different code? Search another status or error code.