Skip to main content

Problems using the .NET transactionscope with DB2 on a 64 bit machine

To solve the growing need for more memory, we decided to upgrade all our development machines to a 64bit OS.  Although this allows us to install and use more memory on our machines, it also introduces a whole list of new problems.

One of them was regarding the usage of the .NET transactionscope in combination with DB2. In DB2 managing your transactions through the transactionscope will immediatelly involve the DTC coordinator. However the moment the DTC tries to open a transaction, it fails with the following error message:

The XA Transaction Manager attempted to load the XA resource manager DLL. The call to LOADLIBRARY for the XA resource manager DLL failed: DLL=C:\Program Files\IBM\SQLLIB\BIN\DB2APP.DLL, HR=0x800700c1, File=d:\w7rtm\com\complus\dtc\dtc\xatm\src\xarmconn.cpp Line=2446.

After trying almost every possible solution, we finally found a solution that worked for us. When installing the DB2 client, it doesn’t correctly register the 64bit dll’s in the register.

The following registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\XADLL incorrectly referenced the db2app.dll instead of the db2app64.dll. As a consequence the MSDTC tries to load a 32bit DLL on 64bit machine, which fails. After changing the reference to the 64bit dll everything worked.

More information in this thread on the DB2 forums.

Labels:

Popular posts from this blog

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

Cleaner switch expressions with pattern matching in C#

Ever find yourself mapping multiple string values to the same result? Being a C# developer for a long time, I sometimes forget that the C# has evolved so I still dare to chain case labels or reach for a dictionary. Of course with pattern matching this is no longer necessary. With pattern matching, you can express things inline, declaratively, and with zero repetition. A small example I was working on a small script that should invoke different actions depending on the environment. As our developers were using different variations for the same environment e.g.  "tst" alongside "test" , "prd" alongside "prod" .  We asked to streamline this a long time ago, but as these things happen, we still see variations in the wild. This brought me to the following code that is a perfect example for pattern matching: The or keyword here is a logical pattern combinator , not a boolean operator. It matches if either of the specified pattern...
Read more