| Previous | Next |
| CONVERT10_E_OLESTREAM_PUT | CONVERT10_E_OLESTREAM_BITMAP_TO_DIB |
CONVERT10_E_OLESTREAM_FMT
Contents of the OLESTREAM not in correct format
When Windows returns CONVERT10_E_OLESTREAM_FMT—HRESULT 2147746242, 0x800401C2, signed -2147221054—The documented description is “Contents of the OLESTREAM not in correct format”. The actionable meaning is the OLE 1 stream contents do not conform to the format expected by the converter. The surrounding operation is parsing records after successful OLESTREAM reads.
Precise failure point
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 parsing records after successful OLESTREAM reads, rather than from cleanup or a wrapper that ran afterward.
Diagnostic evidence
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.
- Retain a hash and size of the input and the byte offset where parsing fails.
- Verify source provenance and format signature.
- Compare with a known-good export from the same producer version.
Resolution path
- Identify the exact object, method, and lifecycle phase involved in parsing records after successful OLESTREAM reads.
Distinct causes
- It can result when the stream is truncated or corrupted.
- It can result when the input is not actually an OLE 1 stream despite its extension or metadata.
- It can result when record lengths, class data, or presentation sections are internally inconsistent.
Retry policy
Correction. obtain or regenerate a valid OLE 1 stream; do not guess missing fields or continue into partially built storage. Retry condition. Retry only with different validated input or a corrected producer. 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 document labeled as legacy OLE contains an HTML wrapper downloaded from a server; identifying the real content prevents the converter from treating it as binary OLE data.
Difference from related HRESULTs
CONVERT10_E_OLESTREAM_GET reports inability to read bytes; it reports invalid meaning of bytes that were read.
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.