June 7, 2017 at 2:40 am
In a 2 node cluster, I can able to connect SSMS in Node 1 only. When i tried to connect in node2 i am getting below 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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)
But i can able to connect instance with port number "instance name,portnumber". Without port number its throwing error. TCP dynamic port is 56307.
Firewall is in off
June 7, 2017 at 3:09 am
You need to connect to the clustered name, not the individual node name. And if the SQL Server Browser service isn't running on the node on which the instance is running, you will also need to supply the port number in your connection string.
John
June 7, 2017 at 3:24 am
John Mitchell-245523 - Wednesday, June 7, 2017 3:09 AMYou need to connect to the clustered name, not the individual node name. And if the SQL Server Browser service isn't running on the node on which the instance is running, you will also need to supply the port number in your connection string.John
why its not connecting without port number in Node 2. It is connecting fine in Node 1. Browser service is running fine
June 7, 2017 at 3:32 am
vigneshbeece - Wednesday, June 7, 2017 3:24 AMJohn Mitchell-245523 - Wednesday, June 7, 2017 3:09 AMYou need to connect to the clustered name, not the individual node name. And if the SQL Server Browser service isn't running on the node on which the instance is running, you will also need to supply the port number in your connection string.John
why its not connecting without port number in Node 2. It is connecting fine in Node 1.
I don't know. Please post the names of both (all?) nodes, the name of the clustered SQL Server and the connection strings you are using.
Browser service is running fine
On both nodes?
John
June 7, 2017 at 4:21 am
John Mitchell-245523 - Wednesday, June 7, 2017 3:32 AMvigneshbeece - Wednesday, June 7, 2017 3:24 AMJohn Mitchell-245523 - Wednesday, June 7, 2017 3:09 AMYou need to connect to the clustered name, not the individual node name. And if the SQL Server Browser service isn't running on the node on which the instance is running, you will also need to supply the port number in your connection string.John
why its not connecting without port number in Node 2. It is connecting fine in Node 1.
I don't know. Please post the names of both (all?) nodes, the name of the clustered SQL Server and the connection strings you are using.
Browser service is running fine
On both nodes?John
Node 1
Node 2
network Name:tgssql
Instance Name:TGSSQL
In Node 1: SSMS is connecting fine
tgssql\TGSSQL
tgssql\TGSSQL,56307
In Node 2: getting Error
tgssql\TGSSQL ---> unable to connect DB engine
tgssql\TGSSQL,56307 --able to connect DB engine
June 7, 2017 at 5:02 am
You didn't confirm that SQL Server Browser is running on both nodes.
When you say you can only connect in Node1, does that mean that when you run SSMS on Node1 you can connect, but if you run it on Node2 you can't? Or do you mean that if you fail over to Node2 you can no longer connect, unless you specify the port? What happens if you connect in Node2 using the port and then run SELECT SERVERPROPERTY('ServerName'), SERVERPROPERTY('ComputerNamePhysicalNetBIOS')?
John
June 7, 2017 at 7:10 am
John Mitchell-245523 - Wednesday, June 7, 2017 5:02 AMYou didn't confirm that SQL Server Browser is running on both nodes.When you say you can only connect in Node1, does that mean that when you run SSMS on Node1 you can connect, but if you run it on Node2 you can't? Or do you mean that if you fail over to Node2 you can no longer connect, unless you specify the port? What happens if you connect in Node2 using the port and then run SELECT SERVERPROPERTY('ServerName'), SERVERPROPERTY('ComputerNamePhysicalNetBIOS')?
John
Browser service is running fine in both the nodes. As of now instance is running on Node 1, failover is not possible to check the ssms connectivity in node2. Currently I am unable to connect SSMS without specifying port number in Node 2.
What happens if you connect in Node2 using the port and then run SELECT SERVERPROPERTY('ServerName'), SERVERPROPERTY('ComputerNamePhysicalNetBIOS')?
TGSSQL\TGSSQL
TGVT01-SQL
June 7, 2017 at 7:19 am
It looks as if the SQL Server Browser service isn't working properly on Node 1, then. What happens if you try to connect from a different computer - your own PC, for example?
John
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply