Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All

6 Appendix A: Product Behavior

The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include released service packs.

Note: Some of the information in this section is subject to change because it applies to an unreleased, preliminary version of the Windows Server operating system, and thus may differ from the final version of the server software when released. All behavior notes that pertain to the unreleased, preliminary version of the Windows Server operating system contain specific references to Windows Server 2016 Technical Preview as an aid to the reader.

  • Windows NT operating system

  • Windows 2000 operating system

  • Windows XP operating system

  • Windows Server 2003 operating system

  • Windows Vista operating system

  • Windows Server 2008 operating system

  • Windows 7 operating system

  • Windows Server 2008 R2 operating system

  • Windows 8 operating system

  • Windows Server 2012 operating system

  • Windows 8.1 operating system

  • Windows Server 2012 R2 operating system

  • Windows 10 operating system

  • Windows Server 2016 Technical Preview operating system

Exceptions, if any, are noted below. If a service pack or Quick Fix Engineering (QFE) number appears with the product version, behavior changed in that service pack or QFE. The new behavior also applies to subsequent service packs of the product unless otherwise specified. If a product edition appears with the product version, behavior is different in that product edition.

Unless otherwise specified, any statement of optional behavior in this specification that is prescribed using the terms SHOULD or SHOULD NOT implies product behavior in accordance with the SHOULD or SHOULD NOT prescription. Unless otherwise specified, the term MAY implies that the product does not follow the prescription.

<1> Section 2.2.3.2.5:  On Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2, the provided values of the lenDSN field are confirmed to be less than 256.

<2> Section 2.2.4.1: CONNTYPE_XAUSER_XACT_MIGRATE connection type is not supported by Windows NT 4.0 operating system Option Pack for Windows NT Server or Windows XP.

<3> Section 2.2.4.1: CONNTYPE_XAUSER_XACT_MIGRATE2 connection type is not supported by Windows 2000, Windows Server 2003, or Windows Vista. CONNTYPE_XAUSER_XACT_MIGRATE connection type is used instead. CONNTYPE_XAUSER_XACT_MIGRATE2 and CONNTYPE_XAUSER_XACT_MIGRATE are not supported by Windows NT 4.0 Option Pack or Windows XP.

<4> Section 2.2.4.1: CONNTYPE_XAUSER_XACT_BRANCH_START and CONNTYPE_XAUSER_XACT_BRANCH_OPEN connection types are not supported by Windows NT 4.0 Option Pack, Windows 2000, Windows XP, Windows Server 2003, or Windows Vista.

<5> Section 2.2.4.1: CONNTYPE_XAUSER_XACT_BRANCH_START and CONNTYPE_XAUSER_XACT_BRANCH_OPEN connection types are not supported by Windows NT 4.0 Option Pack, Windows 2000, Windows XP, Windows Server 2003, or Windows Vista.

<6> Section 2.2.4.2.4: When processing an XAUSER_CONTROL_MTAG_RECOVER message, the value of Total UOWs Requested is not verified to be valid on Windows NT 4.0 Option Pack, Windows 2000, or Windows XP. On Windows Server 2003 it is only verified not to be 0.

<7> Section 2.2.4.2.4: When processing an XAUSER_CONTROL_MTAG_RECOVER message, the value used for Total UOWs Requested is set to the minimum value between the provided value and 10000 on Windows Server 2003 RTM.

<8> Section 2.2.4.2.4: The provided Count is not minimized by an implementation-specific value when processing an xa_recover event on Windows NT 4.0 Option Pack, Windows 2000, or Windows XP. When sending an XAUSER_CONTROL_MTAG_RECOVER (section 2.2.4.2.4) message, Windows implementations limit the value of the totalUOWsRequested field and the Open Count field of the XA Superior Proxy object to a maximum of 5.

<9> Section 2.2.4.2.6: When processing an XAUSER_CONTROL_MTAG_RECOVER_REPLY (section 2.2.4.2.6) message on Windows NT 4.0 Option Pack, Windows 2000, Windows XP, and Windows Server 2003, the provided ultotalUOWs field is not validated to be less than the number of requested XIDs (totalUOWsRequested).

<10> Section 2.2.4.3.1: Setting the Timeout of a transaction created by an xa_start call is not supported on Windows NT 4.0 Option Pack, Windows 2000, Windows XP, and Windows Server 2003. The default value of 0x00000000 is used.

<11> Section 3.2.5.1.2: When processing an XAUSER_CONTROL_MTAG_RECOVER message, the value of Total UOWs Requested is not verified to be valid on Windows NT 4.0 Option Pack, Windows 2000, or Windows XP. On Windows Server 2003, it is only verified not to be 0.

