| Previous | Next |
| TYPE_E_UNKNOWNLCID | TYPE_E_BADMODULEKIND |
TYPE_E_DLLFUNCTIONNOTFOUND
Type-library referenced DLL function is missing
TYPE_E_DLLFUNCTIONNOTFOUND is HRESULT 2147647535 (0x8002802F) from winerror.h. The documented description is “Function not defined in specified DLL.” The value must be interpreted at module type information or Automation metadata binding an entry point in a DLL.
The function declared by the type library cannot be found in the specified module exports.
Where the result appears
- This result belongs to type-library and metadata processing around module type information or Automation metadata binding an entry point in a DLL.
- Identify the LIBID, major/minor version, LCID, SYSKIND, file path, resource ID, and the specific ITypeLib or ITypeInfo operation.
- Metadata consumers should treat this result as a contract-version or construction problem until file integrity, registry view, import dependencies, TYPEKIND, and builder phase are verified.
Typical causes and interpretation
Common cause categories are: the DLL version removed the export; name decoration differs; bitness is wrong; the type library and implementation are from different packages.
Evidence to preserve
- Record the HRESULT with the type-library path and hash, LIBID and version, LCID, architecture, source package, and producer toolchain.
- Capture DLL path and version; function name or ordinal; architecture; export table; type-library declaration; dependency search path.
- Retain the exact type, member, field, name, MEMBERID, HREFTYPE, TYPEKIND, or registry path involved in the failing operation.
- When the failure occurs during type-library generation, record construction order, imported libraries, layout/finalization state, and output TLB hash.
- After the failing call, release TYPEATTR, FUNCDESC, VARDESC, BSTR, and interface resources using the matching API even when parsing or lookup fails.
Logs should expose enough structure to reproduce the failure without becoming a secondary store of sensitive input data.
Diagnostic sequence
- Capture the HRESULT (0x8002802F) before a compiler, importer, or language runtime reduces the value to a generic metadata error.
- Verify the exact type-library identity, file/resource loaded, registry view, architecture, and operation that returned the HRESULT.
- Prove the relevant metadata condition: the function declared by the type library cannot be found in the specified module exports.
- Test the likely causes independently: the DLL version removed the export; name decoration differs; bitness is wrong; the type library and implementation are from different packages.
- For
TYPE_E_DLLFUNCTIONNOTFOUND, enumerate the relevant TYPEATTR, members, imports, names, IDs, locales, and builder state instead of assuming source declarations match deployed metadata. - Rebuild or reload one corrected metadata generation and verify that the HRESULT no longer occurs without introducing a different identity or compatibility break.
Correct handling and recovery
The appropriate recovery is to deploy matching DLL and TLB versions, inspect the real export table, and avoid search-path substitutions that load another module.
Practical scenario
A type library declares EntryPointA but the deployed DLL exports only EntryPointW; package versions are aligned.
Difference from related HRESULTs
TYPE_E_LIBNOTREGISTERED concerns locating the library itself; it means the library loaded but its declared implementation entry point is absent.
Developer and administrator guidance
Tools handling this HRESULT should pin type-library identity and version, avoid caching raw indices across versions, and preserve stable GUIDs and DISPIDs for published contracts. Repair for TYPE_E_DLLFUNCTIONNOTFOUND should be performed by the metadata producer or installer, not by ad hoc registry edits in the consuming process.
Administrators should compare installed files and registration against the product manifest, repair the matching package, and keep 32-bit and 64-bit registry views explicit. For TYPE_E_DLLFUNCTIONNOTFOUND, copying a TLB from another machine can silence lookup while creating a more dangerous ABI mismatch.
References
Looking for a different code? Search another status or error code.