| Previous | Next |
| CRYPT_E_OBJECT_LOCATOR_OBJECT_NOT_FOUND | OSS_NEGATIVE_UINTEGER |
OSS_MORE_BUF
OSS_MORE_BUF (0x80093001) is an OSS ASN.1 runtime result for caller-owned output buffer exhaustion. The encoder or decoder needs more room than the caller supplied; pointer-referenced fields can make a PDU larger than sizeof its top-level C structure. Because requested versus allocated byte count is central to this condition, Microsoft’s HRESULT range and the OSS Nokalva return-code documentation should be read together. Start the investigation by recording whether automatic allocation was disabled, then separate the encoded value from generated artifacts, call arguments, and the runtime package actually loaded by the process.
Locate the failing codec stage
At the caller-owned output buffer exhaustion boundary, capture the first OSS function returning the value and note whether the operation was encode, decode, copy, compare, constraint validation, or trace setup. Preserve the selected PDU, encoding rules, and the PDU fields that own strings, arrays, or off-shoot structures; otherwise an outer certificate or security wrapper may hide the useful codec result behind a generic failure.
Evidence worth preserving
- requested versus allocated byte count
- whether automatic allocation was disabled
- the PDU fields that own strings, arrays, or off-shoot structures
A controlled way to reproduce it
- ask the runtime to determine the encoded length before allocating
- Repeat with runtime allocation as a control
- place guard bytes around a test buffer to detect overwrite assumptions
What not to confuse it with: the result
Unlike OSS_MORE_INPUT, the complete encoded input may be present; the shortage is in storage for the produced representation.
Instrumentation
Where requested versus allocated byte count can expose sensitive content, a hash plus a bounded structural excerpt is safer than the complete payload. Use whether automatic allocation was disabled together with OSS module paths and versions logged once per process so packaging differences can be correlated without flooding normal diagnostics.
Exit criteria: the result
Size from the codec contract rather than from the host-language structure, then prove the same PDU succeeds without truncation.
Technical references
Looking for a different code? Search another status or error code.