January 4, 2017 at 3:47 pm
Hi everyone , hoping someone could assist with my current confusion...
I have a SQL 2012 cluster , 2 node active passive setup.
SQL is running on a non default port which has been set in TCP properties within SQL config manager.
Protocols for MSSQLSERVER are all enabled , Shared Memory , Named Pipes and TCP/IP
Client Protocols all enabled Shared Memory 1 ,TCP/IP 2 and Named pipes 3.
SQL server has been restarted a number of times , Cluster fails over as expected ok in regards to SQL
However when I run the following
SELECT
CONNECTIONPROPERTY('net_transport') AS net_transport,
CONNECTIONPROPERTY('protocol_type') AS protocol_type,
CONNECTIONPROPERTY('client_net_address') AS client_net_address
I get:
net_transportprotocol_typeclient_net_address
Named pipeTSQL <named pipe>
So this returns the physical transport protocol that is used by this connection ,
ie it is using named pipes and not TCP/IP ? Is that correct ?
Disabling named pipes in config manager does not allow me to bring the SQL cluster on line post service restart.
When reset to enable Named pipes the SQL cluster does come on line.
Is that an indication of a Cluster issue ?
Reason for all this testing is that I am unable to install an app , and I wanted to ensure that the cluster is configured correctly before proceeding.
This is the app installation error message , but I don't get much more than this in any other logs.
"error 27502 could not connect to microsoft sql server dbnetlib"
Any other checks I can suggest to the platform team in regards to the SQL cluster config would be appreciated.
many thanks
January 4, 2017 at 9:25 pm
This was removed by the editor as SPAM
January 5, 2017 at 1:55 pm
Not sure if you are using a listener, but when you fail over and if you used the SERVER1 name, you connection may fail and that is not longer the active server.
Curtis Smith
SQL Server DBA
Well in worked in Theory ...
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply