Skip to main content

Testing Distributed Transaction Coordinator(DTC) settings using DTCTester

After a datacenter move, we had some network changes that caused distributed transactions involving the DTC to fail.

To help me find the root cause of the issue I used the DTC tester tool created by Microsoft. Let me explain how to use it:

Installation

C:\Users\BaWu\Desktop>dtctester
Too few parameters
Usage: dtctester <dsn name> <user name> <password>

  • The tool requires 3 parameters to be used;
    • A data source name(DSN)
    • A user name
    • A password

Creating a DSN

  • Next step is to create a User DSN for the database we want to connect to.
  • Click on your Windows start icon and start typing ‘data sources’

image

  • Select the ODBC Data Sources (32-bit) option. The ODBC Data Sources Administrator tool is loaded.

image

  • On the User DSN tab click Add… This will open the Create New Datasource Wizard.

image

  • Select the SQL Server driver from the list and click Finish. The current wizard is closed and a new Create new Data Source for SQL Server wizard is loaded.

image

  • Type in a Name for the DSN, an (optional) description and most important your SQL Server name / Instance name. Click Next > to continue.

image

  • On the next screen, select the preferred authentication method. In my case I’m using SQL Server authentication so I select the second option. In that case you have to specify a Login ID and Password. Click Next >.

image     

  • Click Next > and Finish to complete the wizard.

Usage

  • Now we can invoke the dtctester tool by providing the DSN name we just created and a SQL server username and password:

C:\Users\BaWu\Desktop>dtctester test username password

  • Here is the result we got back:

Executed: dtctester
DSN:  test
User Name: username
Password: password
tablename= #dtc26446
Creating Temp Table for Testing: #dtc26446
Warning: No Columns in Result Set From Executing: 'create table #dtc26446 (ival int)'
Initializing DTC
DtcGetTransactionManager failed: 8004d01b
DtcGetTransactionManager Call Error: Indicates unable to connect to the transaction manager, or the transaction manager is unavailable.

Labels:

Popular posts from this blog

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more