Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

[Microsoft][ODBC driver for Oracle]Failure in DTC: not able to validate open information

177 views
Skip to first unread message

ma

unread,
Jul 30, 2009, 2:49:18 AM7/30/09
to
Hi,
We have one application which is developed in 3 tier architecture in
VB 6.0 - MTS - Oracle 9i. In the production environment, all the COM
components deployed as a COM+ application on Windows 2000 server. And
the Oracle 9i is running on IBM AIX OS, this setup is working fine
without any issues. Now the client is looking to migrate the middle
layer from Window 2000 server to Windows 2003 server (SP2). So the
respective COM+ application is exported to msi from Windows 2000
server and installed on Windows 2003 server. We did the respective COM
+ security settings as per the documentation. Now while running the
application, the ODBC connection is failing and popping up the
following error message. When we try the same thing with SQLConnect,
it seems connecting fine. The error and the event log are like this –

The error message is –
Run-time error ‘-2147168246 (8004d00a);
[Microsoft][ODBC driver for Oracle]Failuer in DTC:not able to validate
open information

The Even log is showing as –

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:\WIDNOWS\system32\mtxoci.dll File=d:\nt\com\complus\dtc\dtc\xatm
\src\xarmconn.cpp Line=2476.

Here Source = MSDTC
Category = XATM
Event ID = 53284


We did make sure the following things -

COM+ configuration specific to COM+1.5.
We added NETWORK SERVICE access to MtxOci regkey in registry

Oracle released one patch for Oracle 9i database server to run on
Windows 20003 server. But there are no patches for Oracle 9i client.
Since we are changing the environment on the middle server which has
the Oracle 9i client and not modifying anything on database server, we
are assuming that we don’t need to update any patches. Is that
correct?

When we step through the code in debugger, we noticed that the ADODB
obejct is created and the string looks ok, but ADODB::Open is getting
failed. That is where the error is generating.

But the connection from SQL connect seems working fine.

We are looking for the information - whether any issues with Oracle 9i
client on 2003 server to work with MTS or anything we need to take
care to run the VB 60 application on Windows 2003 server.
We installed the Oracle client only, we did not see any other patches
or driver updates (SQORA32.dll). And also we did not run any extra
patches / softwares to work MSDTC with Oracle 9i. Anything we are
missing in this space.

Any help would be really appreciable.

0 new messages