SQL Server, Import of MSDTC transaction failed

microsoft.public.sqlserver.server - Microsoft SQL Server forum discussing administration and other SQL Server related topics. MS SQL Server is used for high performance and enterprise level applications.


SQL Server >> Import of MSDTC transaction failed

by lv mingtong » Tue, 07 Sep 2004 10:17:45 GMT

Error: 8509, State: 1, Message: Import of MSDTC transaction failed: Result
Code = 0x8004d00e

I can not find any help on many websites.
How to do it?



Top

SQL Server >> Import of MSDTC transaction failed

by Gert E.R. Drapers » Tue, 07 Sep 2004 19:54:44 GMT


The error message says that SQL Server can not enlist in the transaction
that is provide because the transaction is already implicitly or explicitly
committed or aborted.

Which OS are you on? If you are using Windows XP or Windows Server 2003 you
can use DTC trace to find out why the transaction import failed. If you do
not have this OS, you could use AppMetrics from ExtermeSoft see
http://www.xtremesoft.com

XXXX@XXXXX.COM

Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright SQLDev.Net 1991-2004 All rights reserved.


>> Error: 8509, State: 1, Message: Import of MSDTC transaction failed: Result >> Code = 0x8004d00e >> >> I can not find any help on many websites. >> How to do it? >> >>




Top

SQL Server >> Import of MSDTC transaction failed

by ken_waugh » Fri, 17 Sep 2004 01:29:52 GMT

I too am having this issue. The db is running on Win XP Professional,
SQL Server 2K + ASP.NET app. It is an intermittent issue and occurs
every 4th hit to any page. I am using
System.EnterpriseServices.AutoCompleteAttribute(True) to auto commit
the transaction. The strange thing is that if I hit the maching
remotely it is fine...If I do it locally the error will appear.

Eg.
Scenario #1: Works and is fine:
Machine A = Web App, dll's etc
Machine B = DB server

Scenario #2: Generates the error "Import of MSDTC transaction failed:
Result Code = 0x8004d00e."
Machine A = Web App, dll's etc + DB server

It is a strange issue that is not constant.

Any suggestions will be attempted...no matter how bizzare :)

Thanks

Top

Import of MSDTC transaction failed

by ken_waugh » Fri, 17 Sep 2004 05:05:10 GMT

I too am having this issue. The db is running on Win XP Professional,
SQL Server 2K + ASP.NET app. It is an intermittent issue and occurs
every 4th hit to any page. I am using
System.EnterpriseServices.AutoCompleteAttribute(True) to auto commit
the transaction. The strange thing is that if I hit the maching
remotely it is fine...If I do it locally the error will appear.

Eg.
Scenario #1: Works and is fine:
Machine A = Web App, dll's etc
Machine B = DB server

Scenario #2: Generates the error "Import of MSDTC transaction failed:
Result Code = 0x8004d00e."
Machine A = Web App, dll's etc + DB server

It is a strange issue that is not constant.

Any suggestions will be attempted...no matter how bizzare :)

Thanks

Top
Similar Threads

1. Enlist of MSDTC transaction failed: Result Code = 0x8004d00e. Enlist of MSDTC transaction failed: Result Code = 0x8004d00e. 

Dear All,



I am having the following issue since we restarted our two node cluster 
after we had UMS scheduler error. Can any one help me in identifying the 
exact problem.



Problem Description:



SQL Server agent job fails with the following error message

1.  Error: 50000, Severity: 16, State: 1

     ANZDBA - Job Failed  Job Name: ANZDBA - Transaction Log Backups, Step 
Name: ANZDBA -    TellingLogMarker



2. Error: 8510, Severity: 20, State: 2

 Enlist of MSDTC transaction failed: Result Code = 0x8004d00e.



What the job does?

            The job inserts a data into 3 databases across 2 nodes within a 
transaction.



When we started noticing the error?

We started noticing this error from Yesterday after we rebooted the box to 
fix the UMS scheduler error.



Additional Information



The calling procedure uses marked transactions.



SQL Server Configuration



  1.. SQL Server 2000 with SP3 and HF850
  2.. Active / Active SQL Cluster
3.    Windows 2000 Advanced Server with SP4 (5.00.2195)



Regards

Balaji.T

2. Commit of internal MSDTC transaction failed: Result Code = 0x8004d

3. Commit of internal MSDTC transaction failed: Result Code = 0x8 

Yes, there is a fw between these two servers.
before we wrote to you, we made another test. We installed a new test 
server(w2003 enterprise + mssql2000) and put this new server into same VLAN 
with our clusters without a fw between them. We can successfully began a 
transaction from clusters to new server and from new server to clusters. But 
after we changed the VLAN of this new server and put a fw between this new 
server and clusters we were unable to begin a transaction between them with 
the same linked server

"John Vandervliet" wrote:

> Hello Dreamer,
> 
> You issue is one of startup precedence. Basically SQL is starting before the 
> MSDTC is. To get this working simply stop the SQL server and the MSDTC. Then 
> startup the MSDTC and then SQL server.
> 
> If you are behind  a firewall let me know as this needs some configuration 
> other than 1433.
> 
> John ...
> 
> 
> 
> 
> "Dreamer" < XXXX@XXXXX.COM > wrote in message 
> news: XXXX@XXXXX.COM ...
> > Hi,
> > We have 2 node sql failover cluster configuration ( Server 2003 +SP2,
> > MSSQL2000 )
> >
> > We can succesfully query the data from other MSSQL  Server over a linked
> > Server.
> > But, When we want to start a transaction to same server we are getting 
> > this
> > message :
> > ---------------------------------------------------------------------------------------------
> > Server: Msg 8520, Level 20, State 1, Line 3
> >
> > Commit of internal MSDTC transaction failed: Result Code = 0x8004d019.
> >
> > Connection Broken
> > ---------------------------------------------------------------------------------------------
> >
> > P.S :
> > - And also, we can succesfuly begin a transaction to an Oracle Server over
> > an another linked Server.
> >
> > - We have tested the connection between these to Servers with Microsoft's
> > DTC ping tool and the result was succesfully
> >
> >
> > Volkan Vural
> > Celebi-IC Antalya Airport Second International Terminal
> > Information Technologies Department
> > T. +90 242 310 55 00  Ext: 7046
> > F. +90 242 310 56 03
> >  XXXX@XXXXX.COM 
> > www.celebi-ic.com 
>

4. MSDTC orphaned transactions and MSDTC tracing

5. Enlist of MSDTC transaction failed: Result Code = 0x8004d01c. 

I have the next error when I run the distibuted transaction

Server: Msg 8510, Level 20, State 2, Procedure Valida_RegPatronal_pUP, Line 28
Enlist of MSDTC transaction failed: Result Code = 0x8004d01c.

Connection Broken

6. SSIS Transactions failing due to MSDTC - SQL Server

7. MSDTC and Delete transactions 

Hello
I had a question reagrding MSDTC usage. I know that MSDTC will enlist
each connection transactions as it's own (take ownership) and
commit/abort accordingly.

However I'm not sure what would happen where I have a stored proc with
input parameters and 2 Delete commands on  2 different tables. In this
case, would MSDTC also enforce ACID rules when 1 cmd succeeds and 2nd
aborts ? In the script for the Stored Proc, there is no checking for
@@ERROR value. There are just DELETE statement and a plain RETURN.

thanks
Sunit

8. SQL 2000 32-bit on Window 2003 x64 Cluster server & MSDTC distributed transaction