MSDTC & W2K3 & SQL 2000 issue

I have MSDTC installed in the Cluster group (no other disks available). It fails over fine, comes online on either node, no problem. My DBA alerted me, that she cannot start Distributed Transaction Coordinator on the node that is NOT in control of the MSD
TC resource using SQL Server Enterprise Manager. This is on W2K3. This cluster will be replacing a W2K/SQL2K cluster. I configured the W2K3 cluster, the same as the W2K cluster, yet she (the DBA) CAN start MSDTC on either/both nodes of the W2K cluster. W
hy won't DTC start on the other node in Ent Mgr? The DBA says that this is necessary for something to function correctly, so I have to fix it? Any ideas/help would be appreciated.
A clustered instance of SQL server uses a cluster-wide MSDTC instance
instead of a local MSDTC instance on each host node. As such, the cluster
admin tool becomes the correct tool for managing MSDTC, not SQL Enterprise
Mangler. So, the behavior your DBA noted is correct for a cluster, but
since MSDTC is running the application will function correctly.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"wbielinski at abms dot org" <wbielinski at abms dot
org@.discussions.microsoft.com> wrote in message
news:E0451843-96A1-4B57-98E0-39CD3A73304D@.microsoft.com...
> I have MSDTC installed in the Cluster group (no other disks available). It
fails over fine, comes online on either node, no problem. My DBA alerted me,
that she cannot start Distributed Transaction Coordinator on the node that
is NOT in control of the MSDTC resource using SQL Server Enterprise Manager.
This is on W2K3. This cluster will be replacing a W2K/SQL2K cluster. I
configured the W2K3 cluster, the same as the W2K cluster, yet she (the DBA)
CAN start MSDTC on either/both nodes of the W2K cluster. Why won't DTC
start on the other node in Ent Mgr? The DBA says that this is necessary for
something to function correctly, so I have to fix it? Any ideas/help would
be appreciated.
|||It is a good idea to place MSDTC in its own resource group and another thing
I will check is that the Network access for DTC is enabled. YOu can look for
this in control panel/add remove programs/add remove components/Application
Server.
"Geoff N. Hiten" wrote:

> A clustered instance of SQL server uses a cluster-wide MSDTC instance
> instead of a local MSDTC instance on each host node. As such, the cluster
> admin tool becomes the correct tool for managing MSDTC, not SQL Enterprise
> Mangler. So, the behavior your DBA noted is correct for a cluster, but
> since MSDTC is running the application will function correctly.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "wbielinski at abms dot org" <wbielinski at abms dot
> org@.discussions.microsoft.com> wrote in message
> news:E0451843-96A1-4B57-98E0-39CD3A73304D@.microsoft.com...
> fails over fine, comes online on either node, no problem. My DBA alerted me,
> that she cannot start Distributed Transaction Coordinator on the node that
> is NOT in control of the MSDTC resource using SQL Server Enterprise Manager.
> This is on W2K3. This cluster will be replacing a W2K/SQL2K cluster. I
> configured the W2K3 cluster, the same as the W2K cluster, yet she (the DBA)
> CAN start MSDTC on either/both nodes of the W2K cluster. Why won't DTC
> start on the other node in Ent Mgr? The DBA says that this is necessary for
> something to function correctly, so I have to fix it? Any ideas/help would
> be appreciated.
>
>