| Previous | Next |
| TYPE_E_INVALIDSTATE | TYPE_E_ELEMENTNOTFOUND |
TYPE_E_WRONGTYPEKIND
Type information has the wrong TYPEKIND
TYPE_E_WRONGTYPEKIND is HRESULT 2147647530 (0x8002802A) from winerror.h. AllStat describes it as “Type mismatch.” The value must be interpreted at ITypeInfo operations valid only for interfaces, records, enums, aliases, modules, or coclasses of a particular kind, because the same high-level symptom can come from a different contract boundary and require different cleanup.
The decisive Interpretation is that the target TYPEATTR.typekind does not support the requested metadata operation. Keep the symbolic name beside the raw hexadecimal value so later analysis does not collapse the result into an unrelated COM family.
Where the result appears
- This result belongs to type-library and metadata processing around ITypeInfo operations valid only for interfaces, records, enums, aliases, modules, or coclasses of a particular kind.
- 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.
Determine the object and lifecycle phase that owned this result; a UI symptom cannot establish whether the origin was the caller, proxy, runtime, server, or metadata producer.
Typical causes and interpretation boundary
Common cause categories for this HRESULT are: a record is treated as an interface; a module-only function API is used on a coclass; imported metadata differs from assumptions. Evaluate these branches independently and require evidence from the owning API before promoting one branch to the root cause.
If the decisive fact for this HRESULT is unknown, keep the result unresolved and collect the missing state instead of inferring it from wording.
Evidence and telemetry
- Record it with the type-library path and hash, LIBID and version, LCID, architecture, source package, and producer toolchain.
- capture TYPEKIND value; API called; type flags; containing library; generated source declaration; expected kind.
- Retain the exact type, member, field, name, MEMBERID, HREFTYPE, TYPEKIND, or registry path involved in it.
- When it is produced during generation, record construction order, imported libraries, layout/finalization state, and output TLB hash.
- After it, release TYPEATTR, FUNCDESC, VARDESC, BSTR, and interface resources using the matching API even when parsing or lookup fails.
Log identifiers, sizes, type tags, states, and hashes while excluding credentials, tokens, document payloads, and complete user arguments.
Diagnostic sequence
- Capture it (0x8002802A) before a compiler, importer, or language runtime reduces it to a generic metadata error.
- Verify the exact type-library identity, file/resource loaded, registry view, architecture, and operation that returned it.
- Test the likely causes independently for this HRESULT: a record is treated as an interface; a module-only function API is used on a coclass; imported metadata differs from assumptions.
- For <code>it</code>, 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 it disappears without introducing a different identity or compatibility break.
Correct handling and recovery
The appropriate recovery is to read TYPEATTR first, branch by TYPEKIND, and call only operations documented for that category. The owner of retry for this HRESULT must define idempotency, refreshed state, maximum attempts, backoff, and cancellation responsibility.
After it, apply the API-specific validity rules to outputs and release only resources whose ownership transferred during this attempt.
Practical scenario
A browser requests implemented interfaces from an enum type; it checks TYPEKIND and displays enum members instead.
A regression test for this HRESULT should force the decisive precondition, assert native outputs, fix only that condition, and confirm the expected neighboring result.
Difference from related HRESULTs
DISP_E_TYPEMISMATCH concerns a runtime argument; it concerns the category of a metadata type.
Represent this distinction for this HRESULT directly in control flow and dashboards instead of grouping it under a single COM-failure label.
Developer and administrator guidance
Tools handling it should pin type-library identity and version, avoid caching raw indices across versions, and preserve stable GUIDs and DISPIDs for published contracts. Repair for <code>it</code> 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 <code>it</code>, 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.