Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Connecting to Clustered Instance Expand / Collapse
Author
Message
Posted Saturday, June 21, 2014 6:56 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Yesterday @ 7:07 AM
Points: 103, Visits: 277
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
Post #1584747
Posted Monday, June 23, 2014 4:29 AM This worked for the OP Answer marked as solution


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 3:29 PM
Points: 6,745, Visits: 14,384
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"
Post #1585040
Posted Monday, June 23, 2014 4:40 AM This worked for the OP Answer marked as solution
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Monday, July 21, 2014 2:56 AM
Points: 2,603, Visits: 2,061
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."
Post #1585043
Posted Monday, June 23, 2014 7:24 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Yesterday @ 7:07 AM
Points: 103, Visits: 277
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
Post #1585114
Posted Monday, June 23, 2014 7:25 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Yesterday @ 7:07 AM
Points: 103, Visits: 277
BTW yes I was able to Ping the instance name and its IP address and do an NSLOOKUP and it all worked fine.

Jeff
Post #1585118
Posted Tuesday, June 24, 2014 4:03 PM
Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Monday, December 15, 2014 4:01 PM
Points: 3,221, Visits: 2,374
What port are you using - the default 1433 ?

Is the Browser Service running ?

Have you checked Active Directory to verify the SPN ?





Regards
Rudy Komacsar
Senior Database Administrator

"Ave Caesar! - Morituri te salutamus."
Post #1585710
Posted Tuesday, June 24, 2014 5:35 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Yesterday @ 7:07 AM
Points: 103, Visits: 277
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
Post #1585720
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse