| Previous | Next |
| TYPE_E_OUTOFBOUNDS | TYPE_E_CANTCREATETMPFILE |
TYPE_E_IOERROR
I/O failure while reading or writing a type library
TYPE_E_IOERROR is HRESULT 2147650722 (0x80028CA2) from winerror.h. The documented description is “I/O Error.” The result belongs to loading, saving, registering, or generating a TLB resource or file. Interpret this result at the native boundary before a wrapper hides the condition that the type-library operation could not complete an underlying read, write, seek, flush, or resource access.
TYPE_E_IOERROR means that the type-library operation could not complete an underlying read, write, seek, flush, or resource access.
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 type-library operation could not complete an underlying read, write, seek, flush, or resource access.
Typical causes and interpretation
The immediate contract boundary is specific: the type-library operation could not complete an underlying read, write, seek, flush, or resource access. Common cause branches include the following:
- The TLB file is truncated or stored on an unavailable share.
- The destination directory denies creation or replacement.
- An antivirus or deployment process races the generator while it writes the file.
Confirm the cause branch that explains why the type-library operation could not complete an underlying read, write, seek, flush, or resource access by using call arguments, object state, metadata, device information, or provider traces.
Correct handling and recovery
The primary recovery is to repeat only after verifying the exact file, storage health, permissions, and atomic replacement path; otherwise regenerate from source. The failure report should capture the relevant state during loading, saving, registering, or generating a TLB resource or file so it is clear why the type-library operation could not complete an underlying read, write, seek, flush, or resource access.
A UI loop must not repeat it without refreshing the state behind “the type-library operation could not complete an underlying read, write, seek, flush, or resource access” and checking for prior side effects.
Practical scenario
A build writes a type library to a network output directory and loses the connection during final serialization, leaving a partial file that later imports cannot trust.
Difference from related HRESULTs
TYPE_E_CANTLOADLIBRARY is specifically about loading a library or DLL; it identifies a lower-level data transfer 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.
Dashboards should keep it distinct and attach dimensions that can prove or disprove: the type-library operation could not complete an underlying read, write, seek, flush, or resource access.
References
Looking for a different code? Search another status or error code.