HowTo:Solve MSDTC-related problems - Revision history

NWE at 08:36, 25 August 2023

2023-08-25T08:36:41Z

NWE at 10:41, 17 August 2023

2023-08-17T10:41:36Z

NWE at 10:40, 17 August 2023

2023-08-17T10:40:16Z

NWE at 23:07, 16 August 2023

2023-08-16T23:07:05Z

NWE at 23:04, 16 August 2023

2023-08-16T23:04:40Z

NWE at 23:04, 16 August 2023

2023-08-16T23:04:01Z

NWE at 22:51, 16 August 2023

2023-08-16T22:51:15Z

NWE at 22:50, 16 August 2023

2023-08-16T22:50:09Z

NWE at 22:45, 16 August 2023

2023-08-16T22:45:07Z

NWE at 22:43, 16 August 2023

2023-08-16T22:43:54Z

← Older revision		Revision as of 08:36, 25 August 2023
Line 1:		Line 1:
	From version 4 on, {{UBIK}} uses the Distributed Transaction Coordinator (MSDTC or DTC) to manage database transactions. However, there's the necessity for correct configuration on both the database server as well as the application server to make it work. This article explains how to do that.		From version 4 on, {{UBIK}} uses the Distributed Transaction Coordinator (MSDTC or DTC) to manage database transactions. However, there's the necessity for correct configuration on both the database server as well as the application server to make it work. This article explains how to do that.
		+
		+	{{hint\|On Microsoft Azure SQL Database services, MSDTC is not supported - but apparently, it's not needed either (as documented [[https://learn.microsoft.com/en-us/azure/azure-sql/database/elastic-transactions-overview?view=azuresql here]]). So If you don't face any problems this article can be ignored when working with Azure SQL Database.}}
		+

	== Problem Symptoms ==		== Problem Symptoms ==

@@ Line 80: / Line 80: @@
 There are several tools you can use to test the correct configuration and function of the MSDTC on both your client and the host machine.
-{{hint|It might pay off to check whether the "Distributed Transaction Coordinator" (MSDTC) Windows Service is running on the database server. You may wish to set the startup type to "Automatic".}}
+{{hint|It might pay off to check whether the "Distributed Transaction Coordinator" (MSDTC) Windows Service is running on the database server. You may wish to set the startup type to "Automatic". If it cannot be started, please check the Event Manager for errors.}}
 === Test-Dtc ===

