COM+ and ADO 2.8?

Dave

2006-01-09 22:39:03 UTC

http://publib.boulder.ibm.com/infocenter/db2v7luw/index.jsp?topic=/com.ibm.db2v7.doc/db2l0/duow.htm

If the MTS COM objects use ADO to access the database, you must turn off the
OLEDB resource pooling so that the Microsoft OLEDB provider for ODBC
(MSDASQL) will not interfere with ODBC connection pooling. This feature was
initialized to OFF in ADO 2.0, but is initialized to ON in ADO 2.1. To turn
OLEDB resource polling off, copy the following lines into a file called
oledb.reg, save it as a plain text file, and issue the command oledb.reg. The
Windows operating system will import this registry setting.

REGEDIT4

[HKEY_CLASSES_ROOT\CLSID\{c8b522cb-5cf3-11ce-ade5-00aa0044773d}]
@="MSDASQL"
"OLEDB_SERVICES"=dword:fffffffc

Reusing ODBC Connections Between COM Objects Participating in the Same
Transaction
ODBC connections in MTS COM objects have connection pooling turned on
automatically (whether or not the COM object is transactional).

For multiple MTS COM objects participating in the same transaction, the
connection can be reused between two or more COM objects in the following
manner.

Post by Dave
I had a test machine with ADO 2.7.
We use ADO/ODBC/DB2 Connect v8 up to a mainframe. Never had a problem.
We have build machines upgrading to XP and ADO 2.8 so I wanted to test
upgrading to ADO 2.8.1 on my test machine.
Now when I run the Application and get to a point that runs a query in a COM+
transactional component (even SELECT statement), I get the following error.
IBM][CLI Driver][DB2] SQL0998N Error occurred during transaction or
heuristic processing. Reason Code = "16". Subcode = "3-8004D00E".
SQLSTATE=58005
I am wondering if ADO 2.8 changed some security somewhere that is causing
this?
--
Thanks,
Dave