| Previous | Next |
| CACHE_S_SAMECACHE | OLEOBJ_S_INVALIDVERB |
CACHE_S_SOMECACHES_NOTUPDATED
Only some OLE presentation caches were refreshed
CACHE_S_SOMECACHES_NOTUPDATED is HRESULT 262514 (0x00040172) from winerror.h. AllStat describes this result as “Some cache(s) not updated.” The high-order severity bit is clear, so this is a success result, but it carries more information than plain S_OK.
The cache update operation completed partially: at least one cache was updated while one or more other cache entries were not.
Evidence and telemetry to preserve
- preserve cache connection identifiers and FORMATETC values.
- preserve per-entry update result.
- preserve running state of the source object.
- preserve ADVF update flags.
- preserve rendered checksums or timestamps for each presentation.
Also record cache_s_somecaches_notupdated_operation, cache_s_somecaches_notupdated_object, cache_s_somecaches_notupdated_state_before, cache_s_somecaches_notupdated_state_after, UTC time, process and thread identifiers, and a correlation ID. Keep secrets out of logs while retaining GUIDs, CLSIDs, media subtypes, property IDs, row identities, and hashes needed to distinguish objects.
Where the result is encountered
- This result can appear in IOleCache2::UpdateCache calls; record the producing interface and method rather than inferring behavior from the symbolic name alone.
- This result can appear in save or print preparation for embedded objects; record the producing interface and method rather than inferring behavior from the symbolic name alone.
- It can appear in offline presentation refresh across multiple aspects and formats; record the producing interface and method rather than inferring behavior from the symbolic name alone.
The same numeric success value can be mishandled when a wrapper exposes only a Boolean. Keep the original HRESULT until the code-specific outputs and state transition have been evaluated.
State boundary that must be proved
The central question for it is whether the caller must identify which cache entries are current before using them for persistence, preview, or printing. The HRESULT alone confirms neither unrelated work nor the quality of optional outputs.
A reliable interpretation of it names the exact method contract, the object generation, and the outputs that remain valid. This prevents a success-with-information result from being promoted to full success or demoted to a generic error.
Diagnostic sequence
- capture the raw HRESULT
0x00040172immediately after the returning method and record whether the caller usedSUCCEEDED,FAILED, equality testing, or exception translation. - Identify the exact owner of it: interface, method, object instance, provider or filter version, thread or apartment, and operation phase.
- Validate the decisive contract boundary for it: the caller must identify which cache entries are current before using them for persistence, preview, or printing.
- inspect every output parameter, count, status array, returned interface, or side effect that the method documentation associates with this success-with-information result.
- Compare the observed state before and after it; do not assume that a success severity bit means every optional sub-operation completed.
- reproduce the smallest request with the same object state and then change only the condition identified by the evidence before repeating the operation.
Difference from nearby HRESULT values
CACHE_S_FORMATETC_NOTSUPPORTED explains an unsupported requested format; it reports a mixed refresh outcome across existing caches.
This distinction determines whether the caller should consume partial outputs, stop iteration, wait, reconfigure, notify the user, or perform no error recovery at all.
Correct handling, retry, and recovery
Use the current entries only where partial freshness is acceptable. Retry or replace failed entries individually; do not report the entire object cache as current.
Retry it only when the recorded state can change the documented outcome. Repeating the same call is inappropriate for a stable end marker, cancellation, unsupported format, adjusted property, or partial result whose completed side effects have not been reconciled.
Practical validation scenario
A container refreshes icon, content, and thumbnail caches before save. Content and icon update, thumbnail does not; the save path preserves the successful entries and marks the thumbnail stale for later repair.
The negative test should preserve the condition that produces it; the recovery test should alter only that condition and verify the final state as well as the HRESULT.
Developer and administrator guidance
When it crosses process, RPC, scripting, or managed-code boundaries, preserve the unsigned 32-bit value and symbolic name. A signed decimal rendering can obscure that the severity bit indicates success and can lead to incorrect exception or retry behavior.
A support report for it should include decimal 262514, hexadecimal 0x00040172, the AllStat meaning, the owning API, and the first detailed status or output that explains why the method did not return ordinary S_OK.
References
Looking for a different code? Search another status or error code.