| Previous | Next |
| CONVERT10_E_OLESTREAM_GET | CONVERT10_E_OLESTREAM_FMT |
CONVERT10_E_OLESTREAM_PUT
OLESTREAM Put method failed
CONVERT10_E_OLESTREAM_PUT has hexadecimal value 0x800401C1 (unsigned 2147746241, signed -2147221055). Windows reports “OLESTREAM Put method failed”. The narrow interpretation is that the OLESTREAM Put callback failed while writing converted OLE 1 data. The failing stage is converting OLE 2 structured storage into an OLE 1 stream.
API stage
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 OLE 2 structured storage into an OLE 1 stream, rather than from cleanup or a wrapper that ran afterward.
Verification steps
- Identify the exact object, method, and lifecycle phase involved in converting OLE 2 structured storage into an OLE 1 stream.
- Capture requested/written byte counts, offset, and underlying write error.
- Track whether the destination supports rollback or atomic replacement.
- Verify callback lifetime and synchronization.
Interpretation limits
- It can result when the destination is full, closed, or read-only.
- It can result when the callback reports a short write or loses its context.
- It can result when a network or custom stream rejects data after partial output.
Incident record
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.
Recovery conditions
Correction. write to a new temporary destination, fix the sink, and publish the output only after complete conversion. Retry condition. Retry from the beginning after cleaning partial output; appending to a truncated stream is unsafe. 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 converter writes directly over an existing file and runs out of disk space; using a temporary file preserves the original and permits a clean retry.
Difference from related HRESULTs
CONVERT10_E_OLESTREAM_GET concerns reading OLE 1 input; it concerns emitting OLE 1 output.
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.