| Previous | Next |
| CONVERT10_E_OLESTREAM_BITMAP_TO_DIB | CONVERT10_E_STG_NO_STD_STREAM |
CONVERT10_E_STG_FMT
Contents of the IStorage not in correct format
Windows defines CONVERT10_E_STG_FMT as 2147746244 (0x800401C4; signed value -2147221052). The documented description is “Contents of the IStorage not in correct format”. The OLE 2 IStorage does not have the structure expected for conversion to OLE 1. The relevant operation is reading structured storage before producing an OLE 1 stream.
Where it is raised
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 reading structured storage before producing an OLE 1 stream, rather than from cleanup or a wrapper that ran afterward.
Telemetry checklist
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.
- Record root CLSID, stream/storage inventory, STATSTG data, and commit state.
- Validate with structured-storage APIs before invoking conversion.
- Compare required metadata with a known-good object of the same class.
Why it is specific
- It can result when the root storage is not an OLE object storage.
- It can result when required class or format metadata is malformed.
- It can result when the storage was partially written or opened from unrelated compound-file content.
Investigation order
- Identify the exact object, method, and lifecycle phase involved in reading structured storage before producing an OLE 1 stream.
Safe handling
Correction. use a valid committed OLE object storage or repair it through its owning application; do not manufacture undocumented streams. Retry condition. Retry only with repaired or regenerated storage. 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 compound file contains application-private streams but no OLE object metadata; exporting through the owning application produces a convertible storage.
Difference from related HRESULTs
CONVERT10_E_STG_NO_STD_STREAM is narrower: the storage is recognized but lacks a required standard stream.
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.