<12> Section 3.2.5.1.2: When processing an XAUSER_CONTROL_MTAG_RECOVER message, the value that Windows implementations use as a maximum for totalUOWsRequested is 10000.

<13> Section 3.2.5.1.2: When processing a XAUSER_CONTROL_MTAG_RECOVER message, the value that Windows implementations use as a maximum for totalUOWsRequested is 10000.

<14> Section 3.2.5.1.2: When iterating over available XA Superior Enlistment Objects during processing of an XAUSER_CONTROL_MTAG_RECOVER (section 2.2.4.2.4) message on Windows NT 4.0 Option Pack, no check is performed, and the actions are taken for all XA Superior Enlistment Objects. Under the same conditions, only XA Superior Enlistment Objects in the Preparing State are returned.

<15> Section 3.2.5.2.2: A Connection Disconnected (section 3.2.5.2.2) event on a CONNTYPE_XAUSER_XACT_START (section 2.2.4.3), CONNTYPE_XAUSER_XACT_OPEN (section 2.2.4.5), CONNTYPE_XAUSER_XACT_BRANCH_START (section 2.2.4.4), or CONNTYPE_XAUSER_XACT_BRANCH_OPEN (section 2.2.4.6) connection type is not processed on Windows NT 4.0 Option Pack, Windows 2000, Windows XP, or Windows Server 2003.

<16> Section 3.2.5.3.5: A Connection Disconnected (section 3.2.5.3.5) event on a CONNTYPE_XAUSER_XACT_START (section 2.2.4.3), CONNTYPE_XAUSER_XACT_OPEN (section 2.2.4.5), CONNTYPE_XAUSER_XACT_BRANCH_START (section 2.2.4.4), or CONNTYPE_XAUSER_XACT_BRANCH_OPEN (section 2.2.4.6) connection type is not processed on on Windows NT 4.0 Option Pack, Windows 2000, Windows XP, or Windows Server 2003.

<17> Section 3.2.5.5.2: A Connection Disconnected (section 3.2.5.5.2) event on a CONNTYPE_XAUSER_XACT_START (section 2.2.4.3), CONNTYPE_XAUSER_XACT_OPEN (section 2.2.4.5), CONNTYPE_XAUSER_XACT_BRANCH_START (section 2.2.4.4), or CONNTYPE_XAUSER_XACT_BRANCH_OPEN (section 2.2.4.6) connection type is not processed on on Windows NT 4.0 Option Pack, Windows 2000, Windows XP, or Windows Server 2003.

<18> Section 3.2.5.6.5: A Connection Disconnected (section 3.2.5.6.5) event on a CONNTYPE_XAUSER_XACT_START (section 2.2.4.3), CONNTYPE_XAUSER_XACT_OPEN (section 2.2.4.5), CONNTYPE_XAUSER_XACT_BRANCH_START (section 2.2.4.4), or CONNTYPE_XAUSER_XACT_BRANCH_OPEN (section 2.2.4.6) connection type is not processed on Windows NT 4.0 Option Pack, Windows 2000, Windows XP, or Windows Server 2003.

<19> Section 3.3.3: The XATransactions registry key, defined in [MS-CMOM] section 3.3.1.2.1, is not supported on Windows NT 4.0 Option Pack, Windows 2000, and Windows XP.

<20> Section 3.3.4.3: Disabling Require Thread Affinity is not supported on Windows NT 4.0 Option Pack and Windows XP, and thus Require Thread Affinity is always set to TRUE.

<21> Section 3.3.4.5: CONNTYPE_XAUSER_XACT_MIGRATE2 connection type is not supported by Windows 2000, Windows Server 2003 or, Windows Vista. CONNTYPE_XAUSER_XACT_MIGRATE connection type is used instead. CONNTYPE_XAUSER_XACT_MIGRATE2 and CONNTYPE_XAUSER_XACT_MIGRATE are not supported by Windows NT 4.0 Option Pack or Windows XP.

<22> Section 3.3.4.5: The CONNTYPE_XAUSER_XACT_MIGRATE2 (section 2.2.4.8) connection type is not supported by Windows 2000, Windows Server 2003, or Windows Vista; the CONNTYPE_XAUSER_XACT_MIGRATE (section 2.2.4.7) connection type is used instead. The CONNTYPE_XAUSER_XACT_MIGRATE2 and CONNTYPE_XAUSER_XACT_MIGRATE connection types are not supported by the Windows NT 4.0 Option Pack or Windows XP; a result of XA_RMFAIL is returned when attempting to connect.

<23> Section 3.3.4.7: Setting the Timeout of a transaction created by an xa_open call is not supported on Windows NT 4.0 Option Pack, Windows 2000, Windows XP, and Windows Server 2003. The default value of INFINITE is used.

