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

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Sunny - 03 Dec 2005 07:14 GMT

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.

Reply to this Message

Anthony Thomas - 06 Dec 2005 04:03 GMT

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

> 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
[quoted text clipped - 9 lines]
>
> Ohh yes and there's no errors in the event log.

Reply to this Message

Sunny - 06 Dec 2005 21:58 GMT

Ok first question Answer......
Cluster Group has the Cluster IP address=10.0.0.59, Cluster name, and Disk
Q:(Quorum)
MSDTC Group has the MSDTC Network name, MSDTC IP Address=10.0.0.60,
Distributed Transaction Coordinator and Disk T:(Transaction log)
SQL Group has the SQL Server Fulltext, SQL Server Agent, SQL Server, SQL
Network Name(SQL), SQL IP Address1(SQL)=10.0.0.61 Disk S:

Second Question:
Ok here's the thing, it doesnt fail over or go offline, it actually stays
online but except for Remote Desktop connecting to the SQL virtual server by
name(Which i'm guessing is running off of cache) i'm not able to ping the sql
server unless and until the msdtc is failed over to the other server which is
the current config.

What do you suggest i try? or do?

And thanks for any assistance you can offer.

> What are the Resource Group names, Resource Network Names, and Resource IP
> addresses? What other resources a apart of each group?
[quoted text clipped - 27 lines]
> >
> > Ohh yes and there's no errors in the event log.

Reply to this Message

Anthony Thomas - 07 Dec 2005 14:11 GMT

Sorry for all the questions, but it doesn't sound right; so, I need more
information.

What are the IP addresses of the hosts (cluster nodes) both public and
private network interfaces?

I see that the IP in the SQL Server cluster resource group is named SQL IP
Address1, did you recently change this IP address? If so, what mechanism
did you use, how did you implement the change?

Finally, in the SQL Server error log, there are five things to look for; I
need this information:

1. The copyright line will tell you what version, edition, and build
level you are using.

2. If there is a problem with connecting with the DTC, you will see an
"Attempt to elicit distributed transaction coordinator," followed by a
"error creating resource" or "resource manager" error.

3. The error log will report the Network Protocols, SQL Server Name, and
IP Addresses/Ports it has hooked into. For a cluster, you should see Named
Pipes, TCP/IP, and Shared Memory protocols and then the Virtual
Server\Instance Name and Cluster Virtual IP address. These should match
what you've defined above.

4. There should be a "ready for client connections" entry.

5. Finally, there should be a "recovery complete" entry right before
launching the Startup Procedures "xpstar.dll."

Hope this helps.

Sincerely,

Anthony Thomas

> Ok first question Answer......
> Cluster Group has the Cluster IP address=10.0.0.59, Cluster name, and Disk
[quoted text clipped - 46 lines]
> > >
> > > Ohh yes and there's no errors in the event log.

Reply to this Message

sunny - 21 Dec 2005 07:19 GMT

Anthony i think you might have been right about the DNS registration, maybe
for some reason it didnt go through but i just tried failing over the MSDTC
group to the active node and everything is on the Active node right now and
it's working. So it might have been just one of those things......

Sorry for the late reply but i really appreciate all your help i looked into
a few of the things but like u said "it just doesnt sound right"

Overall thanks for the help "YOU ARE THE MAN"

-SUNNY

> Sorry for all the questions, but it doesn't sound right; so, I need more
> information.
[quoted text clipped - 96 lines]
> > > >
> > > > Ohh yes and there's no errors in the event log.

Reply to this Message

Anthony Thomas - 24 Dec 2005 15:29 GMT

Not a problem. I'm glad you were able to resolve this.

Thanks for the update, and the praise.

Sincerely,

Anthony Thomas

> Anthony i think you might have been right about the DNS registration, maybe
> for some reason it didnt go through but i just tried failing over the MSDTC
[quoted text clipped - 108 lines]
> > > > >
> > > > > Ohh yes and there's no errors in the event log.

Reply to this Message