| Previous | Next |
| CO_S_NOTALLINTERFACES | WINBIO_I_MORE_DATA |
CO_S_MACHINENAMENOTFOUND
COM machine name was absent from the activation cache
CO_S_MACHINENAMENOTFOUND is HRESULT 524307 (0x00080013) from winerror.h. AllStat describes it as “The specified machine name was not found in the cache.” The severity bit indicates a nonfailure result, but the value carries a specific condition that must not be collapsed into plain S_OK.
In the COM activation or interface negotiation, this result means that the specified machine name was not found in the cache. Consumers of it must decide from the API contract whether to stop, wait, continue, or expose a reduced outcome.
What must be true before accepting it
Verify that the caller distinguishes a cache miss from proof that the machine or COM server does not exist. Checking the boundary keeps this result from hiding stale data, pending work, or a deliberately reduced result.
Do not compensate for it until the caller knows which sub-operations actually occurred.
Where the status is encountered
- This result can be returned during COM activation requesting multiple interfaces; log the exact method and object state instead of interpreting the constant outside that contract.
- This result can be returned during remote COM or DCOM activation; log the exact method and object state instead of interpreting the constant outside that contract.
- It can be returned during component wrappers that preserve per-interface outcomes; log the exact method and object state instead of interpreting the constant outside that contract.
Because it is informational, a language binding may expose it as success and hide the symbolic distinction. Keep the original HRESULT available until the code-specific branch has run.
Evidence and telemetry
- preserve requested machine name.
- preserve canonical DNS and NetBIOS names.
- preserve cache generation or timestamp.
- preserve COSERVERINFO settings.
- preserve activation and name-resolution traces.
Also record co_s_machinenamenotfound_operation, co_s_machinenamenotfound_state_before, co_s_machinenamenotfound_state_after, UTC time, process and thread identifiers, component version, and a correlation ID. A diagnostic bundle for it should preserve correlation fields without copying tokens, keys, or private media.
Correct handling and recovery
Refresh or bypass the machine-name cache through the owning COM path, validate DNS and configured remote server identity, and retry only after the resolution data changes.
Retry it only when a documented input or state has changed. Continuation after it may be appropriate, but an identical restart is not automatically recovery.
Practical scenario
A remote activation request uses a recently renamed server. The client refreshes configuration and name resolution rather than repeatedly activating against the stale cached name.
A regression test should reproduce it, assert the relevant outputs and state, then change only the decisive condition and verify the expected neighboring result or ordinary completion.
Difference from nearby results
RPC_S_SERVER_UNAVAILABLE indicates communication failure after resolution; this status specifically reports that the machine name was not found in the cache.
The practical value of distinguishing it is choosing the right wait, stop, retry, or user-notification behavior.
References
- Microsoft: IUnknown::QueryInterface — official Microsoft material used to interpret it.
- Microsoft: COM and DCOM
- Microsoft: HRESULT values
Looking for a different code? Search another status or error code.