<24> Section 3.3.4.7: CONNTYPE_XAUSER_XACT_BRANCH_START and CONNTYPE_XAUSER_XACT_BRANCH_OPEN connection types are not supported by Windows NT 4.0 Option Pack, Windows 2000, Windows XP, Windows Server 2003, or Windows Vista.  However, Windows Server 2003 operating system with Service Pack 2 (SP2) will support these connection types if updated using the hotfix located here: [KB938653].

<25> Section 3.3.4.8: Disabling Require Thread Affinity is not supported on Windows NT 4.0 Option Pack and Windows XP, and thus Require Thread Affinity is always set to TRUE.

<26> Section 3.3.4.9: On Windows NT 4.0 Option Pack, Windows 2000, and Windows XP, the Recovery Complete field is not supported.

<27> Section 3.3.4.9: On Windows NT 4.0 Option Pack, Windows 2000, and Windows XP, the Recovery Complete field is not supported.

<28> Section 3.3.4.9: On Windows NT 4.0 Option Pack, Windows 2000, and Windows XP, the Recovery Complete field is not supported.

<29> Section 3.3.4.9: On Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2 operating system, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2, the XARECOVER_END_SCAN flag is not set.

<30> Section 3.3.4.9: The Flags argument provided for the xa_recover event is not validated on Windows NT 4.0 Option Pack, Windows 2000, and Windows XP; therefore, on these versions, XAER_INVAL is not returned if TMSTARTSCAN is not set, AND TMENDSCAN is not set, but the provided Flags argument is not TMNOFLAGS.

<31> Section 3.3.4.9: The value provided to the Recovery Request Number field will not be minimized between the provided Count value and an implementation specific value when processing an xa_recover event on Windows NT 4.0 Option Pack, Windows 2000, and Windows XP.

<32> Section 3.3.4.9: The value provided to the Recovery Request Number field will not be minimized between the provided Count value and an implementation specific value when processing an xa_recover event on Windows NT 4.0 Option Pack, Windows 2000, and Windows XP.

<33> Section 3.3.4.10: Disabling Require Thread Affinity is not supported on Windows NT 4.0 Option Pack and Windows XP, and thus Require Thread Affinity is always set to TRUE.

<34> Section 3.3.4.11: The CONNTYPE_XAUSER_XACT_MIGRATE2 connection type is not supported by Windows 2000, Windows Server 2003, or Windows Vista. The CONNTYPE_XAUSER_XACT_MIGRATE connection type is used instead. The CONNTYPE_XAUSER_XACT_MIGRATE2 and CONNTYPE_XAUSER_XACT_MIGRATE connection types are not supported by the Windows NT 4.0 Option Pack or Windows XP.

<35> Section 3.3.4.11: Calling Xa_start with TMJOIN will not resume a Suspended transaction on Windows NT 4.0 Option Pack and Windows XP.

<36> Section 3.3.4.11: Disabling Require Thread Affinity is not supported on Windows NT 4.0 Option Pack or Windows XP, and thus Require Thread Affinity is always set to TRUE.

<37> Section 3.3.4.11: The CONNTYPE_XAUSER_XACT_MIGRATE2 connection type is not supported by Windows 2000, Windows Server 2003, or Windows Vista. The CONNTYPE_XAUSER_XACT_MIGRATE connection type is used instead. The CONNTYPE_XAUSER_XACT_MIGRATE2 and CONNTYPE_XAUSER_XACT_MIGRATE connection types are not supported by the Windows NT 4.0 Option Pack or Windows XP.

<38> Section 3.3.4.11: Disabling Require Thread Affinity is not supported on Windows NT 4.0 Option Pack or Windows XP, and thus Require Thread Affinity is always set to TRUE.

<39> Section 3.3.5.1.4: On Windows NT 4.0 Option Pack and Windows 2000, if the connection is disconnected while waiting for an Abort or a Commit response, a result of XA_RBCOMMFAIL is returned.

<40> Section 3.3.5.1.4: When sending an XAUSER_CONTROL_MTAG_RECOVER (section 2.2.4.2.4) message, Windows implementations limit the values of the totalUOWsRequested field and the Open Count field of the XA Superior Proxy object to a maximum of 5.

<41> Section 3.3.5.3.7: Losing connection when waiting for an Abort or Commit response will result in a result of XA_RBCOMMFAIL being returned on Windows NT 4.0 Option Pack and Windows 2000.

<42> Section 3.3.5.3.7: Losing connection when waiting for an Abort or Commit response will result in a result of XA_RBCOMMFAIL being returned on Windows NT 4.0 Option Pack and Windows 2000.

<43> Section 3.3.5.6.8: Losing connection when waiting for an Abort or Commit response will cause a result of XA_RBCOMMFAIL being returned on Windows NT 4.0 Option Pack and Windows 2000.

