| Previous | Next |
| TYPE_E_BADMODULEKIND | TYPE_E_DUPLICATEID |
TYPE_E_SIZETOOBIG
Type metadata exceeds the supported 64K size
TYPE_E_SIZETOOBIG is HRESULT 2147649733 (0x800288C5) from winerror.h. AllStat describes it as “Size may not exceed 64K.” The value must be interpreted at legacy Automation type-library structures with a 64K limit for a generated type or metadata block, because the same high-level symptom can come from a different contract boundary and require different cleanup.
The decisive Interpretation is that the encoded type information is too large for the supported representation. A diagnostic event for this HRESULT should retain both representations of the HRESULT and the exact API boundary that produced it.
Where the result appears
- This result belongs to type-library and metadata processing around legacy Automation type-library structures with a 64K limit for a generated type or metadata block.
- 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.
Before assigning cause to this result, identify the responsible thread, apartment, process, library generation, and server instance rather than relying on the final dialog text.
Typical causes and interpretation boundary
Common cause categories for this HRESULT are: a generated interface has thousands of members; embedded help strings are excessive; one module accumulates too many declarations. The candidate causes for this HRESULT are alternatives, so test one precondition at a time instead of applying several broad repairs together.
The check that separates this result from nearby HRESULTs is: the encoded type information is too large for the supported representation. When the boundary condition behind it has not been proven, avoid retries or repairs that assume a different neighboring HRESULT.
Evidence and telemetry
- Record it with the type-library path and hash, LIBID and version, LCID, architecture, source package, and producer toolchain.
- capture type or module name; member count; documentation size; generated record layout; TLB size; compiler version.
- 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.
Telemetry for this HRESULT should be reproducible without copying secret values: prefer GUIDs, lengths, flags, sanitized names, and correlation IDs.
Diagnostic sequence
- Capture it (0x800288C5) 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.
- Prove the decisive metadata condition for this HRESULT: the encoded type information is too large for the supported representation.
- Test the likely causes independently for this HRESULT: a generated interface has thousands of members; embedded help strings are excessive; one module accumulates too many declarations.
- 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 split the contract into smaller interfaces or modules, remove generated duplication, preserve compatibility through composition, and rebuild the type library. Before retrying it, specify which precondition changed and how duplicate effects or stale outputs will be detected.
Inspect every output before cleanup because interfaces, buffers, server effects, or metadata handles may be partially initialized.
Practical scenario
A code generator emits every database column as methods on one interface; the contract is partitioned into focused interfaces.
Test it by reproducing the smallest failing contract, recording postconditions, and then changing a single input or state transition.
Difference from related HRESULTs
TYPE_E_BUFFERTOOSMALL concerns caller storage; it means the metadata object itself exceeds the format limit.
Keeping it separate from its neighbor improves retry, cleanup, and user messaging because the two results imply different postconditions.
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.