technical content. 10/24/2008 7.0 Major Updated and revised the technical content. 12/5/2008 8.0 Major Updated and revised the technical content. 1/16/2009 9.0 Major Updated and revised the technical content. 2/27/2009 10.0 Major Updated and revised the technical content. 4/10/2009 11.0 Major Updated and revised the technical content. 5/22/2009 12.0 Major Updated and revised the technical content. 7/2/2009 13.0 Major Updated and revised the technical content. 8/14/2009 13.1 Minor Clarified the meaning of the technical content. 9/25/2009 14.0 Major Updated and revised the technical content. 11/6/2009 15.0 Updated and revised the technical content. 12/18/2009 16.0 Major Updated and revised the technical content. 1/29/2010 17.0 Major Updated and revised the technical content.
3/12/2010 18.0 Major Updated and revised the technical content. 4/23/2010 19.0 Updated and revised the technical content. 6/4/2010 20.0 Major Updated and revised the technical content. 7/16/2010 20.0 None No changes to the meaning, language, or formatting of the technical content. 8/27/2010 20.0 None No changes to the meaning, language, or formatting of the technical content. 10/8/2010 20.0 None No changes to the meaning, language, or formatting of the technical content. 11/19/2010 20.0 None No changes to the meaning, language, or formatting of the technical content. 1/7/2011 21.0 Major Updated and revised the technical content. 2/11/2011 22.0 Major Updated and revised the technical content. 3/25/2011 22.0 None No changes to the meaning, language, or formatting of the technical content. 5/6/2011 22.0 None No changes to the meaning,
language, or formatting of the technical content. 6/17/2011 22.1 Minor Clarified the meaning of the technical content. 9/23/2011 22.1 None No changes to the meaning, language, or formatting of the technical content. 12/16/2011 23.0 Major Updated and revised the technical content. 3/30/2012 23.0 None No changes to the meaning, language, or formatting of the technical content. 7/12/2012 23.0 None No changes to the meaning, language, or formatting of the technical content. 10/25/2012 23.1 Minor Clarified the meaning of the technical content. 1/31/2013 23.1 None No changes to the meaning, language, or formatting of the technical content. 8/8/2013 23.2 Minor Clarified the meaning of the technical content. 11/14/2013 23.2 None No changes to the meaning, language, or formatting of the technical content. 2/13/2014 23.2 None No changes to the meaning,
0x000006BB RPC_S_SERVER_TOO_BUSY The return value indicates that the partner is too busy to complete this operation. For more information, see section 3.1.1.5.5. 0x80000173 E_CM_S_PROTOCOL_NOT_SUPPORTED The return value indicates that none of the protocols described in the rguchBlob parameter are supported by the partner. 0x80070057 E_INVALIDARG The return value indicates that one of the specified arguments is invalid. The following table of return values describes the possible errors that SHOULD be returned by this method. Return value/code Description 0x80000120 E_CM_SESSION_DOWN In a scenario where the value of the sRank parameter is SRANK_SECONDARY, if BuildContext is called and an existing session object is not found, the call SHOULD return this value.<21> 0x80000123 E_CM_SERVER_NOT_READY The session object is not in the Connecting The field value for this method is 1. For more information, see [C706]. This method has different effects depending on the of the sRank parameter. For the structure and sequence of data on the wire, see [C706] Transfer Syntax topics. Primary
0x00000000 ERROR_STATUS The return value indicates success. 0x80000172 E_CM_VERSION_SET_NOTSUPPORTED The return indicates that the callee partner does not support the caller's BindVersionSet parameter and will not execute the requested operation. 0x000006D1 RPC_S_PROCNUM_OUT_OF_RANGE The return value indicates that the caller does not support this call. 0x80000124 E_CM_S_TIMEDOUT The return value indicates that the callee timed out while waiting for the caller to complete the bind. This value is returned by a secondary partner to a primary partner if the primary partner does not return from the secondary partner's call to BuildContext within half the amount of time specified in the . 0x000006BB RPC_S_SERVER_TOO_BUSY The return value indicates that the partner is too busy to complete this operation. For more information, see section 3.1.1.5.5.
Messages 16 16 16 16 16 12 51 16 Methods 42 33 44 38 30 43 39 40 N 26 26 38 38 58 8 O 9 9 P 62 9 22 30 30 43 43 13 13 52 48 50 66 Protocol Details 21 16 R 8 9 8 13 51 12 20 9 S 55 49 Security 62 16 62 39 39 Sequencing rules 48 27 30 Server 28 42 33 44 29 47 30 38 30 43 39 30 40 46 29 Session 50 51 25 48 50 48 51 49 timer ( 26, 27) 23 teardown timer ( 26, 28) 25 20 Sessions 10 10 12 12 13 Setup timer - session ( 26, 27) 15 T Teardown timer - session ( 26, 28) 40 40 20 59 59 60 59 Timer events 48 27