@@ Line 76: / Line 76: @@
 * [https://learn.microsoft.com/en-us/powershell/module/netsecurity/new-netfirewallrule?view=windowsserver2022-ps Powershell New-NetFirewallRule (learn.microsoft.com)]
-= Test-Dtc and DTCPing =
+= Testing =
 === Test-Dtc ===

@@ Line 95: / Line 95: @@
 {{hint|The DTCPing program has to run on both the host and the client machine.}}
 <!-- DO NOT REMOVE THIS -->{{Template:HowTo/End}}<!-- DO NOT REMOVE THIS -->
 [[Category:Database|Solve MSDTC-related problems]]

@@ Line 17: / Line 17: @@
 * [https://learn.microsoft.com/en-us/troubleshoot/windows-server/application-management/enable-network-dtc-access?source=recommendations Enable Network DTC Access (learn.microsoft.com)]
 * Open the "Component Services" console (typing that into the Windows start menu should find you the right app)
 * In the Component Services console, you should see a tree view to the left.

@@ Line 14: / Line 14: @@
 The configuration is described here:
-https://stackoverflow.com/questions/7694/how-do-i-enable-msdtc-on-sql-server
+* [https://stackoverflow.com/questions/7694/how-do-i-enable-msdtc-on-sql-server How do I enable MSDTC on SQL Server (StackOverflow)]
-https://learn.microsoft.com/en-us/troubleshoot/windows-server/application-management/enable-network-dtc-access?source=recommendations
+* [https://learn.microsoft.com/en-us/troubleshoot/windows-server/application-management/enable-network-dtc-access?source=recommendations Enable Network DTC Access (learn.microsoft.com)]
 * Open the "Component Services" console (typing that into the Windows start menu should find you the right app)
@@ Line 41: / Line 41: @@
 {{attention|There should be an existing enabled rule for this already, but the RPC port 135 must be opened.}}
-There are two strategies to open the required ports:
+There are two different strategies to open the required ports:
-* Enable the (preconfigured) firewall rules for dynamic MSDTC ports
+* Enable the (preconfigured) firewall rules for dynamic MSDTC ports (recommended if possible)
-* Configure a fixed port for MSDTC and customize the port range for RPC, and open those ports on the firewall
+* Configure a fixed port for MSDTC and customize the port range for RPC, and open those ports on the firewall (only recommended if the IT security policy requires it)
-The latter should only be necessary if the customer's IT security policy requires it (e.g., if there's an external firewall that doesn't care much about the dynamic ports in your database server).
+Custom ports should only be necessary if the customer's IT security policy requires it (e.g., if there's an external firewall that doesn't care much about the dynamic ports in your database server).
 {{attention|Please make sure the firewall is configured correctly both on the client machine (e.g., the application server) and the host machine (e.g., the DB server).}}
-{{hint|Cusotmizing the dynamic ports mostly makes sense on the DB server, but it might also be necessary on the client machine depending on the customer's IT security policy.}}
+{{hint|Customizing the dynamic ports mostly makes sense on the DB server, but it might also be necessary on the client machine depending on the customer's IT security policy.}}
 === Default dynamic ports ===
-If you use the default dynamic ports, there are three different ways of adding the firewall rules to open them:
+If you use the default dynamic ports, there are different ways of adding the firewall rules to open them:
 * Powershell: <source lang="winbatch">Enable-NetFirewallRule -DisplayGroup "Distributed Transaction Coordinator"</source>
 * Netsh: <source lang="winbatch">netsh advfirewall firewall set rule group="Distributed Transaction Coordinator" new enable=yes</source>
-* Or use Windows Firewall Advanced Settings, enabling the 3 Inbound and 1 Outbound Rules regarding the "Distributed Transaction Coordinator"
+* Windows Firewall Advanced Settings UI: Enable the 3 Inbound and 1 Outbound Rules regarding the "Distributed Transaction Coordinator"
 === Custom dynamic ports ===
 Here it is described how to configure a specific port for MSDTC and how to customize the port range used by RPC:
-https://learn.microsoft.com/en-us/troubleshoot/windows-server/application-management/configure-dtc-to-work-through-firewalls
+* [https://learn.microsoft.com/en-us/troubleshoot/windows-server/application-management/configure-dtc-to-work-through-firewalls Configure DTC to work through firewalls (learn.microsoft.com)]
 Long story short, we have to add a couple of registry entries:
@@ Line 72: / Line 73: @@
 Here's a documentation about how to add firewall rules with the Powershell:
+* [https://learn.microsoft.com/en-us/powershell/module/netsecurity/new-netfirewallrule?view=windowsserver2022-ps Powershell New-NetFirewallRule (learn.microsoft.com)]
 https://learn.microsoft.com/en-us/powershell/module/netsecurity/new-netfirewallrule?view=windowsserver2022-ps
 = Test-Dtc and DTCPing =
@@ Line 79: / Line 79: @@
 === Test-Dtc ===
 You can use the Powershell module (or cmdlet) "Test-Dtc" to check if everything was configured correctly:
+* [https://learn.microsoft.com/en-us/powershell/module/msdtc/test-dtc?view=windowsserver2022-ps&source=recommendations Test-Dtc (learn.microsoft.com)]
 https://learn.microsoft.com/en-us/powershell/module/msdtc/test-dtc?view=windowsserver2022-ps&source=recommendations
 {{hint|For an end-to-end test, you have to open an inbound port for the resource manager service created by this (3002 by default, but you can specify a different one).}}
@@ Line 86: / Line 85: @@
 === DTCPing ===
 Also, the DTCPing tool can be applied to test the correct setup:
+* [https://learn.microsoft.com/en-us/troubleshoot/windows-server/application-management/ms-dtc-connectivity-issues?source=recommendations Trouble-shoot MSDTC connectivity issues (learn.microsoft.com)]
 https://learn.microsoft.com/en-us/troubleshoot/windows-server/application-management/ms-dtc-connectivity-issues?source=recommendations
 A good thing about this program is that it makes you notice to use the involved machine's names instead of IP addresses.
 Here's a link to a detailed article describing how to trouble-shoot MSDTC issues using the DTCPing tool:
+* [https://puneet-gupta.github.io/puneetgupta/2008/11/12/troubleshooting-msdtc-issues-with-the-dtcping-tool/ Trouble-shooting MSDTC issues with DTCPing (puneet-gupta.github.io)]
 https://puneet-gupta.github.io/puneetgupta/2008/11/12/troubleshooting-msdtc-issues-with-the-dtcping-tool/
 {{hint|The DTCPing program has to run on both the host and the client machine.}}

← Older revision		Revision as of 22:50, 16 August 2023
Line 70:		Line 70:

	{{attention\|If you use a custom ports range, you have to create new rules to open that range specifically (inbound and outbound).}}		{{attention\|If you use a custom ports range, you have to create new rules to open that range specifically (inbound and outbound).}}
		+
		+	Here's a documentation about how to add firewall rules with the Powershell:
		+
		+	https://learn.microsoft.com/en-us/powershell/module/netsecurity/new-netfirewallrule?view=windowsserver2022-ps

	= Test-Dtc and DTCPing =		= Test-Dtc and DTCPing =