ITipTransaction::Push

 

Applies To: Windows 10, Windows 7, Windows 8, Windows 8.1, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server Technical Preview, Windows Vista

A call to this method causes the Transaction Manager (TM) to send the TIP push command to the remote TIP transaction manager. The transaction identifier accompanying the push command is a string form of the Unit of Work Identifier of the transaction object on which the ITipTransaction::Push call was made. For the DTC, the string form of the Unit of Work Identifier is the string "oletx-" followed by the string form of a Universally Unique Identifier (UUID); that is, it is of the form "oletx-XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX", where the Xs are the ASCII representation of hexadecimal digits.

Note

The TIP service feature is deprecated. The TIP service feature and all related APIs are available for use in the operating systems listed in the Requirements sections of the reference topics for those APIs. They might be unavailable in subsequent versions of the operating system. You might consider using the WS-AtomicTransaction (WS-AT) protocol as a replacement transaction coordination and propagation technology. WS-AT support is provided through Windows Communication Foundation (WCF) as part of the .Net Framework. For more information about WS-AT support in the .Net Framework see Transactions.

Syntax

  
    HRESULT Push( char * pszRemoteTmUrl,   
char ** ppszRemoteTxUrl);  

Parameters

pszRemoteTmUrl
[in] Specifies the destination transaction manager's TIP TM URL.

ppszRemoteTxUrl
[out] Returns the TIP Transaction URL identifying the transaction on the remote TM. The application must free this parameter by calling CoTaskMemFree after it is finished using it.

Return Values

S_OK
Success—the transaction push completed.

E_OUTOFMEMORY
Failure—out of resources.

E_INVALIDARG
Failure—one or more parameters are not valid.

E_FAIL
Failure—generic failure while pushing the transaction to the remote transaction manager.

E_UNEXPECTED
Failure—an unexpected error occurred.

XACT_E_TMNOTAVAILABLE
Failure—unable to establish a connection with DTC service.

XACT_E_CONNECTION_DOWN
Failure—the connection to the local transaction manager is down.

XACT_E_CONNECTION_DENIED
Failure—the transaction manager refused to accept a connection.

XACT_E_LOGFULL
Failure—the transaction manager's log is full.

XACT_E_NOTRANSACTION
Failure—the transaction has already committed or aborted.

XACT_E_TIP_DISABLED
Failure—the Transaction Internet Protocol (TIP) service is disabled by default.

Requirements

For an explanation of the requirement values, see Requirements (Component Services).

Platforms: Windows Server 2016, Windows 10, Windows Server 2012 R2, Windows 8.1, Windows Server 2012, Windows 8, Windows Server 2008 R2, Windows 7, Windows Server 2008, Windows Vista

Header: Declared in txcoord.h

See Also

ITipHelper
ITipPullSink