meredithryan
asked on
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.
What am I missing in the setup or config?
Failover worked both ways prior to the upgrade.
ASKER
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)
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)
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 ?
...
...
ASKER
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
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
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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!
SP2 finished as made your last reply and it seems to be failing over both way's successfully now. thanks for your help though!
You're welcome ...
>>Instance 2 ...
So you have more instances of SQL 2005 running on the cluster or SQL 2000/SQL 2005 or ... ?
Hope this helps ...