Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic Processing RopWriteStream

When the server receives a RopWriteStreamROP request buffer ([MS-OXCROPS] section from the client, the server parses the buffer. The server responds with a RopWriteStreamROP response buffer. For details about how the server parses buffers and processes ROPs, see [MS-OXCROPS] section For details about how the server formats buffers for the response, see [MS-OXCROPS] section

The server SHOULD<11> return the TooBig error code if it writes less than the amount requested. The server MUST store the data that is specified in the ROP request buffer into a stream buffer, writing forward starting at the current seek pointer. The seek pointer MUST be moved forward the same number of bytes as were written to the Stream object.

After a RopWriteStream ROP request buffer is processed, the new value of the property MUST be immediately available for retrieval by a ROP that uses the same object handle. However, the new value of the property is not persisted to the database. For a Message object, the new value is persisted to the database when a successful RopSaveChangesMessage ROP ([MS-OXCROPS] section is issued. For an Attachment object, the new value is persisted to the database when a successful RopSaveChangesAttachment ROP ([MS-OXCROPS] section followed by a successful RopSaveChangesMessage ROP is issued. For a Folder object, the value is persisted when the RopCommitStream ROP ([MS-OXCROPS] section is issued on the Stream object or the Stream object is closed with a RopRelease ROP ([MS-OXCROPS] section

The following error codes SHOULD be returned when the scenarios described in the corresponding Description column of the following table are met.

Error code name





The write will exceed the maximum stream size.



Write access is denied.

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
© 2014 Microsoft. All rights reserved.