Problems with XA Transaction Manager

I have got an entry in the Application Event Log as follows:
"The XA Transaction Manager attempted to load the XA resource manager DLL.
The call to LOADLIBRARY for the XA resource manager
DLL failed: DLL=.\xarmconn.cpp File$06 Line=%3."

This only happens for updates. The SQL select are working fine.

IBM thinks that it is due to some configuration or settings on Windows
Server or COM+.
Here is some information about the environment:
O.S.: Windows 2000 SP4
I've tried different MDAC versions 2.6, 2.7 SP1 Refresh and 2.81. I
confirmed with ComChecker that the new version was updated well.
IIS: diferent versions from 5.0 until 6 SP1.
IBM Informix Connect 2.81 but I've also tried 2.9.

I've found hits on a known problem for Win2003 and XP SP2, but nothing
where
this problem is reported for Win2000.

Everything it's quite extrange because I had an already installed machine
with that configuration and I have no problems at all. But now I have
tried
to install the application into developmental enviroments and I got always
the same Transaction Error.

Anyone encounter this and know of a solution?

Thanks in advance

Hi,



there are some issues with XA and w2k3. First of all you must give the
network service account the appropriate access to the IBM folder (I only
know oracle and XA en normally that would be something like d:\oracle)
Accounts need RX rights. Als you will need to specify the IBM XA dll's in
your registry, and give the network service account (if not already there)
the appropriate rights. Als XA transactions are default disabled in w2k3,
so you must change this through the properties of MSDTC. I believe these
steps should do the trick, please write if you need more info.



Sander



"Fco Javier" schreef in bericht
news:
Mostrar la cita

I have got an entry in the Application Event Log as follows:
"The XA Transaction Manager attempted to load the XA resource manager
DLL.
The call to LOADLIBRARY for the XA resource manager
DLL failed: DLL=.\xarmconn.cpp File$06 Line=%3."

This only happens for updates. The SQL select are working fine.

IBM thinks that it is due to some configuration or settings on Windows
Server or COM+.
Here is some information about the environment:
O.S.: Windows 2000 SP4
I've tried different MDAC versions 2.6, 2.7 SP1 Refresh and 2.81. I
confirmed with ComChecker that the new version was updated well.
IIS: diferent versions from 5.0 until 6 SP1.
IBM Informix Connect 2.81 but I've also tried 2.9.

I've found hits on a known problem for Win2003 and XP SP2, but nothing
where
this problem is reported for Win2000.

Everything it's quite extrange because I had an already installed machine
with that configuration and I have no problems at all. But now I have
tried
to install the application into developmental enviroments and I got
always
the same Transaction Error.

Anyone encounter this and know of a solution?

Thanks in advance