Menu
We're in the process of moving our SQL Server to it's own machine, but I'm having issues getting transactions through MSDTC to work.
Here is the error message ASP.Net is generating for me:
The transaction manager has disabled its support for remote/network transactions
I have tried googling around for this, but haven't managed to find much other than a guide of how to solve this for Windows 2003.
Can anyone tell me how to solve this issue on Windows 2008? (Both SqlServer + IIS box are running Win 2k8).
Thanks!
454
To ensure that MSDTC communications are not blocked between computers, add msdtc.exe to the Windows Firewall exception list if the Windows Firewall service is running. Click Start, click Run, type firewall. cpl, and then click OK to display the Windows Firewall dialog box.
MSDTC on the database server computer uses RPC dynamic port allocation to randomly select a port number ranging from 1024 to 65535 for communication with the central computer.
It can be done from Component Services. Microsoft have jiggled the tool around this from Vista onwards. If Component Services isn't available on your Administrative Tools menu, goto Start>Run and type in 'dcomcnfg'.
Then you need to navigate the hierarchy as follows: Computers > My Computer > Distributed Transaction Coordinator > Local DTC.
Then right-click on Local DTC, select Properties ... and then select the Security tab. From this tab, you should be able to switch on Network DTC.
You might also need to add an exception for DTC into the Windows Firewall.
More details (included recommended settings, and firewall twiddling) at Microsoft on Technet behind this link... Enabling DTC Network Acccess (Vista/2008)
84
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
