June 21, 2014 at 6:56 pm
06/21/2014
I have an issue where I cannot connect to an instance using the Cluster name. I can connect using the node name and instance name.
Everything was fine until we had to move the instances around to reboot the nodes.
When I try to use SSMS to connect by using CLUSTER\INSTANCE I get the following error:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.) (Microsoft SQL Server, Error: 10061)
When I try connecting using the NODE1\INSTANCE I can connect just fine.
There is another instance in the cluster that I can connect to just fine using CLUSTER\INSTANCE
We are using the Veritas Cluster Solution and both servers are running Windows Server 2008 with SQL 2008 R2
Your help is appreciated.
Jeff
June 23, 2014 at 4:29 am
what version of VCS are you using?
have you contacted symantec or checked their knowledgebase for help?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
June 23, 2014 at 4:40 am
Are you able to ping the server with sql server virtual name? or ping virtual IP address?
---------------------------------------------------
"Thare are only 10 types of people in the world:
Those who understand binary, and those who don't."
June 23, 2014 at 7:24 am
Thanks for the help.
I am new to VCS and dont know much about it nor have i used the knowlege base, but started looking at it over the weekend.
Kind of weird because a co worker suggested I use a different name and it connected up fine. Until friday the name I was using working fine, but after moving the instances around a few time it stopped working. I will work at it a little, but since it working fine now I am not going to beat it to death.
Thank you very much for your help again.
Jeff
June 23, 2014 at 7:25 am
BTW yes I was able to Ping the instance name and its IP address and do an NSLOOKUP and it all worked fine.
Jeff
June 24, 2014 at 4:03 pm
What port are you using - the default 1433 ?
Is the Browser Service running ?
Have you checked Active Directory to verify the SPN ?
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
June 24, 2014 at 5:35 pm
Thanks for the reply.
Yes the browser service is running and No i have not checked the SPN. I will check that next to see why this has happened.
Jeff
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply