3.2.5.6 Processing RopAbort
The RopAbort ROP ([MS-OXCROPS] section 2.2.5.5) MUST abort the current asynchronous table ROP that is executing on the table or send an error if there is nothing to abort or if it fails to abort.
If the server receives a RopAbort ROP request while asynchronous work is being done, it MUST abort that work. The table state after a RopAbort ROP request is received is undefined until the server receives a RopResetTable ROP request ([MS-OXCROPS] section 2.2.5.15). This is true whether or not the RopAbort ROP succeeds. For more details about asynchronous processing, see section 3.2.5.1.
The RopAbort ROP MUST be supported for contents tables and hierarchy tables.
The following specific error codes apply to this ROP. For more details about ROP errors returned, see [MS-OXCDATA] section 2.4.
|
Error code name |
Value |
Description |
|---|---|---|
|
ecUnableToAbort |
0x80040114, %x14.01.04.80 |
There were no asynchronous operations to abort, or the server was unable to abort the operations. |
|
ecNotSupported |
0x80040102, %x02.01.04.80 |
The object on which this ROP was sent is not a contents table or a hierarchy table. |