| Previous | Next |
| OSS_PDU_MISMATCH | OSS_BAD_PTR |
OSS_LIMITED
OSS_LIMITED (0x8009300A) is an OSS ASN.1 runtime result for implementation limit exceeded while decoding. A syntactically recognizable value exceeds a runtime capacity, such as an INTEGER magnitude, nesting depth, or representation supported by that build. Because value length, magnitude, and nesting at failure 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 runtime edition and generated representation options, then separate the encoded value from generated artifacts, call arguments, and the runtime package actually loaded by the process.
What the return code narrows down
At the implementation limit exceeded while decoding 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 protocol limits expected by the application; otherwise an outer certificate or security wrapper may hide the useful codec result behind a generic failure.
Build a useful capture
- value length, magnitude, and nesting at failure
- runtime edition and generated representation options
- protocol limits expected by the application
Neighboring statuses: the result
A schema constraint violation is reported separately; LIMITED can arise even when the abstract ASN.1 type has no such narrow bound.
Test one variable at a time
- decode a value just below the observed boundary
- enforce a protocol quota before ASN.1 allocation
- Compare another supported runtime build without changing schema
Instrumentation
Where value length, magnitude, and nesting at failure can expose sensitive content, a hash plus a bounded structural excerpt is safer than the complete payload. Use runtime edition and generated representation options together with OSS module paths and versions logged once per process so packaging differences can be correlated without flooding normal diagnostics.
Verify the repair: the result
Choose a representation that supports the required range or reject oversized inputs at the protocol boundary.
Technical references
Looking for a different code? Search another status or error code.