| Previous | Next |
| OSS_MEM_MGR_DLL_NOT_LINKED | OSS_PDV_CODE_NOT_LINKED |
OSS_PDV_DLL_NOT_LINKED
OSS_PDV_DLL_NOT_LINKED (0x80093027) is an OSS ASN.1 runtime result for legacy PDV support DLL absent. A legacy modular runtime requests Presentation Data Value support, but the corresponding dynamic component is unavailable. Because operation and ASN.1 type that selects PDV handling 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 PDV module filename and loader error, then separate the encoded value from generated artifacts, call arguments, and the runtime package actually loaded by the process.
Avoid the wrong workaround: OSS_PDV_DLL_NOT_LINKED
Because Microsoft exposes this historical runtime value without a modern public Windows API contract, diagnose it as a deployment boundary rather than guessing a Windows protocol failure.
Interpretation at runtime
At the legacy PDV support DLL absent 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 runtime generation and deployment manifest; otherwise an outer certificate or security wrapper may hide the useful codec result behind a generic failure.
Diagnostic record
| Record | Diagnostic value |
|---|---|
| operation and ASN.1 type that selects PDV handling | Locates the concrete message, allocation, module, or API boundary |
| PDV module filename and loader error | Separates payload-dependent behavior from build and process state |
| runtime generation and deployment manifest | Makes the comparison reproducible without rewriting the original artifact |
Keep the original bytes or object graph unchanged while testing confirm a non-PDV PDU still works. A change in PDV module filename and loader error after reload, plugin replacement, restart, or schema deployment is evidence about runtime state, not permission to discard the reproducer. When runtime generation and deployment manifest points to one message, retain a cryptographic hash and the smallest safe sample instead of logging certificate, subscriber, credential, or private-key material.
Small experiments with high signal
- confirm a non-PDV PDU still works
- inspect dependencies of the missing module
- test the packaged application on a clean host
Decision matrix
| Controlled observation | Conclusion it supports |
|---|---|
| confirm a non-PDV PDU still works | A changed outcome isolates the first proposed control instead of a blind retry |
| operation and ASN.1 type that selects PDV handling differs between success and failure | The difference localizes the legacy PDV support DLL absent boundary before unrelated settings are changed |
| An independent decoder accepts the same artifact | Inspect generated schema, selected rules, ABI, and optional OSS modules before declaring the bytes invalid |
| A fresh control object changes the outcome | Investigate initialization, lifecycle, allocator ownership, configuration mutation, and concurrent access |
Instrumentation
Record the full 32-bit HRESULT and lower OSS return number together with operation direction, symbolic PDU, encoding rule, byte count, and generated-table identifier. Where operation and ASN.1 type that selects PDV handling can expose sensitive content, a hash plus a bounded structural excerpt is safer than the complete payload. Use PDV module filename and loader error 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
Restore the matching legacy component or rebuild the codec without that modular dependency, then replay the original PDU. A recovery test built around confirm a non-PDV PDU still works should replay the same operation under the same schema and encoding rule, retain one deliberately invalid control, and verify ownership and cleanup after both outcomes. Success after an unexamined retry is not proof that operation and ASN.1 type that selects PDV handling now satisfies the codec contract.
Technical references
- Microsoft: OSS ASN.1 HRESULT definitions
- OSS Nokalva: encoder/decoder return codes
- OSS Nokalva: runtime functions and control initialization
- Relevant ASN.1 specification or runtime detail
Looking for a different code? Search another status or error code.