Re: client can't connect when instance on one particular node
- From: unc27932@xxxxxxxxx
- Date: 2 Feb 2007 05:50:36 -0800
That's the problem - we've already done that. We've already rerun
setup, added SQL back to the rebuilt node, and reapplied SP4.
On Feb 2, 7:51 am, "Rodney R. Fournier [MVP]" <r...@xxxxxxxxxxxxxxxx
america.com> wrote:
Use your product CD to reinstall the bits on the evicted node. Use the
instance name for SQL1. Then reapply SP4 to that instance. Both of these
steps will on affect Node1.
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clusteringhttp://www.nw-america.com- Clustering Websitehttp://www.msmvps.com/clustering- Bloghttp://www.clusterhelp.com- Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
<unc27...@xxxxxxxxx> wrote in message
news:1170373222.776799.316260@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
OK - so here's the setup - two node cluster (we'll say Node1 & Node2),
two instances (so multi instance, we'll say SQL1 & SQL2). W2K3 server
on the nodes, SQL 2000 SP4 for SQL version. Our situation is this.
We removed Node1 from the virtual server using the setup utility in
SQL 2000 in order to do some maintenance. Then server guys evicted
Node1 from the cluster, and we had SQL1 & SQL2 running on Node2 during
maintenance period. Server guys rebuilt Node1 (to boot to the SAN
instead of local drives) and then readded the server back into the
cluster configuration. At that point I readded the node back to the
SQL virtual server, and added SP4 as well - all appeared well. I put
SQL1 onto Node1 and SQL2 onto Node2.
But then we get a call from a (only one) customer saying that she
cannot connect through their application (this particular app connects
to SQL1). After some troubleshooting, I realize that she can only
connect when SQL1 resources are running on Node2. When I failover to
Node1, she can no longer connect. She can ping the virtual IP & the
DNS name that the application uses (the dns points to the virtual IP
of SQL1). Others in her environment can connect fine through the same
app. She can go to other machines & login with her login (SQL auth.)
& she can connect. So clearly it's a workstation issue - but it also
clearly seems to be related to the cluster, since this only happens
when I fail back to Node1, and it only happened after we did this
maintenance.
We're puzzled & need help. Any thoughts?
.
- Follow-Ups:
- Re: client can't connect when instance on one particular node
- From: Rodney R. Fournier [MVP]
- Re: client can't connect when instance on one particular node
- Prev by Date: Re: Side-by-side upgrade - moving master, msdb and model
- Next by Date: Re: Side-by-side upgrade - moving master, msdb and model
- Previous by thread: Re: Side-by-side upgrade - moving master, msdb and model
- Next by thread: Re: client can't connect when instance on one particular node
- Index(es):
Relevant Pages
|
