| Previous | Next |
| OSS_PDV_CODE_NOT_LINKED | OSS_BERDER_DLL_NOT_LINKED |
OSS_API_DLL_NOT_LINKED
OSS_API_DLL_NOT_LINKED (0x80093029) is an OSS ASN.1 runtime result for OSS API DLL absent. The legacy runtime expects its API component as a dynamic module, but Windows loader resolution does not provide a compatible DLL. Because requested DLL name and search result 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 bitness, file version, and dependent modules, then separate the encoded value from generated artifacts, call arguments, and the runtime package actually loaded by the process.
Locate the exact codec boundary
At the OSS API 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 packaging layout on the failing machine; otherwise an outer certificate or security wrapper may hide the useful codec result behind a generic failure.
Keep the original bytes or object graph unchanged while testing capture loader snaps in a test environment. A change in bitness, file version, and dependent modules after reload, plugin replacement, restart, or schema deployment is evidence about runtime state, not permission to discard the reproducer. When packaging layout on the failing machine points to one message, retain a cryptographic hash and the smallest safe sample instead of logging certificate, subscriber, credential, or private-key material.
Evidence worth preserving
| Record | Diagnostic value |
|---|---|
| requested DLL name and search result | Locates the concrete message, allocation, module, or API boundary |
| bitness, file version, and dependent modules | Separates payload-dependent behavior from build and process state |
| packaging layout on the failing machine | Makes the comparison reproducible without rewriting the original artifact |
A controlled way to reproduce it
- capture loader snaps in a test environment
- launch from a clean directory and explicit package
- remove duplicate old runtime DLLs from PATH
What not to confuse it with: the result
Registration changes do not fix an ordinary missing or incompatible DLL unless the product explicitly uses COM registration.
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 requested DLL name and search result can expose sensitive content, a hash plus a bounded structural excerpt is safer than the complete payload. Use bitness, file version, and dependent modules together with OSS module paths and versions logged once per process so packaging differences can be correlated without flooding normal diagnostics.
Decision matrix
| Controlled observation | Conclusion it supports |
|---|---|
| capture loader snaps in a test environment | A changed outcome isolates the first proposed control instead of a blind retry |
| requested DLL name and search result differs between success and failure | The difference localizes the OSS API 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 |
Exit criteria: the result
Package one compatible runtime set and verify the loaded file paths at application start. A recovery test built around capture loader snaps in a test environment 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 requested DLL name and search result 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.