Hello all.

We've just built a Windows 2003 EE active/active cluster. SQL Server 2000 is
installed on each node. MSDTC was installed after-the-fact and is not
working properly, i.e. working for some applications, not for others.

MSDTC was originally set up in one of the SQL Server Groups, deleted, and
then installed in the Cluster Group using the Quorum Drive/Cluster
Name/Cluster IP Address (Some KB articles suggest that this is okay, others
recommend that it be installed elsewhere.) I suspect that the because MSDTC
was initially installed in a different group, it is not properly installed
and/or configured. Is using the Cluster Group still an acceptable practice?
If not what Drive/Name/IP resource do you create for it?

I am aware of 'KB294209 HOWTO: Rebuild or Move MSDTC Used with a SQL
Failover Cluster', however, because the process it recommends is so complex,
I would like to know if this is actually what I must do to correct my
problem before I attempt it.

Does anyone have any ideas?

Thanks all.

MSDTC should be in it's own group with it's own disk resource. Why shouldn't it share the Quorum disk resource? If MSDTC corrupts the disk (for whatever reason) your cluster is dead until you manually fix it... What error is being logged when your applications cannot enlist a distributed transaction?