none
[MS-OXCFXICS] Transfer Status of 0x0002 (NoRoom?) RRS feed

  • Question

  • Hi,

    I'm running some tests of my FastTransfer stream parser, and I've hit a situation with RopFastTransferSourceGetBuffer where the server returns a TransferStatus of 0x0002. Unfortunately I can't provide a capture, since this isn't a pure-test server.

    The request looks like:

                  BufferSize        : 0xbabe (47806)
                  MaximumBufferSize    : union FastTransferSourceGetBuffer_MaxBufferSize(case 47806)
                  MaximumBufferSize    : 0x8000 (32768)
    

    and the response looks like:

                  TransferStatus      : TransferStatus_NoRoom (2)
                  InProgressCount     : 0x0016 (22)
                  TotalStepCount      : 0x0056 (86)
                  Reserved         : 0x00 (0)
                  TransferBufferSize    : 0x7fde (32734)
                  TransferBuffer      : DATA_BLOB length=32734
    

    Earlier versions (up to the end of 2009) of the documentation did include a TransferStatus enumeration of 0x0002 as "NoRoom". That isn't included in MS-OXCFXICS v20100729 Section 2.2.3.1.1.5.1 "TransferStatus", although Product Note <11> does show this value as not being returned by Exchange 2010 (and I've only seen this during testing against SBS 2008).

    Is the intent of Product Note <11> that NoRoom should be interpreted as equivalent to Partial? Is there any significance to RopFastTransferSourceGetBuffer returning NoRoom instead of Partial on Exchange 2003 and Exchange 2007?

    Brad

     

    Tuesday, October 19, 2010 4:36 AM

Answers

  • Hi Brad,

     

    [MS-OXCFXICS] Regarding NoRoom (0x0002), this should be interpreted as equivalent to Partial (0x0001).  In Exchange Server 2007 and prior versions of Exchange Server, clients had no reason to differentiate between these two values, so starting with Exchange Server 2010, only one of the values is returned, Partial (0x0001).

     

    Also,

    <11> Section 2.2.3.1.1.5.1: In Exchange 2007 and Exchange 2003 the Partial value (0x0001) and the NoRoom value (0x0002) both indicate that the FastTransfer stream was split, more data is available, and that TransferBuffer contains incomplete data. NoRoom is not returned by Exchange 2010.

     

    I hope this answers your question.

     

    Regards,

    Mark Miller

    Escalation Engineer

    US-CSS DSC PROTOCOL TEAM

    • Marked as answer by Brad Hards Tuesday, November 2, 2010 1:25 AM
    Monday, November 1, 2010 6:25 PM

All replies

  • Brad,

    Someone from our team will be following-up with you shortly in regards to your questions.

    Dominic Salemno
    Escalation Engineer
    Open Specifications

    Tuesday, October 19, 2010 2:57 PM
  • Hi Brad,

    I will investigate this and follow up with you.

    Regards,

    Mark Miller

    Escalation Engineer

    US-CSS DSC PROTOCOL TEAM

     

    Wednesday, October 20, 2010 5:21 PM
  • Hi Brad,

     

    [MS-OXCFXICS] Regarding NoRoom (0x0002), this should be interpreted as equivalent to Partial (0x0001).  In Exchange Server 2007 and prior versions of Exchange Server, clients had no reason to differentiate between these two values, so starting with Exchange Server 2010, only one of the values is returned, Partial (0x0001).

     

    Also,

    <11> Section 2.2.3.1.1.5.1: In Exchange 2007 and Exchange 2003 the Partial value (0x0001) and the NoRoom value (0x0002) both indicate that the FastTransfer stream was split, more data is available, and that TransferBuffer contains incomplete data. NoRoom is not returned by Exchange 2010.

     

    I hope this answers your question.

     

    Regards,

    Mark Miller

    Escalation Engineer

    US-CSS DSC PROTOCOL TEAM

    • Marked as answer by Brad Hards Tuesday, November 2, 2010 1:25 AM
    Monday, November 1, 2010 6:25 PM
  • Mark,

    Thanks for this.

    Brad

    Tuesday, November 2, 2010 1:25 AM