3.2.5.13 Receiving a RopCreateAttachment ROP Request
When processing the RopCreateAttachment ROP ([MS-OXCROPS] section 2.2.6.13), the server does not commit the new Attachment object until it receives a call to the RopSaveChangesAttachment ROP ([MS-OXCROPS] section 2.2.6.15).
The server MUST initialize the following properties before responding.
|
Property name |
Initial data |
|---|---|
|
PidTagAttachNumber (section 2.2.2.6) |
Varies, depending on the number of existing attachments on the Message object |
|
PidTagAttachSize (section 2.2.2.5) |
0x00000040<30> |
|
PidTagAccessLevel ([MS-OXCPRPT] section 2.2.1.2) |
0x00000001<31> |
|
PidTagRenderingPosition (section 2.2.2.16) |
0xFFFFFFFF |
|
PidTagCreationTime (section 2.2.2.3) |
The time the RopCreateAttachment ROP ([MS-OXCROPS] section 2.2.6.13) was processed |
|
PidTagLastModificationTime (section 2.2.2.2) |
Same as the PidTagCreationTime property<32> |
The following specific error codes apply to this ROP.
|
Error code name |
Value |
Meaning |
|---|---|---|
|
ecMaxAttachmentExceeded |
0x000004DB |
The (server defined) maximum number of attachments for a message has been exceeded. |
|
ecNullObject |
0x000004B9 |
The value of the InputHandleIndex field on which this ROP was called does not refer to a Message object. |