Welcome to MSDN Blogs Sign in | Join | Help
Configuring Distributed Transaction Coordinator (DTC) for use with Commerce Server Orders Adapter

There have been questions about how to setup Distributed Transaction Coordinator for use with the Commerce Server Orders Adapter.  The Orders Adapter uses Biztalk’s Transaction libraries which use DTC to communicate and control the transaction.  Below is a list of how to setup DTC in a multi-machine environment.    Perform these instructions on all machines that will contribute to the transaction (ie Biztalk Server, Commerce Server, Database Server)

 

To turn DTC Access on :
 
From the Start menu, double-click Control Panel, double-click 
 
Administrative Tools, and then double-click Component Services. 
 
Expand Component Services, and then expand Computers. 
 
Right-click the computer you need to set, and from the context menu select 
 
Properties. 
 
In the Properties window, select the MSDTC tab. 
 
In the Transaction Configuration area, click Security Configuration. 
 
In the Security Settings area, make sure the Network DTC Access check box 
 
is selected. 
 
In the Security Settings area, check the Network Clients check box. 

Check the "No Authentication Required" in the Transaction Manager Communication.
 
Click OK on each open dialog box. 
 
Restart your computer to enable the remote DTC option. 
 
Warning  This configuration could take up to 15 minutes. 
 

 

If you have any problems with this setup – please let me know.

 

 

Posted: Monday, March 27, 2006 3:13 PM by akfaulkner

Comments

Prasenjit Biswas said:

I configured MSDTC thru Component Services on both the CS and Client

(BizTalk) server boxes (I am using the Orders receive adapter).

NO LUCK, I get the same message from the Commerce Server Orders Receive

Adapter - "Failed submitting message to BizTalk." Always coupled with

it is the mssage from CrossTierTypes.TxHelper  - "The call to

ITransactionExport.Export failed.  Message: The transaction has already

been implicitly or explicitly committed or aborted...at

Microsoft.CommerceServer.Internal.TxHelper.GetCookieForTransaction(ITransac­tion

transaction, Byte[] whereabouts). "

Because DTC works over RPC, on a colleagues suggestion I disabled

"Restrictions for Unauthenticated RPC Clients". Did this via RUN -->

gpedit.msc --> Computer Configuration --> Administrative templates -->

Remote Procedure Calls --> Restrictions for Unauthenticated RPC Clients

--> Properties --> Disabled.

Did not work either. I then enabled Transaction Internet Protocol for

MSDTC on the server (CS) machine. This too did not work.

Could it be a firewall isssue?

Commerce Server and the SQL Server database are on the same machine.

Our CS machine is remote to the BizTalk client which uses it and

accesses it thru the Internet. Do I need to open Firewall to the DTC

port 3327 from the BizTalk box and/or the Commerce Server box?

If so this is a security flaw...

# November 3, 2006 6:50 PM

Ahmad said:

After Configuring the msdtc i agin get the new error.

That Is.

The transaction has already been implicitly or explicitly committed or aborted. if any body know how to handle this error please solve it

# November 6, 2008 4:59 AM
Leave a Comment

(required) 

(required) 

(optional)

(required) 

  
Enter Code Here: Required

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Page view tracker