[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 244
  • Last Modified:

Cannot connect to clustered sql 05 instance when failed over to primary node

I just upgraded my test Active/Active cluster from sql 2000 sp4a to SQL 2005. While the sql instance that normally runs on node2 was failed over to node1 instance2 refused remote connections.  I have not had a chance to test failover the other way (all instances to node2).  Obviously this defeats the purpose of clustering.
What am I missing in the setup or config?  
Failover worked both ways prior to the upgrade.
0
meredithryan
Asked:
meredithryan
  • 4
  • 3
1 Solution
 
YveauCommented:
Activated the remote connection option in SQL 2005 ... it's off by default.
>>Instance 2 ...
So you have more instances of SQL 2005 running on the cluster or SQL 2000/SQL 2005 or ... ?

Hope this helps ...
0
 
meredithryanAuthor Commented:
I did verify that remote connections were activated in the Surface Area Configuration tool.
here is my setup:
Active/Active cluster (that used to failover cleanly both ways)
Node1 - windows 2003 advanced with named instance SQL 2005 Enterprise (3 user db's)
Node2 - windows 2003 advanced with named instance SQL 2005 Enterprise (1 user db)

0
 
YveauCommented:
So let me get this straight ... You've got two active SQL Servers (in a node config) operating just fine ... each of them. Then you failover node 2 to node 1 and the whole instance on node 1 is no longer accessible ... even though it was before the failover ?

...
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
meredithryanAuthor Commented:
almost..  Instance1 (which lives on node1 normally) is accessable.  Instance2 (which lives on node2 normally) is not.
I am applying SP 2 currently, although I don't hold much hope that it will fix this issue.  

Also, when Instance2 is running off of Node2 it is accessable remotely via SSMS running on node1
0
 
YveauCommented:
Both instances running on different port numbers ? you can't share port 1433 for tw instances o one machine !
Make sure that for example instance 1 is always running 1433 and instance 2 is always running 51433 (just to name a number) so that when a failover occurs, they are not fighting on the port ...
What happens if you fail instance 1 over to machine 2 ?

Hope this helps ...
0
 
meredithryanAuthor Commented:
both instances were running on different port numbers.
SP2 finished as made your last reply and it seems to be failing over both way's successfully now.  thanks for your help though!
0
 
YveauCommented:
You're welcome ...
0

Featured Post

 [eBook] Windows Nano Server

Download this FREE eBook and learn all you need to get started with Windows Nano Server, including deployment options, remote management
and troubleshooting tips and tricks

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now