Definitive steps to configure MSDTC on Azure virtual machines – without need of domain controller


MSDTC – Microsoft Dis07ibuted Transaction.

I had requirement to configure Azure Virtual machine with SQL Server 2008 R2 and One Azure Virtual machine as an application server having few sites hosted on it. Azure virtual machine app server hosted application should be able to connect to SQL server and run SQL queries with 07ansactions. Unfortunately 07ansaction queries were not working in my environment set up.

The problem is, for 07ansaction to work between SQL server and application server you need to have MSDTC to be configured on both machines. Everywhere I read through many posts that for configuring MSDTC, settings related to AD DC (domain con07oller) is required. However my azure virtual machines were not in any domain neither any one of them was 07eated as DC.

Hence I 07ied to configure MSDTC on azure virtual machines without domain configuration and it was successful.
Following steps will guide through the steps required to enable MSDTC on Azure virtual machines. Please note that the azure virtual machines do not have any domain configured on them neither they are not part of any domain.

I have 2 azure virtual machines with following configuration –

1.     SQL Server 2008 R2

2.     Windows Server 2008 R2 – call it as app server

Now I need to configure MSDTC on SQL server and app server.

At first you need to configure Azure virtual network as per the guidelines mentioned at this post.
http://www.windowsazure.com/en-us/documentation/articles/create-virtual-network/ 

Then provision Azure virtual machines with above configuration using the steps mentioned at this post in the virtual network you created above.
http://www.windowsazure.com/en-us/documentation/articles/virtual-networks-add-virtual-machine/ 

Now RDP to both Azure Virtual machines from the steps mentioned in this post.
http://www.windowsazure.com/en-us/documentation/articles/virtual-machines-windows-tutorial/#logon 

Then on SQL server make configuration settings mentioned on this post - http://www.windowsazure.com/en-us/documentation/articles/virtual-machines-provision-sql-server/#SSMS

Then log in to App server and follow below steps.

***MSDTC configuration***

Select Open Con07ol Panel -> System and Security -> Allow a program through windows firewall option as shown below.




Then select enable check mark for Dis07ibuted Transaction coordinator process as shown below.



Open Run window and type “Services.msc” and make sure that Dis07ibuted Transaction Coordinator process is started and in running mode.



Selection “Component Services” as shown below from Adminis07ative Tools.


Select properties of Local DTC as shown below –



On Local DTC properties select Security tab and make sure that you select check following options –

·         Network DTC access

·         Allow Inbound

·         Allow Outbound

·         No authentication required

·         Enable SNA LU 6.2 Transactions

Rest all of the options will be unchecked as shown below –



Follow all of the above steps under heading ***MSDTC configuration*** on SQL server as well. This way configure the same setting son both servers.

Testing MSDTC –

To test MSDTC configuration I created a two sample DB on SQL server with one table in each one of it. Then created a simple windows application to make insert statement in both databases using C# - TransactionScope - http://msdn.microsoft.com/en-us/library/system.07ansactions.07ansactionscope(v=vs.110).aspx 

07y
    {
        // Create the TransactionScope to execute the commands, guaranteeing
        // that both commands can commit or roll back as a single unit of work.
        using (TransactionScope scope = new TransactionScope())
        {
                // code to create connectiions to two databases and execution of insert statements using commands

               scope.Complete(); 
        } 
    }
    catch (TransactionAbortedException ex)
    {
        //write exception details to UI
    }

I ran the application on app server and found that my 07ansaction was committed as shown below –



If you want test application of MSDTC just comment your email id and i will share it with you. Hence this is how you can configure MSDTC on azure virtual machines. And to configure MSDTC domain availability is not required.

Hope this helps.

Cheers…

Happy Transacting!!!

Comments

Post a Comment

Popular posts from this blog

The request has both SAS authentication scheme and 'Bearer' authorization scheme. Only one scheme should be used

Image
While doing testing after doing a POC on Securing Logic App with Azure Active Directory authentication , where I have put logic app behind APIM and before passing the request to logic app, apim does validation of the token.  I was encountered with an error "The request has both SAS authentication scheme and 'Bearer' authorization  scheme.  Only one scheme should be used." Why it happened After validating the token which is part of the header i.e. Authorization, APIM forwards the request as it is to backend. As  Logic app is configured as  back end , it's url already consist of SAS signature plus the request also has Authorization section and this is the problem. By default every request endpoint on a logic app has a Shared Access Signature (SAS) in the endpoint's URL, which follows this format: https://<request-endpoint-URI>sp=<permissions>sv...
Read more

Getting Started with Logic Apps - AS2

Image
What is AS2? Every enterprise requires some kind of product, service or counselling from another enterprises thus there happens a B2B(business to business) communications, some of the communication is unique whereas most of the communications are common for most of the enterprises e.g., Purchase Order. But every enterprise has there own way(format) of sending the messages, leading to difficult management when number of partners increased.  Considering this the Enterprise leaders decided to have some standards/rules defined across the communication leading to B2B protocol standards which provide guidelines for trading partners to follow when conducting business between enterprises. EDI X12, EDIFACT, TRADACOM etc. AS2 stands for Applicability Statement 2 and is a B2B messaging protocol used to transmit Electronic Data Interchange (EDI)/Business documents from one organization to another. So EDI standards define how to format data and AS2 specifies how to securely transport...
Read more

How to Debug and Trace request in Azure APIM - Portal, Postman, RequestBin

Image
Introduction  APIM is a great option to expose API's with out of box features for applying restrictions, preprocessing, postprocessing etc. You can leverage existing API's,  by importing it and it gets added as a new API with all the operations associated with it. And based on the requirements you  apply policies at the stage/level (Inbound,Backend/Outbound) and you are ready to use the API. Before it is shared, we do some testing to make sure everything is working as per the expectation and this is where Debugging and Tracing request becomes important. APIM does provide a way to Trace a call with the help of  Ocp-Apim-Trace http header. So whichever request/call is to be traced, it needs to include this in header  with the value set to true and it has dependency on another header, so that also needs to be passed i.e.  Ocp-Apim-Subscription-Key Note: The api on which Tracing is to applied , it requires the subscription key to be en...
Read more