Motherboard, Mainboard and Microprocessor Information

SQL Server

Microsoft OLE DB Provider for SQL Server error '8004d00a' Distributed transaction error

This can happen if you use the following line in your ASP code, and then connect to SQL Server:

<%@TRANSACTION=Required%>

My first recommendation is to handle transactions at the database level.

If you absolutely must use Transaction Server (MTS) to handle ADO transactions from within ASP, you need to make sure the distributed transaction coordinator (DTC) is configured correctly. The web server and the SQL Server must be able to see each other over the network, by name. For more information on configuring MTS for use with DTC and SQL Server, see KB #191168. There is also a new KB article written by an ASP.NET MVP: KB #555017.

And finally, be sure to use an OLE-DB connection string, as opposed to ODBC (see Article #2126).

---

Oracle

Microsoft OLE DB Provider for ODBC Drivers error '8004d00a' [Microsoft][ODBC driver for Oracle]Failure enlisting in Resource Manager or Provider error '8000ffff' Catastrophic failure

This might mean that the resource DB list has become corrupted. You can try reinstalling the driver you're using, reinstalling ODBC, or getting an OLE-DB driver (see Article #2126). Make sure that if you are using a linked server from SQL Server to Oracle, and connecting from ASP through the linked server, that you have the linked server set up correctly (see KB #280106).

Microsoft OLE DB Provider for ODBC Drivers error '8004d00a' [Oracle][ODBC]Driver not capable.

Make sure that your Oracle client is 8.0.5.2.2 or higher, and see the white paper on configuring MTS with Oracle, from KB #193893.

[ Comment, Edit or Article Submission ]