| Previous | Next |
| ERROR_BAD_ACCESSOR_FLAGS | ERROR_NOT_CAPABLE |
ERROR_ERRORS_ENCOUNTERED
one or more sub-operations failed while the overall request was being processed.
ERROR_ERRORS_ENCOUNTERED identifies the condition that this condition This aggregate status says the operation produced multiple per-item outcomes and at least one was unsuccessful. The actionable detail is usually stored in a status array, error object, property result, or diagnostic record returned alongside it.
Where the result appears
- bulk property updates.
- multi-row or multi-column provider operations.
- batch management commands.
- APIs that continue after individual item failures.
How to interpret the result
Interpret the numeric value in the Win32/LRESULT domain and in the context of the API that returned it. Preserve this result before wrappers convert it to an HRESULT, exception, Boolean failure, or provider-specific message. When recording it, note whether the operation produced usable output; this determines whether the value is completion information, control flow, or a terminal failure.
Diagnostic evidence to collect
- per-item status values.
- first failing item and all subsequent failures.
- partial outputs that were committed.
- provider-specific error records and correlation identifiers.
A diagnostic record for this Win32 error should contain the API name, input flags, relevant handles or object identifiers, thread and process identity, timestamp, and the immediately preceding state transition. Those fields are more useful than a generic screenshot because they show which contract and lifecycle phase produced the value.
Handling and recovery
Do not discard the detailed result collection. Decide whether partial success is acceptable, compensate only the items that changed, and report precise failed elements to the caller.
Retry after this result only when an external state relevant to this operation can actually change. When it is rooted in object state, unsupported capability, ownership, or invalid sequencing, an unchanged retry repeats the defect and can obscure the first useful diagnostic record.
Common misinterpretation
The aggregate code alone cannot identify the root cause. Logging only this value destroys the information needed to distinguish validation, permission, conversion, and resource failures.
Guidance for developers
Keep the original this result value and its Win32 domain in structured telemetry. If it crosses COM or another HRESULT-based boundary, store both the source Win32 value and the converted result. If it crosses JSON, RPC, or a database boundary, include error_domain, error_code, operation, and object_state so the receiver does not apply a second conversion.
An automated test should construct the specific state that leads to this result, assert the exact returned value, and verify cleanup on both the normal and exceptional path. The result test should additionally prove that the caller does not collapse this status into an unrelated generic error and does not retry forever.
References
Looking for a different code? Search another status or error code.