msdtc is causing my cluster to be unavailiable via it's virtual na

I have windows 2003 sp1 running in a 2-node cluster. The cluster is running
sql sp4. I tried failing over my cluster after a windows update and i'm not
sure if that's what threw my server's off or something else. But here's the
situation. I currently have the cluster group running on node 2, the msdtc
running on node 1 and the sql group running on node 2. When i move the msdtc
group to node 2 (ie.. the server which should be running all services)i cant
ping the sql virtual server by name or ip. I am however able to contact the
individual servers via their names sql1 and sql2. So basically i lose my
connection to the virtual sql server throughout my network when the msdtc is
running on the same server. Is there an update? upgrade? to the msdtc or
anything else i can do to fix this issue?
Ohh yes and there's no errors in the event log.
What are the Resource Group names, Resource Network Names, and Resource IP
addresses? What other resources a apart of each group?
Sounds like a DNS registration issue. Does the SQL Server group go offline
or fail over when the MSDTC group is moved to node 2?
Sincerely,
Anthony Thomas

"Sunny" <Sunny@.discussions.microsoft.com> wrote in message
news:12879549-04B5-454B-A44C-C075061EAEC1@.microsoft.com...
> I have windows 2003 sp1 running in a 2-node cluster. The cluster is
running
> sql sp4. I tried failing over my cluster after a windows update and i'm
not
> sure if that's what threw my server's off or something else. But here's
the
> situation. I currently have the cluster group running on node 2, the
msdtc
> running on node 1 and the sql group running on node 2. When i move the
msdtc
> group to node 2 (ie.. the server which should be running all services)i
cant
> ping the sql virtual server by name or ip. I am however able to contact
the
> individual servers via their names sql1 and sql2. So basically i lose my
> connection to the virtual sql server throughout my network when the msdtc
is
> running on the same server. Is there an update? upgrade? to the msdtc or
> anything else i can do to fix this issue?
> Ohh yes and there's no errors in the event log.

MSDTC - running but not available - RPC error?

Hi there.
I am having problems with MSDTC on a 2-node clustered server. I currently
have it added as a resource in a group with disk storage, SQL Server, an IP
Address and a Network name. When I look at the status of MSDTC using MSSQL
Enterprise Manager on either node, it seems to be running Ok (after I select
"bring online" in cluster admin).
I have a non-clustered SQL Server from which I'd like to call stored
procedures on my clustered server (hence I need MSDTC running). However, on
running these queries, I am seeing problems like this:
select * from CLUSTER.MyDB.dbo.MyTable --this works fine BUT
BEGIN DISTRIBUTED TRANSACTION
select * from CLUSTER.MyDB.dbo.MyTable
COMMIT TRANSACTION
returns errors like
'MSDTC on server unavailable' and my stored procedure calls return errors
like:
'OLE DB error trace - ITransactionJoin::JoinTransaction returned 0x8004d00a'
I have performed some configuration according to
http://support.microsoft.com/kb/817064
and
http://support.microsoft.com/kb/301600
but to no avail.
Any ideas? We tried using DTCPing to obtain more detailed errors and what we
saw were 'RPC' errors (the cluster was unable to ping the other linked server)
Any help would be appreciated!
P.S: A constraint I have is that I can't assign a new IPAddress for MSDTC...
|||Hello,
Is your MSDTC the one from Windows 2003?
/Patrice
|||Yes - it's 2003 - sorry for leaving this out (I've ust gone a bit dizzy from
trying to fix this!)
"Patrice" wrote:

> Hello,
> Is your MSDTC the one from Windows 2003?
> /Patrice
>
|||Hello,
Is it possible for you to do the following test...
Cound you call your SP after
(a) you bring SQL online only after MSDTC was fully up and running
(b) you (try to) bring SQL online before MSDTC was fully up and
running
It would be interesting to notice that everything is fine with (a), and
that you got an "MSDTC on server unavailable" error message with (b).
If it is the case it will mean that you are experiencing the same
problem than the one I experienced a couple of months ago ;-)
/Patrice
|||Hello "Len",
Are you able to do the test I have proposed? Should I continue to
monitor this topic?
Thanks in advance for your reply.
/Patrice
|||If Patrice's test works you should contact Microsoft Product Support and
request the hotfix associated with this KB article:
883955 Availability of Windows Server 2003 COM 1.5 Rollup Package 3
http://support.microsoft.com/?id=883955
Dave Whitney
SQL Support