<44> Section 3.3.5.6.8: Losing connection when waiting for an Abort or Commit response will cause a result of XA_RBCOMMFAIL being returned on Windows NT 4.0 Option Pack and Windows 2000.

<45> Section 3.3.5.7.6: The CONNTYPE_XAUSER_XACT_MIGRATE2 connection type is not supported by Windows 2000, Windows Server 2003, or Windows Vista. If the Transaction Manager does not support this connection type and a MTAG_CONNECTION_REQ_DENIED is returned, the connection type will be converted to CONNTYPE_XAUSER_XACT_MIGRATE and processing continues.

<46> Section 3.4.3.1: On Windows 2000, Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, Windows Server 2012 R2, Windows 10, and Windows Server 2016 Technical Preview,  the XaTmMinWarmRecoveryInterval is initialized to 15 seconds and is configurable to a positive number of seconds.

<47> Section 3.4.3.1: On Windows 2000, Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, Windows Server 2012 R2, Windows 10, and Windows Server 2016 Technical Preview, the XaTmMaxWarmRecoveryInterval is initialized to 600 seconds and is configurable to a positive number of seconds.

<48> Section 3.4.4.1: The Recovery Interval of all XA resource managers is set to 60 seconds on Windows NT 4.0 Option Pack.

<49> Section 3.4.5.1.1: On Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2, the provided values of the lenDSN field in an XATMUSER_MTAG_RMOPEN (section 2.2.3.2.5) message are confirmed to be less than 256. On Windows 10 and Windows Server 2016 Technical Preview, the provided values of the lenDSN field in an XATMUSER_MTAG_RMOPEN (section 2.2.3.2.5) message are confirmed to be less than 3072.

<50> Section 3.4.5.1.1: On Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, Windows Server 2012 R2, Windows 10, and Windows Server 2016 Technical Preview, the provided values of the lenXaDll field in an XATMUSER_MTAG_RMOPEN (section 2.2.3.2.5) message are confirmed to be less than 256.

<51> Section 3.4.5.1.1: The Recovery Interval of all XA resource managers is set to 60 seconds on Windows NT 4.0 Option Pack.

<52> Section 3.4.5.1.1: When an error condition other than those specified occurs during the processing of an XATMUSER_ MTAG_RMOPEN message, a message with an invalid MTAG is sent back on Windows NT 4.0 Option Pack.

<53> Section 3.4.5.1.1: On Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2, if the value of the lenDSN field or the lenXaDll field in an XATMUSER_MTAG_RMOPEN (section 2.2.3.2.5) message is greater than 256, an XATMUSER_MTAG_E_RMOPENFAILED (section 2.2.3.2.3) response message is sent, and the Connection State is set to Ended. On Windows 10 and Windows Server 2016 Technical Preview, if the value of the lenDSN field in an XATMUSER_MTAG_RMOPEN (section 2.2.3.2.5) message is greater than 3072 or the lenXaDll field in an XATMUSER_MTAG_RMOPEN (section 2.2.3.2.5) message is greater than 256, an XATMUSER_MTAG_E_RMOPENFAILED (section 2.2.3.2.3) response message is sent, and the Connection State is set to Ended. On Windows NT, Windows 2000, and Windows XP, the message is ignored, and the Connection State remains at Processing Open Request.

<54> Section 3.4.5.2.1: On Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2, the provided values of the lenDSN field in an XATMUSER_MTAG_RMOPEN (section 2.2.3.2.5) message are confirmed to be less than 256. On Windows 10, and Windows Server 2016 Technical Preview, the provided values of the lenDSN field in an XATMUSER_MTAG_RMOPEN (section 2.2.3.2.5) message are confirmed to be less than 3072.

<55> Section 3.4.5.2.1: On Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, Windows Server 2012 R2, Windows 10, and Windows Server 2016 Technical Preview the provided values of the lenXaDll field in an XATMUSER_MTAG_RMOPEN (section 2.2.3.2.5) message are confirmed to be less than 256.

<56> Section 3.4.5.2.1: The Recovery Interval of all XA resource managers is set to 60 seconds on Windows NT 4.0 Option Pack.

<57> Section 3.4.7.6: The Recovery Interval of an XA resource manager is not increased after signaling the Recovery Interval Timer (section 3.4.2.1) on Windows NT 4.0 Option Pack.

<58> Section 3.4.7.6: The Recovery Interval of an XA resource manager is not increased after signaling the Recovery Interval Timer (section 3.4.2.1) on Windows NT 4.0 Option Pack.

<59> Section 3.5.4.3: On Windows NT 4.0 Option Pack, the value of tmprotUsed field of an STxInfo is set to 2.

Show:
© 2015 Microsoft