Welcome to dbForumz.com!
FAQFAQ    SearchSearch      ProfileProfile    Private MessagesPrivate Messages   Log inLog in

Commit of internal MSDTC transaction failed: Result Code =..

  
   Database Forums (Home) -> Clustering RSS
Next:  Bug in JDBC Driver with use of Bulk Insert and Mo..  
Author Message
Dreamer

External


Since: Apr 25, 2007
Posts: 1



(Msg. 1) Posted: Wed Apr 25, 2007 9:22 am
Post subject: Commit of internal MSDTC transaction failed: Result Code = 0x8004d
Archived from groups: microsoft>public>sqlserver>clustering (more info?)
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.DeleteThis@celebi-ic.com
www.celebi-ic.com

 >> Stay informed about: Commit of internal MSDTC transaction failed: Result Code =.. 
Back to top
Login to vote
John Vandervliet

External


Since: Apr 25, 2007
Posts: 3



(Msg. 2) Posted: Wed Apr 25, 2007 12:53 pm
Post subject: Re: Commit of internal MSDTC transaction failed: Result Code = 0x8004d [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
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" wrote in message

> 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.TakeThisOut@celebi-ic.com
> www.celebi-ic.com

 >> Stay informed about: Commit of internal MSDTC transaction failed: Result Code =.. 
Back to top
Login to vote
omarusta

External


Since: Apr 27, 2007
Posts: 1



(Msg. 3) Posted: Fri Apr 27, 2007 12:22 am
Post subject: Re: Commit of internal MSDTC transaction failed: Result Code = 0x8 [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
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" wrote in message
>
> > 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.TakeThisOut@celebi-ic.com
> > www.celebi-ic.com
>
 >> Stay informed about: Commit of internal MSDTC transaction failed: Result Code =.. 
Back to top
Login to vote
Exe_Vaz

External


Since: Dec 27, 2007
Posts: 1



(Msg. 4) Posted: Thu Dec 27, 2007 11:57 am
Post subject: Re: Commit of internal MSDTC transaction failed: Result Code = 0x8004d [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
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:
> 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" wrote in message
> >
> >


--
Exe_Vaz
 >> Stay informed about: Commit of internal MSDTC transaction failed: Result Code =.. 
Back to top
Login to vote
Display posts from previous:   
Related Topics:
Clusterinstallation failed with "error while commit - wron.. -

MSDTC - I have 2 nodes Windows Server 2003 R2 Enterprise x64 Edition with Service Pack 2. I need to install SQL2005 Standard Edition with multiples instances. Each instance has its own one Cluster Group. I am installing MSDTC in cluster and I need to assign a...

MSDTC is does not respond - Hi All- We have a MSDTC issue in our cluster. If I make any cross database calls in the cluster instance, I get an error related with MSDTC [Error text is similar to "MSDTC is not running in the given instance"] I notice that the MSDTC Lo...

MSDTC with SQL Server 2000 - Hi, I have a three nodes cluster with Win 2003. On that I have four SQL intances. MSTDC is installed on the Quorum. When a failover happens, the SQL groups start before MSDTC and that create a problem with the transactions after. To assure a good..

MSDTC Troubles, Do I Even Need It? - I am running a two node cluster. The failover node had a hardware failure and I had to re-install Windows. I have been trying to add the node back into the cluster for 3 days and it continually fails with MSDTC. Mostly it's been complaining that a..
   Database Forums (Home) -> Clustering All times are: Pacific Time (US & Canada)
Page 1 of 1

 
 You can post new topics in this forum
You can reply to topics in this forum
You can edit your posts in this forum
You can delete your posts in this forum
You can vote in polls in this forum



[ Contact us | Terms of Service/Privacy Policy ]