WIN2K3 SP1, SQL Server / MSDTC Issue

Hi,
I have been setting up a WIN2K3 Cluster here today and having some
problems. I can get SQL Installed ok and everything works fine until I set
my Application Servers to point at the new SQL Server, at which point my
Component Services Components start getting MSDTC errors - 'New transaction
cannot enlist in the specified transaction coordinator' to be precise.

Here is what I did in order:
Installed Windows 2003 (with SP1 already preapplied)
Setup Network Connections (for internal cluster comms and public network)
Set Server to be an Application Server Role (ensuring Enable Network DTC
Access was checked)
Reboot Servers
Setup Cluster
Add second node to cluster
Reboot Servers
Install SQL
Apply SP3a to SQL
Reboot Servers
Finally I added in the MSDTC Resource (and I have tried this in the Cluster
Group and the SQL Group, and finally in its own group)
Tried to call my components and I get the above errors.

I have since gone through god knows how many web sites looking for answers
and tried all the suggested things such as ensuring MSDTC is started before
SQL Starts etc to no avail.

What I did notice is that when I actually add the MSDTC resource to the
cluster then go back into Add Remove Programs it has unchecked Enable network
DTC access (Yes it was definately checked - I checked at least 5 times and
even ended up re-installing both servers and setting it all up again to make
sure I wasn't going crazy!)

I re-checked the box on both servers and rebooted them both and still
nothing. I also checked the Registry to ensure the MSDTC Keys relating to
network transactions were both set to 1.

I have tried DTC Tester also and I get an error just after it tries to
Enlist the connection in the transaction, which is a Distributed Transaction
Error. The extra detail says Invalid Cursor State.

When I run the DTC Tester on either node of the cluster it works fine so it
HAS to be related to network DTC, but all the settings seem correct!

Please HELP! :(

Dan

.

Relevant Pages

  • Re: Adding 3 nodes to a cluster
    ... So you need to add the nodes to the cluster using the Cluster tool. ... Then extend the existing instance to the new nodes using the installer. ... Senior SQL Infrastructure Consultant ... servers acting as a failover in case one of the servers fails. ...
    (microsoft.public.sqlserver.clustering)
  • Re: SQL 2008 clustering with Windows 2008
    ... Since the heartbeat NIC is not onany public network, it should have IP addresses hard-set. ... While Windows 2008 and SQL 2008 support DHCP addresses in a cluster, that is a prety advanced setup. ... You can team the public NICs, but you need to put them on different switches ...
    (microsoft.public.sqlserver.clustering)
  • Re: Adding 3 nodes to a cluster
    ... First you use the cluster admin tool to add the machines as nodes to the cluster. ... Then you run the SQL installer to install binaries on the newly added nodes and allow the new nodes to host the existing instances. ... >>>I need to add these new servers as seperate instances in the SQL ...
    (microsoft.public.sqlserver.clustering)
  • Re: Accessing Cluster Disks from a WEB Application
    ... Cluster Name ... Cluster Quorum Disk ... SQL Network Name ...
    (microsoft.public.windows.server.clustering)
  • RE: New SQL 2005 Cluster Questions
    ... You have only one SQL instance in the cluster. ... So, from what I am seeing is I have no choice but to DC the servers, cluster ... Win2003 Ent and then install SQL 2005 Ent onto this cluster. ...
    (microsoft.public.sqlserver.clustering)