MSDTC and SQL 2000

Question

Host: Windows 2003 w/sp1 and SQL 2000 w/ sp3a

I am able to issue a Select statement (not inside of a transaction) to a table on a database on server and the record-set is returned. I can also issue an insert statement (not inside a transaction) to a table in a database on server ¿ and the record inserts.

However, once I enclose that statement in the BEGIN DISTRIBUTED TRANSACTION ¿¿. COMMIT TRAN, I get this error:

Server: Msg 7391, Level 16, State 1, Line 3
The operation could not be performed because the OLE DB provider 'SQLOLEDB' was unable to begin a distributed transaction.
[OLE/DB provider returned message: New transaction cannot enlist in the specified transaction coordinator. ]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB' ITransactionJoin::JoinTransaction returned 0x8004d00a].

Is anyone else running into this problem?

dpinink_silva · Answer

Well, I did have a lot of problems working with MSDTC and EMC AutoStart, and I still don't know what should be a good approach to solve this kind of problem. I opened a case sometime ago related to problems with MSDTC, you can try to take a look at that and see if there's anything that could help you:

http://softwaresupport.emc.com/support/cases/dmCaseView.asp?id=513920

I think the case is available to other users to see, if don't, please let me know...

ble1 · Answer

http://softwaresupport.emc.com/support/cases/dmCaseView.asp?id=513920

I think the case is available to other users to see,
if don't, please let me know...

Nope. Only owners (individual or individuals within same company) can see their own cases.

dpinink_silva · Answer

I know it does not make any sense, but I was able to solve my problem regarding MSDTC excluding sacn and resacn scripts from the startup and shutdown sequences.

EMC was not able to tell me why it worked, but said that we had to use it this way at our own risk, and make all the tests on our own. AFAIK, everything is working fine without those scripts.

You can try that, maybe it works, maybe not...

aperez2 · Answer

If I run the SQL query using server name it works.
If I run the SQL query using server name and MSDTC it works.
If I run the SQL query and Legato "node alias" it works.

If I run the SQL query and Legato "node alias" and MSDTC is does NOT work.

Here is my startup sequence:

BeginResources
IP address (vip)
Node Alias
CloseResources
StartupSacn
MSDTC
SQL2000
SQL2000Agent

Here is my shutdown sequence:

SQL2000Agent
SQL2000
MSDTC
StartupResacn
BeginResources
Node Alias
IP Address (vip)
CloseResources

dpinink_silva · Answer

I did hope that it would be available as a "Support Note" when you did search in the KB...

Anyway, does this error happen only on one node? If you failover to another one, you get the same error?

Did you tried to run SQL and MSDTC without AutoStart to see if it works? What do you have in your startup and shutdown sequences?

aperez2 · Answer

I removed the RestartSacn and RestartResacn scripts and it still does not work. I am testing using this simple SQL select query.

BEGIN distributed TRANSACTION
select * from [servername].pubs.dbo.authors
COMMIT TRAN

Note: [servername] = Legato node alias

twood3 · Answer

Alex,If you would like to dicuss this problem, we have a config that worked for us with DTC. I can be reached at twood@stsgi.com

Replication Manager

MSDTC and SQL 2000

Was this post helpful?