| Previous | Next |
| TYPE_E_TYPEMISMATCH | TYPE_E_IOERROR |
TYPE_E_OUTOFBOUNDS
Type-information argument count is outside the valid range
TYPE_E_OUTOFBOUNDS is HRESULT 2147650721 (0x80028CA1) from winerror.h. The documented description is “Invalid number of arguments.” The result belongs to creation or inspection of function and property descriptions in a type library. The important boundary is not merely failure but which object and state transition established: the number or index of metadata arguments lies outside the limits of the current member description.
TYPE_E_OUTOFBOUNDS means that the number or index of metadata arguments lies outside the limits of the current member description.
Where the result appears
- This result can surface in a type-library compiler, importer, registration step, proxy generator, or Automation metadata consumer.
- Map the failure to one concrete operation among LoadTypeLib, RegisterTypeLib, ITypeInfo, ICreateTypeInfo, FUNCDESC, TYPEDESC, and imported LIBID versions.
- Preserve LIBID, type-library version, LCID, SYSKIND, TYPEKIND, GUID, MEMBERID, HREFTYPE, and the producer toolchain before releasing or replacing the object that returned this result.
An incident record must distinguish caller, runtime, provider, and backing resource while testing whether the number or index of metadata arguments lies outside the limits of the current member description.
Typical causes and interpretation
The immediate contract boundary is specific: the number or index of metadata arguments lies outside the limits of the current member description. Common cause branches include the following:
- A FUNCDESC count does not match the allocated parameter array.
- An importer reads a stale index after the member list changed.
- A generator emits more arguments than the target Automation representation supports.
Confirm the cause branch that explains why the number or index of metadata arguments lies outside the limits of the current member description by using call arguments, object state, metadata, device information, or provider traces.
Correct handling and recovery
The primary recovery is to recompute parameter counts and indices from the current metadata, then rebuild rather than patching the binary type library. The failure report should capture the relevant state during creation or inspection of function and property descriptions in a type library so it is clear why the number or index of metadata arguments lies outside the limits of the current member description.
Retry this result only when evidence shows the state behind “the number or index of metadata arguments lies outside the limits of the current member description” can change and the operation is repeatable.
Practical scenario
An IDL generator removes an optional parameter but leaves cParams and the parameter table out of sync, causing final type-info layout to fail.
Difference from related HRESULTs
DISP_E_BADPARAMCOUNT is raised during IDispatch invocation; it is a type-information construction or inspection failure
Developer and administrator guidance
Use a minimal IDL or metadata fixture that reproduces the exact graph, then validate both 32-bit and 64-bit generated artifacts.
Administrators should repair the component owning creation or inspection of function and property descriptions in a type library as a versioned unit instead of copying arbitrary DLLs.
References
Looking for a different code? Search another status or error code.