| Previous | Next |
| OSS_NEGATIVE_UINTEGER | OSS_MORE_INPUT |
OSS_PDU_RANGE
OSS_PDU_RANGE (0x80093003) is an OSS ASN.1 runtime result for PDU selector outside the generated control table. The PDU number supplied to the runtime does not identify a top-level type in the control information currently in use. Because numeric PDU selector and symbolic generated constant 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 identity and build hash of the control table, then separate the encoded value from generated artifacts, call arguments, and the runtime package actually loaded by the process.
Avoid the wrong workaround: OSS_PDU_RANGE
OSS_TABLE_MISMATCH instead means a type is absent from the selected table during a later operation; PDU_RANGE rejects the selector itself.
Interpretation at runtime
At the PDU selector outside the generated control table 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 OssControl instance passed to the call; otherwise an outer certificate or security wrapper may hide the useful codec result behind a generic failure.
Diagnostic record
- numeric PDU selector and symbolic generated constant
- identity and build hash of the control table
- the OssControl instance passed to the call
Small experiments with high signal
- encode a known top-level type from the same generated files
- Log selector-to-name mapping at the call boundary
- Verify that no stale enum was persisted across deployments
Instrumentation
Where numeric PDU selector and symbolic generated constant can expose sensitive content, a hash plus a bounded structural excerpt is safer than the complete payload. Use identity and build hash of the control table together with OSS module paths and versions logged once per process so packaging differences can be correlated without flooding normal diagnostics.
Proof of recovery: the result
Deploy generated headers, control data, and application code as one versioned unit.
Technical references
Looking for a different code? Search another status or error code.