dbTalk Databases Forums  

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

microsoft.public.sqlserver.clustering microsoft.public.sqlserver.clustering


Discuss Commit of internal MSDTC transaction failed: Result Code = 0x8004d in the microsoft.public.sqlserver.clustering forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Dreamer
 
Posts: n/a

Default Commit of internal MSDTC transaction failed: Result Code = 0x8004d - 04-25-2007 , 11:22 AM






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
volkan.vural (AT) celebi-ic (DOT) com
www.celebi-ic.com

Reply With Quote
  #2  
Old   
John Vandervliet
 
Posts: n/a

Default Re: Commit of internal MSDTC transaction failed: Result Code = 0x8004d - 04-25-2007 , 01:53 PM






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" <Dreamer (AT) discussions (DOT) microsoft.com> wrote

Quote:
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
volkan.vural (AT) celebi-ic (DOT) com
www.celebi-ic.com


Reply With Quote
  #3  
Old   
omarusta
 
Posts: n/a

Default Re: Commit of internal MSDTC transaction failed: Result Code = 0x8 - 04-27-2007 , 02:22 AM



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:

Quote:
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" <Dreamer (AT) discussions (DOT) microsoft.com> wrote in message
news:1186D491-38A8-4971-B774-8EB05F74F465 (AT) microsoft (DOT) 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
volkan.vural (AT) celebi-ic (DOT) com
www.celebi-ic.com


Reply With Quote
  #4  
Old   
Exe_Vaz
 
Posts: n/a

Default Re: Commit of internal MSDTC transaction failed: Result Code = 0x8004d - 12-27-2007 , 11:57 AM




Hi ,I had the same problem, the solution was

go to panel control\Add o remove programs\add o remove windows
components\ application server

Check that the selected Enable Network Com +access
Check that the selected Enable network DTC access


After this configuration works ok !



saludos
Exequiel




omarusta;7559553 Wrote:
Quote:
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" <Dreamer (AT) discussions (DOT) microsoft.com> wrote in message
news:1186D491-38A8-4971-B774-8EB05F74F465 (AT) microsoft (DOT) com...


--
Exe_Vaz


Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.