Yes, there is a fw between these two servers.
before we wrote to you, we made another test. We installed a new test
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
"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@discussions.microsoft.com> wrote in message
> news:1186D491-38A8-4971-B774-8EB05F74F465@microsoft.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@celebi-ic.com
> >
www.celebi-ic.com
