| Previous | Next |
| INPLACE_E_NOTOOLSPACE | CONVERT10_E_OLESTREAM_PUT |
CONVERT10_E_OLESTREAM_GET
OLESTREAM Get method failed
The native value 0x800401C0 is CONVERT10_E_OLESTREAM_GET, unsigned 2147746240 and signed -2147221056. The documented description is “OLESTREAM Get method failed”. Treat it as evidence that the OLESTREAM Get callback failed while reading OLE 1 data; the operation in progress is converting an OLE 1 stream into OLE 2 structured storage.
Operational meaning
OLE 1/OLE 2 conversion combines callback I/O, binary parsing, structured storage, and presentation conversion. Retaining the stage and byte offset is essential because a read failure, format failure, missing stream, and GDI failure require different repairs.
- Associate this result with one exact operation in OleConvertOLESTREAMToIStorage, OleConvertIStorageToOLESTREAM, OLESTREAM callbacks, structured-storage streams, and presentation-data conversion.
- Confirm that this result came from converting an OLE 1 stream into OLE 2 structured storage, rather than from cleanup or a wrapper that ran afterward.
Cause model
- It can result when the callback returns fewer bytes than required without a valid end condition.
- It can result when the source file, memory block, or transport becomes unreadable.
- It can result when callback context, offset, or lifetime is invalid.
Troubleshooting workflow
- Identify the exact object, method, and lifecycle phase involved in converting an OLE 1 stream into OLE 2 structured storage.
- Log each requested and returned byte count and callback status.
- Record source offset and whether earlier reads succeeded.
- Verify that the callback context remains valid for the entire conversion.
What to log
A useful incident records the conversion direction, OLESTREAM Get or Put callback result, requested byte count, actual byte count, storage class, stream names, presentation format, bitmap or DIB metadata, and commit state.
Correction strategy
Correction. repair the source or callback, restart conversion into a fresh uncommitted storage, and discard partial output. Retry condition. Retry from the beginning after input becomes readable; resuming at an inferred offset can misparse object records. Before repeating the operation, record stream positions and byte counts, release temporary GDI objects, and discard or roll back any output storage that was only partly written.
Practical scenario
A migration tool closes the input file before OleConvertOLESTREAMToIStorage finishes; keeping the handle alive through the call restores all reads.
Difference from related HRESULTs
CONVERT10_E_OLESTREAM_FMT means bytes were read but the OLE 1 format is invalid; it means acquisition itself failed.
Developer and administrator guidance
Make OLESTREAM callbacks report exact byte counts, validate format headers before allocating, preserve structured-storage commit boundaries, and separate bitmap from DIB ownership. Regression coverage should include short reads and writes, invalid format records, absent standard streams, truncated presentation data, large dimensions, callback errors, and failure before versus after storage commit.
Preserve the original document and reproduce with a copy; repair the producing application or converter only after the failing conversion stage and file provenance are identified.
References
Looking for a different code? Search another status or error code.